Aha, looks like there already is one:
http://code.google.com/p/twitter-api/issues/detail?id=949colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
On Aug 22, 3:34 am, Chad Etzel jazzyc...@gmail.com wrote:
Please file a
Calling /statuses/destroy (on a valid status ID) seems to return a 400
error with a Bad request. We could not delete that status for some
reason..
... but the status is successfully deleted.
Bug?
I'm not saying OAuth is a panacea, but it is better than handing over
a password.
That's the crux of it. It's not a panacea (the UX sucks, especially
for iPhone apps), but the fact is it's only marginally better than
handing over a password. I mentioned this in my blog post (linked
above),
First of all I agree wholeheartedly with the philosophy of shifting
control to users and Twitter. I disagree with the details of the
implementation. (In particular using the browser as a crutch).
Ah, but then your application would have the user's password.
I can get the users password
Is it my imagination, or are some profile images not being scaled down
properly (again)?
Example: http://twitter.com/stealing_second
http://s3.amazonaws.com/twitter_production/profile_images/109230522/twitter_normal.jpg
- 466x371px...
I'll also take this time to request some scrubbing of
I'd like to second this request. It'd be more than reasonable for the
example above to count as 3 marks against the rate limit, the only
difference would be that there's a single round-trip to the twitter
servers rather than 3 (would save a bit of overhead on your end too).
This makes a ton of
Just to confirm: EXTREME prejudice as in 140 *bytes* as defined by
UTF-8 with HTML entity encoding only for special ( ) characters?
So my tweet should *NOT* have worked?
http://twitter.com/atebits/status/1286199010
Would love to see some kind of official *this is how we determine how
long some
They should - I believe there was an issue at one point where profile
images weren't being scaled down properly. It's fixed now, but old
(broken) avatars remain broken. That user needs to re-upload their
profile image.
On Mar 1, 7:51 pm, Dave Briccetti da...@davebsoft.com wrote:
This is odd.
Exactly. Changing the OS is a long way off if people want to use these
technologies today.
I agree completely, nothing is going to change overnight. What I
would like to do is encourage all of us to look towards the future.
Eventually, we can have our cake and eat it too (have something with
Not sure if pushing oAuth for desktop is actually a Good Thing (tm) or
an exercise in purity for purity's sake, UX be damned.
I think you hit the nail on the head. Sorry for that outburst
before. I love you Twitter.
I'm happy to jump through hoops on the client side and invent some new
Hey,
Figured I should start using this group rather than bug people
directly :).
Question: know you guys deployed a fix for the gigantor avatar
problem... will this fix existing avatars too? Or just newly uploaded
ones? Getting more reports of crashes when Tweetie tries to decode
humungo
11 matches
Mail list logo
