>  On the api page (http://api.openomy.com/2.0) where it talks about
>  creating signatures there is a serious error that makes it impossible
>  to generate valid signatures if you just follow the spec.   It states:

>  Construct an HMAC-SHA1 of the following pattern:
>  HTTP-VERB\n
>  relativeUri\n
>  date\n

>  Note the \n at the end of date.  That is *incorrect*.  The pattern
>  should be:
>  HTTP-VERB\n
>  relativeURI\n
>  date

>  with no \n after date.  If you put in the \n you will get a 401
>  invalidSignature error when you try to use your confirmed token to
>  actually do something.  The only way I worked this out was by tracing
>  the ruby library code and finally noticing that it does not append a
>  \n to the string that gets encoded.

>  You should really fix this as it makes it impossible to use the api
>  and is very hard to track down.