I just did a test with this status...
Testing my Twitter OAuth library with some special characters
!?:"*&^%...@!~`=+-_
and it went through without any errors and posted the correct status.
Ryan
On Wed, Feb 3, 2010 at 8:02 PM, ryan alford wrote:
> I don't know which version(if there are multi
I don't know which version(if there are multiple versions). I downloaded it
in October I believe.
Ryan
Sent from my DROID
On Feb 3, 2010 7:59 PM, "Andrew Badera" wrote:
>From Shannon's original stuff, or something more recent? I'd worked
with OAuthBase.cs in the past, but seemed to recall the
>From Shannon's original stuff, or something more recent? I'd worked
with OAuthBase.cs in the past, but seemed to recall there were
explicit exceptions in that ver of that stuff ... maybe a year ago
now?
--ab
On Wed, Feb 3, 2010 at 7:57 PM, ryan alford wrote:
> I don't want to take credit for i
I don't want to take credit for it as it is from Shannon Whitley's OAuth
library.
Ryan
Sent from my DROID
On Feb 3, 2010 7:53 PM, "Andrew Badera" wrote:
Interesting, for some reason I thought there were a few explicit
exceptions that had to be made, but your solution looks pretty
elegant.
--a
Interesting, for some reason I thought there were a few explicit
exceptions that had to be made, but your solution looks pretty
elegant.
--ab
On Wed, Feb 3, 2010 at 7:48 PM, ryan alford wrote:
> I have it working and have had it working for months. My code is
> open-source and written in C#.
I have it working and have had it working for months. My code is
open-source and written in C#.
http://twiteclipseapi.codeplex.com/
I haven't tried every special character, though I haven't run across a
character that didn't work.
Ryan
Sent from my DROID
On Feb 3, 2010 6:53 PM, "Andrew Badera
Are you following the proper URL encoding? Basic .NET URLEncode
doesn't meet OAuth's encoding spec. I forget what it is offhand, but
they aren't 100% equivalent.
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com
has anybody on a .NET library had problems with doing an oAuth
connection and then posting an update with special characters such as !?
We're having that problem on TwitterVB and I wanted to know if
somebody has gotten it fixed yet?