[twitter-dev] Re: Public timeline feed frozen at about 7 PST?
Thanks for the notice, my server has been trying to post the same public timeline feed all day. Is there a ETD to when the public feed will be up and running again? I'm also trying to perform some testing that requires this feed. Any info would be greatly appreciated. -Matt On Mar 2, 3:01 pm, Alex Payne wrote: > Power outage, slave database replication issues. Both are being > recovered from as I type. > > > > On Mon, Mar 2, 2009 at 11:48, Doug Williams wrote: > > Matt also mentioned a power outage at the search host. > > > Doug Williams > > > On Mon, Mar 2, 2009 at 2:01 PM, Chad Etzel wrote: > > >> I think there is some latent sluggishness in twitter this morning due > >> to a certain celebrity talking about twitter on a certain morning talk > >> show. > >> -Chad > > >> On Mon, Mar 2, 2009 at 2:00 PM, Nick Arnett wrote: > > >> > On Mon, Mar 2, 2009 at 10:57 AM, jungle wrote: > > >> >> Hi! I haven't been getting anything new from the public time feed for > >> >> the last four hours... Anybody else noticed this? > > >> > I'm not getting that feed, but I noticed a lot of failures, internal > >> > server > >> > errors, service too busy, etc., this morning when trying to get almost > >> > anything. Helped me work on code to deal with the 50x errors... ;-) > >> > Nick > > > -- > > Doug Williams > > > do...@igudo.com > >http://www.igudo.com > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Please Add Me to the List
Name: Matthew Arnold Twitter: twitter.com/mattarnold1977 e-mail: matt.arnold.1...@gmail.com blog: http://www.mattsblogsite.com app: http://www.populartweets.com Dev: ASP.NET; javascript; AJAX; SQL
[twitter-dev] Re: Python-twitter: Public stream not updating
I'm guessing that there is an issue with Twitter's servers. Hopefully someone will advise when the service will be back up and running again. This happens frequently, so I'm not surprised.
[twitter-dev] Re: Python-twitter: Public stream not updating
Yes, although it looks like the feed is leaking out new entries. Most of my updates are still failing. On Mar 31, 1:09 pm, Doug Williams wrote: > Are you guys still seeing this? > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Tue, Mar 31, 2009 at 6:51 AM, Matt Cottingham > wrote: > > > > > Ah, didn't catch your reply before I posted the above. > > > Thanks, I thought it was just me. The FAQ/Status log aren't exactly > > helpful. > > > On Mar 31, 2:41 pm, Jennie Lees wrote: > > > It's nowt to do with Python, the base public_timeline JSON isn't > > > updating and neither's the data mining feed :( > > > > --Jennie > > > > On Tue, Mar 31, 2009 at 2:25 PM, Matt Cottingham > > > > wrote: > > > > > I have been using the python wrapper for the API, which has been > > > > working fine for about a month. > > > > > Today I tried to call the public status using the simple > > > > getPublicTimeline() function, which normally works fine. > > > > > However, the stream is not updating and has been giving the same users > > > > and statuses all day. > > > > > Is there are reason for this? Perhaps a change in the API which > > > > renders the python function obsolete? > > > > > I would appreciate any help with this. > > > > -- > > > Jennie Lees > > > Founder, Affect Labs > > > jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] HTML Encoded Return Values
I was wondering if Twitter was going to encode all status text return elements as HTML? Right now, if you use the Search API, the text of a status comes back HTML encoded. However, if you perform an "update status" call, the returned status text is not HTML encoded. -Matt
[twitter-dev] Public Timeline Frozen
I just checked the log on my server and noticed that the public time line has been putting out the same status information since around 5 o'clock yesterday. Is this a known issue? -Matt
[twitter-dev] Public Timeline Frozen (Again)
Not sure if this is an outcome of the site maintenance, but it looks like the public timeline has been sending out the same statuses since about 9:20pm on 5/8/09. The timeline was frozen last week, but was fixed. Thus, I'm guessing this is a result of the maintenance that was just performed. Please let us know if this is a known issue.
[twitter-dev] oAuth .NET receiving Unauthorized Error (401)
All of my development up to this point has been with basic authentication. This is my first attempt at using oAuth. I setup an application at Twitter and received the identifying tokens. I believe I have signed the request properly, and formatted the request token url correctly. However, when I place the web request I receive a "401 Unauthorized" error. Could someone please point me in the right direction for diagnosing this issue? -Matt
[twitter-dev] Re: oAuth .NET receiving Unauthorized Error (401)
Bojan, Thanks for the reply. I'm using ASP .NET. -Matt On Jul 25, 4:15 pm, Bojan Rajkovic wrote: > On Fri, 2009-07-24 at 17:10 -0700, mattarnold1977 wrote: > > All of my development up to this point has been with basic > > authentication. This is my first attempt at using oAuth. I setup an > > application at Twitter and received the identifying tokens. I believe > > I have signed the request properly, and formatted the request token > > url correctly. However, when I place the web request I receive a "401 > > Unauthorized" error. Could someone please point me in the right > > direction for diagnosing this issue? > > > -Matt > > Hi Matt, > > What are you using to do OAuth? > > -- > Bojan Rajkovic > Biochemistry '10, Brandeis University > PGP Signature Key ID: 0x8783D016 > PGP Encryption Key ID: 0x2497B8B2 > > signature.asc > < 1KViewDownload
[twitter-dev] ASP .NET Development Issue w/OAuth Callback Parameter
I've been able to create a successful web request to receive an auth token from Twitter. However, Twitter is not sending me back to my development environment even though I have put the oauth_callback parameter on my request. It even shows my call back parameter in the URL on the Twitter oAuth authentication page. I'm wondering if anyone else is using VS 08 (ASP .NET) as their development environment and were able to successfully get the oAuth call back parameter to redirect back to their development environment? -Matt
[twitter-dev] Re: oAuth .NET receiving Unauthorized Error (401)
Andy, That was it! Sorting my parameters did the trick. After that I was able to successfully post a web request to Twitter's OAuth request token URL. Now, the next problem. I'm working in a development environment and I can not get the call back argument to work correctly. I've added it as a parameter in my web request and you can see it in the URL when logging into Twitter to get the token. But, Twitter just returns me back to my application that I registered with them (not my development environment that I've setup in my call back argument). -Matt On Jul 26, 4:55 am, Andrew Badera wrote: > On Sat, Jul 25, 2009 at 6:46 PM, mattarnold1977 > wrote: > > > > > Bojan, > > > Thanks for the reply. I'm using ASP .NET. > > > -Matt > > I suspect Bojan was more curious about what OAuth library you're using. If > you're doing it on your own, allow me to suggest DotNetOpenAuth instead. > > Also, are you sorting your parameters correctly? Non-alphabetized sort of > parameters prior to signing will give you a 401. > > Thanks- > - Andy Badera > - and...@badera.us > - Google me:http://www.google.com/search?q=andrew+badera > - This email is: [ ] bloggable [x] ask first [ ] private
[twitter-dev] Re: ASP .NET Development Issue w/OAuth Callback Parameter
AB, I'm using http://localhost as my call back parameter. But, Twitter just sends me back to my registered application site http://www.populartweets.com -Matt On Jul 27, 8:49 pm, Andrew Badera wrote: > On Mon, Jul 27, 2009 at 6:49 PM, mattarnold1977 > wrote: > > > > > I've been able to create a successful web request to receive an auth > > token from Twitter. However, Twitter is not sending me back to my > > development environment even though I have put the oauth_callback > > parameter on my request. It even shows my call back parameter in the > > URL on the Twitter oAuth authentication page. > > > I'm wondering if anyone else is using VS 08 (ASP .NET) as their > > development environment and were able to successfully get the oAuth > > call back parameter to redirect back to their development environment? > > > -Matt > > As I think I'd mentioned off-list, I'm able to redirect no problem, using > VS05 or VS08 or even VS10 VPC. > > I'm able to default to my registered callback, and I'm able to provide an > oauth_callback value for testing (localhost) that works without difficulty. > > What oauth_callback value are you providing, and what URL are you ending up > at? > > --ab
[twitter-dev] 401 Unauthorized When Getting an Access Token
I am using ASP .NET (VB) to try and authenticate using oAuth. I have been able to get a request token and direct a user to Twitter's authentication page. Twitter then redirects back to my app. At that point I attempt to get an access token, but I continue to receive 401 "unauthorized" errors. I have made sure that I am getting a new signature, using both the token and token secret when generating the signature, and that my url parameters are in alphabetical order, but I continue to get 401 errors. Has anyone experienced this, and if so, could you point me in the right direction toward diagnosing this issue? -Matt
[twitter-dev] Re: 401 Unauthorized When Getting an Access Token
Please, if anyone can assist I would be grateful. Here is a sample of my url I've formed to get the access token: http://twitter.com/oauth/access_token?oauth_consumer_key=myconsumerkey&oauth_nonce=6475147&oauth_signature=mysignature&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1248981982&oauth_token=mytoken&oauth_version=1.0 -Matt On Jul 30, 7:49 pm, mattarnold1977 wrote: > I am using ASP .NET (VB) to try and authenticate using oAuth. I have > been able to get a request token and direct a user to Twitter's > authentication page. Twitter then redirects back to my app. At that > point I attempt to get an access token, but I continue to receive 401 > "unauthorized" errors. I have made sure that I am getting a new > signature, using both the token and token secret when generating the > signature, and that my url parameters are in alphabetical order, but I > continue to get 401 errors. Has anyone experienced this, and if so, > could you point me in the right direction toward diagnosing this > issue? > > -Matt
[twitter-dev] Re: 401 Unauthorized When Getting an Access Token
JDG, Thanks for the reply. I didn't realize that I needed to include an oauth_callback parameter for getting the ACCESS TOKEN. I knew I could supply one (optional) when getting the REQUEST TOKEN. I thought it would automatically callback to the application I created with Twitter. I'm also not sure what you mean by the oob flow? -Matt On Jul 31, 3:20 pm, JDG wrote: > Since you're not including an oauth_callback, i would assume you're using > the oob flow, in which case, i have to ask, where's your oauth_verifier > parameter? > > On Fri, Jul 31, 2009 at 13:09, mattarnold1977 > wrote: > > > > > > > > > Please, if anyone can assist I would be grateful. Here is a sample of > > my url I've formed to get the access token: > > >http://twitter.com/oauth/access_token?oauth_consumer_key=myconsumerke... > > > -Matt > > > On Jul 30, 7:49 pm, mattarnold1977 wrote: > > > I am using ASP .NET (VB) to try and authenticate using oAuth. I have > > > been able to get a request token and direct a user to Twitter's > > > authentication page. Twitter then redirects back to my app. At that > > > point I attempt to get an access token, but I continue to receive 401 > > > "unauthorized" errors. I have made sure that I am getting a new > > > signature, using both the token and token secret when generating the > > > signature, and that my url parameters are in alphabetical order, but I > > > continue to get 401 errors. Has anyone experienced this, and if so, > > > could you point me in the right direction toward diagnosing this > > > issue? > > > > -Matt > > -- > Internets. Serious business.
[twitter-dev] Public Timeline Frozen
I just checked my server log and noticed that the public timeline hasn't been responding for about 2 hours. Has anyone else been experiencing this? Is anything going on that we should know about? Perhaps they are working on that service? -Matt
[twitter-dev] Followers Count in Public Timeline
Hi all. For the last week it seems as if the "followers_count" element has been disappearing from the public timeline feed. It's not happening during each cache cycle, but it is happening frequently throughout the day (20 times an hour). Does anyone know if there is work being done on that particular element? Thanks, Matt
[twitter-dev] Public Timeline Frozen
It looks like the public timeline api is reporting the same statuses over-and-over again. This started sometime yesterday (4/19) and continues today. Is anyone else experiencing this issue? Thanks, Matt -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen
Taylor, I just remembered that you were planning to change the generation of status ids. Has that already occurred? If so, where is the documentation on that again? -Matt On Apr 20, 10:14 am, Taylor Singletary wrote: > Hi Matt, > > I'm not able to see the issue at the moment -- can you provide some more > details like examples of duplicate status ids? The public_timeline endpoint > is cached for 60 seconds, so it will remain stagnant if you're requesting it > more often than that. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 > wrote: > > > > > It looks like the public timeline api is reporting the same statuses > > over-and-over again. This started sometime yesterday (4/19) and > > continues today. Is anyone else experiencing this issue? > > > Thanks, > > Matt > > > -- > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen
Taylor, That's odd then because I'm seeing duplicate status id messages in my log. I'll have to dig deeper to see which ID is being repeated to give you an example. -Matt On Apr 21, 10:45 am, Taylor Singletary wrote: > It has not happened yet. > > The most recent parts of the discussion are in this > thread:http://groups.google.com/group/twitter-development-talk/browse_thread... > > Thanks, > Taylor > > On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977 > wrote: > > > > > Taylor, > > > I just remembered that you were planning to change the generation of > > status ids. Has that already occurred? If so, where is the > > documentation on that again? > > > -Matt > > > On Apr 20, 10:14 am, Taylor Singletary > > wrote: > > > Hi Matt, > > > > I'm not able to see the issue at the moment -- can you provide some more > > > details like examples of duplicate status ids? The public_timeline > > endpoint > > > is cached for 60 seconds, so it will remain stagnant if you're requesting > > it > > > more often than that. > > > > Taylor Singletary > > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 > > > wrote: > > > > > It looks like the public timeline api is reporting the same statuses > > > > over-and-over again. This started sometime yesterday (4/19) and > > > > continues today. Is anyone else experiencing this issue? > > > > > Thanks, > > > > Matt > > > > > -- > > > > Subscription settings: > > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen
Taylor, I have a sample from my log. It's not very detailed, but at least you can see that it's happening at random times. I am waiting a full minute before hitting the timeline, so it's not that. Let me know your thoughts. 4/22/2010 7:22:21 PM~Duplicate Message ID: 12667336000 4/22/2010 7:28:16 PM~Duplicate Message ID: 12667634000 4/22/2010 7:29:18 PM~Duplicate Message ID: 12667683000 4/22/2010 7:37:20 PM~Duplicate Message ID: 12668102000 4/22/2010 7:41:17 PM~Duplicate Message ID: 12668312000 -Matt On Apr 21, 1:53 pm, mattarnold1977 wrote: > Taylor, > > That's odd then because I'm seeing duplicate status id messages in my > log. I'll have to dig deeper to see which ID is being repeated to > give you an example. > > -Matt > > On Apr 21, 10:45 am, Taylor Singletary > wrote: > > > > > It has not happened yet. > > > The most recent parts of the discussion are in this > > thread:http://groups.google.com/group/twitter-development-talk/browse_thread... > > > Thanks, > > Taylor > > > On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977 > > wrote: > > > > Taylor, > > > > I just remembered that you were planning to change the generation of > > > status ids. Has that already occurred? If so, where is the > > > documentation on that again? > > > > -Matt > > > > On Apr 20, 10:14 am, Taylor Singletary > > > wrote: > > > > Hi Matt, > > > > > I'm not able to see the issue at the moment -- can you provide some more > > > > details like examples of duplicate status ids? The public_timeline > > > endpoint > > > > is cached for 60 seconds, so it will remain stagnant if you're > > > > requesting > > > it > > > > more often than that. > > > > > Taylor Singletary > > > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > > On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 > > > > wrote: > > > > > > It looks like the public timeline api is reporting the same statuses > > > > > over-and-over again. This started sometime yesterday (4/19) and > > > > > continues today. Is anyone else experiencing this issue? > > > > > > Thanks, > > > > > Matt > > > > > > -- > > > > > Subscription settings: > > > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Public Timeline - Duplicate Status IDs
I posted this issue a couple of days ago when I noticed my logs reporting duplicate status IDs from the public timeline. I haven't heard back from Twitter support, so I wanted to post another message out there. Perhaps someone else is experiencing this issue. I checked and it looks like around 8:54 PM on 4-19-10 Twitter's status IDs from the public timeline started reporting differently. Typically status IDs look something like this "12475374318", but now they all have zeros at the end like this "1247538". I thought this had something to do with the upcoming change to the way status ids were being generated. But Taylor from Twitter support said that change hasn't been implemented yet. My log is filling up with duplicate ID messages, so I'm hoping that someone out there knows what is going on. Any help would be greatly appreciated. Regards, Matt -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline - Duplicate Status IDs
Yes, I was able to confirm that along with duplicate ids the statuses were also duplicated. Here is a sample: 4/28/2010 7:37:10 AM~Duplicate Message ID: 13001313000 ?? #Orix_Buffaloes 4/28/2010 7:40:09 AM~Duplicate Message ID: 13001427000 ternyata eh ternyata ckckk ! On Apr 24, 9:56 am, Raffi Krikorian wrote: > hi matt. > > it seems like you are asking about two things here. > > 1. the status IDs on the public timeline have zeros on the end -- that's > because we have a really simple algorithm picking statuses that go into the > public_timeline > > 2. between subsequent calls to the public timeline, even after the caching > period, you are seeing duplicate statuses. > > so, for #2, are you seeing new statuses also? > > On Sat, Apr 24, 2010 at 6:15 AM, mattarnold1977 > wrote: > > > > > > > I posted this issue a couple of days ago when I noticed my logs > > reporting duplicate status IDs from the public timeline. I haven't > > heard back from Twitter support, so I wanted to post another message > > out there. Perhaps someone else is experiencing this issue. > > > I checked and it looks like around 8:54 PM on 4-19-10 Twitter's status > > IDs from the public timeline started reporting differently. Typically > > status IDs look something like this "12475374318", but now they all > > have zeros at the end like this "1247538". I thought this had > > something to do with the upcoming change to the way status ids were > > being generated. But Taylor from Twitter support said that change > > hasn't been implemented yet. My log is filling up with duplicate ID > > messages, so I'm hoping that someone out there knows what is going > > on. Any help would be greatly appreciated. > > > Regards, > > Matt > > > -- > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Duplicate Statuses in Public Timeline
This is the third time I've reported this issue in the last couple of weeks. I still have not received any word back from Twitter support regarding this issue. My server log is filling up with duplicate status errors coming from the public timeline. I'm waiting to hit the timeline until after the cache period, so it's not that. And, yes it's not just duplicate status ids I'm seeing, it's also duplicate statuses as well. Every time I hit the public timeline I compare the results against a months worth of data that I have saved. Is anyone else having this issue? -Matt
[twitter-dev] Re: Duplicate Statuses in Public Timeline
John, I am using the public timeline for analysis. I haven't examined the streaming API, but it sounds like that's what I need to use. In the mean time I guess I'll just have to ignore the duplicates. Thank you for the response. -Matt On Apr 29, 9:47 am, John Kalucki wrote: > What is your goal for this application? > > Are you trying to get a sampling of statuses for analysis, or for > occasional casual display? If the former, you should use a sample > method on the Streaming API. If the later, please persist in your > quest for a reasonably unique result set. The public timeline isn't > used much anymore and regressions could theoretically and regrettably, > exist for a bit without anyone noticing. > > -John Kaluckihttp://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > On Thu, Apr 29, 2010 at 4:54 AM, mattarnold1977 > > > > wrote: > > This is the third time I've reported this issue in the last couple of > > weeks. I still have not received any word back from Twitter support > > regarding this issue. My server log is filling up with duplicate > > status errors coming from the public timeline. I'm waiting to hit the > > timeline until after the cache period, so it's not that. And, yes > > it's not just duplicate status ids I'm seeing, it's also duplicate > > statuses as well. Every time I hit the public timeline I compare the > > results against a months worth of data that I have saved. Is anyone > > else having this issue? > > > -Matt
