Hi,
You'll want OAuth.
Start here: http://dev.twitter.com/pages/auth_overview
-- Tatham
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-talk@googlegroups.com] On Behalf Of ken lee
Sent: Monday, 4 July 2011 6:02 AM
To: Twitter Development
Just because it doesn't require authentication doesn't mean you can't auth
anyway.
--
Tatham Oddie
au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie
If you're printing this email, you're doing it wrong. This is a computer, not a
typewriter.
From:
left that hour.
That's how I understand it ...
--
Tatham Oddie
If you're printing this email, you're doing it wrong. This is a computer, not a
typewriter.
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-talk@googlegrou
http://dev.twitter.com/pages/tweet_entities
+
http://freenuts.com/top-10-websites-to-expand-any-short-url/
--
Tatham Oddie
au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie
If you're printing this email, you're doing it wrong. This is a computer, not a
Sounds like you might need some Google practice ...
http://tweetsharp.codeplex.com/wikipage?title=UserGuide&referringTitle=Documentation
--
Tatham Oddie
au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie
If you're printing this email, you're doing it wrong. This
Dukeman330,
This issue is being discussed on this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1011865585b129b5
It has been a problem for a few days now and Twitter aren't being very
energetic to fix it.
--
Tatham Oddie
au mob: +61 414 275 989, us
y%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--dad7912a647454357cfa6f0d07804b5c4b5d6ae4;
domain=.twitter.com; path=/; HttpOnly
Server: hi
Vary: Accept-Encoding
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
oauth_token=...&oauth_token_secret=...&user_id=14051560&screen_na
Please go and star this issue:
http://code.google.com/p/twitter-api/issues/detail?id=2118
On Mar 19, 11:47 pm, Trevor Dean wrote:
> Is anyone else experiencing any 401 errors all of a sudden? I was doing
> some testing this morning and was logging in fine using twitter and then 10
> min later I
I'm getting this same behaviour on http://ivebeen.to
If I wait about 30 seconds before trying to convert the request token
to an access token, it all works fine.
This happens on both my local machine and on the deployed website -
two distinct machines in different locations, timezones, etc.
Both
