Indeed. We don't expose information about users' devices, and we
don't intend to on a mass scale.
On Thu, Oct 16, 2008 at 10:25 PM, Abraham Williams <[EMAIL PROTECTED]> wrote:
> Nope. I would imagine that Twitter would get a large amount of flack for
> divulging that kind of personal information
Nope. I would imagine that Twitter would get a large amount of flack for
divulging that kind of personal information.
Abraham
On Thu, Oct 16, 2008 at 23:25, DustyReagan <[EMAIL PROTECTED]> wrote:
>
> Thanks for the reply Abraham!
>
> I'm familiar with that method. No SMS data though.
>
> Any oth
Thanks for the reply Abraham!
I'm familiar with that method. No SMS data though.
Any other idea? Could this be impossible?
On Oct 16, 10:24 pm, "Abraham Williams" <[EMAIL PROTECTED]> wrote:
> This is as close as you are going to
> get:http://apiwiki.twitter.com/REST+API+Documentation#followers
This is as close as you are going to get:
http://apiwiki.twitter.com/REST+API+Documentation#followers
On Thu, Oct 16, 2008 at 21:28, DustyReagan <[EMAIL PROTECTED]> wrote:
>
> Is there a way to find out who's following me by SMS via API or
> otherwise? Cause, that would be neat! :)
>
> Dusty
>
Is there a way to find out who's following me by SMS via API or
otherwise? Cause, that would be neat! :)
Dusty
We saw some intermittent cache corruption, but the problem has
corrected itself. We're investigating to ensure it doesn't happen
again, but all seems fine now.
On Thu, Oct 16, 2008 at 9:46 AM, Damon Clinkscales <[EMAIL PROTECTED]> wrote:
>
> I am also seeing 500 errors on /users/show, which is p
I am also seeing 500 errors on /users/show, which is preventing new
user signups on SnapTweet.
$ curl -I -u damon:wellyouknow "http://twitter.com/users/show/damon.xml";
HTTP/1.1 500 Internal Server Error
Date: Thu, 16 Oct 2008 16:39:51 GMT
Server: hi
Last-Modified: Thu, 16 Oct 2008 16:39:51 GMT
Hi,
Following API is returning complete HTML error page. Is it because of some
maintenance activity? it was working fine previously.
http://twitter.com/users/show/.xml
Thanks,
- Shahid
Hi Matt,
Thanks for your response.
Miguel
On 7 oct, 16:54, Matt Sanford <[EMAIL PROTECTED]> wrote:
> Hi Miguel,
>
> This is a known issue and we have it on our list of things to fix.
> For the curious, this is because search was built using the XMPP
> public timeline and that data feed did no
