Well, it's not an API issue. ;-)
Tom
On 9/30/10 9:42 PM, Jonathan Strauss wrote:
> @themattharris, Pat's ticket just got rejected for not being an API
> issue :-/. See http://code.google.com/p/twitter-api/issues/detail?id=1904
>
> I have just filed it (again) via http://twitter.com/help/escalat
@themattharris, Pat's ticket just got rejected for not being an API
issue :-/. See http://code.google.com/p/twitter-api/issues/detail?id=1904
I have just filed it (again) via http://twitter.com/help/escalate.
-jonathan
On Sep 28, 9:24 pm, Jonathan Strauss wrote:
> Heh, thanks Pat! That was on m
Heh, thanks Pat! That was on my To Do list for tonight, I swear :-)
On Sep 28, 9:04 pm, Pat Diven II wrote:
> Hey Jonathan, how's the Mission? Figures that I'd find a thread
> started by you for the same issue we're also having. :)
>
> So yes, we're also getting bit by the same issue. One thing
Hey Jonathan, how's the Mission? Figures that I'd find a thread
started by you for the same issue we're also having. :)
So yes, we're also getting bit by the same issue. One thing I noticed
on #newtwitter is that the encoding is mangled during a redirect
(from /home?status= to /?status=):
Redire
Hey Jonathan,
Absolutely! Just wanted to put the Tweet Button out there as an option.
So we can track this can you file an issue on:
http://code.google.com/p/twitter-api/issues/list
I'll keep that updated with progress.
Thanks,
@themattharris
On Sep 24, 2010, at 18:54, Jonathan Strauss wr
Hey Matt,
I know the tweet button very well, and I agree that it's better for
most use-cases (we're actually driving our customers towards using /
share instead of /home?status= for their custom share to Twitter
interfaces). However, all legacy 'Share on Twitter' or 'Tweet This'
implementations (t
