[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PMPST and Monday, May 11th Noon-1PM PST

Well, that's true. But, not necessarily. I don't think I was out of line asking for clarification. -Original Message- From: Abraham Williams <4bra...@gmail.com> Date: Fri, 8 May 2009 00:33:09 To: Subject: [twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Mond

[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST

That is usually what "site maintenance" means... Sent from Dev G1 On May 8, 2009 12:24 AM, "Brian Gilham" wrote: Since the message doesn't make it clear (unless my sleep-deprived mind is missing it), will this mean downtime? Jesse Stay wrote: > > Can you share what exactly this will affect?

[twitter-dev] Twitter4J 2.0.2 released - adding trends api support, gzip support for faster performance

Hi all, I'm glad to announce that Twitter4J 2.0.2 is now available for download. http://yusuke.homeip.net/twitter4j/en/index.html#download It'll be available at the Maven central repository in 24 hours. http://repo1.maven.org/maven2/net/homeip/yusuke/twitter4j/ Until then, you may use the snapsho

[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST

Since the message doesn't make it clear (unless my sleep-deprived mind is missing it), will this mean downtime? Jesse Stay wrote: Can you share what exactly this will affect? What symptoms will we see? Thanks, Jesse On Thu, May 7, 2009 at 4:21 PM, Doug Williams > wr

[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST

Can you share what exactly this will affect? What symptoms will we see? Thanks, Jesse On Thu, May 7, 2009 at 4:21 PM, Doug Williams wrote: > Prepare your apps! The status blog has the details [1]: > >> We’re planning a significant database upgrade that will greatly increase >> system performa

[twitter-dev] Re: since_id basic usage confusion

Hi there, Just as a general software comment if you're sending since_id it's probably a good idea to also double check your results. That said: since_id should work like you expect. One case where it does not work is if you follow the next_page URL for pagination. When you do that th

[twitter-dev] Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST

Prepare your apps! The status blog has the details [1]: > We’re planning a significant database upgrade that will greatly increase > system performance. To do this, we will require two planned maintenance > windows: Friday, May 8th from 2p-3p Pacific and again on Monday, May 11th > from Noon-1p Pa

[twitter-dev] Re: since_id basic usage confusion

Your understanding of since_id is correct. If you specify since_id=x then you should only get back tweet ids strictly greater than x. Are you using PHP 5? If so, I strongly recommend using the .json feed instead of .atom and using json_decode() to parse the data. -Chad On Thu, May 7, 2009 at

[twitter-dev] always non-empty?

This is an older post, but I saw no activity around it. I'm seeing this too. It seems that the field profile_background_image_url should either be blank or there should be another flag (like the tile flag) that says if the background_image is being shown or not. Thanks. http://groups.google.co

[twitter-dev] since_id basic usage confusion

Hi all, I have looked at the API and searched this group but can't find the answer. I've created some code which is doing a search and doing some analysis on the results and then poking the results into a database. Simple enough. This code then runs a few minutes later. I obviously don't want t

[twitter-dev] Re: Can Twitter please pick a From: and stick with it?

On Thu, May 7, 2009 at 8:15 AM, Chad Etzel wrote: > > Hi Matt, > > When you decide on the final format and deploy, will you let us know, > please? I'm leaving my email filters in limbo until then. I've dealt with this by leaving my old filters in place. If Twitter switches back to something o

[twitter-dev] Re: Public Timeline Frozen

Excellent job! Many thanks, Alan On May 7, 9:38 pm, Doug Williams wrote: > The public_timeline is updating correctly again. > > @Hwee-Boon: that email as a bit premature. We will announce via @twitterapi > and this list when the push feed is available to the world at large. > > Thanks, > Doug

[twitter-dev] Re: Public Timeline Frozen

I noticed the freeze on one of my scripts that monitors it yesterday. Glad the issue has been resolved, everything working good here. On Thu, May 7, 2009 at 11:04 AM, Sanjay wrote: > > I'm not entirely sure but this may be somewhat my "fault". Yesterday > I noticed two different tweets in the p

[twitter-dev] Re: Public Timeline Frozen

I'm not entirely sure but this may be somewhat my "fault". Yesterday I noticed two different tweets in the public timeline that were attached to protected accounts. I don't think they were an effect of the accounts going from public->private since I caught them right after they showed up and saw

[twitter-dev] Re: Public Timeline Frozen

The public_timeline is updating correctly again. @Hwee-Boon: that email as a bit premature. We will announce via @twitterapi and this list when the push feed is available to the world at large. Thanks, Doug Doug Williams | Platform

[twitter-dev] Re: Public Timeline Frozen

Hmm.. when did the Streaming API come about? I see Firehose mentioned in there, OK that's known. What's Spritzer? (I read the description and tested it). - Hwee-Boon On May 8, 12:39 am, John Kalucki wrote: > Matt, > > As Doug mentioned, we're working on fixing the public timeline. I hope > we c

[twitter-dev] Re: Default Device Notification

Chris, I'll clarify that now. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Thu, May 7, 2009 at 6:31 AM, Chris Carson wrote: > > Hi -- > > The follow parameter (turning device notifications on or off) in > friendships/create is not behaving as I expected

[twitter-dev] Re: Public Timeline Frozen

Matt, As Doug mentioned, we're working on fixing the public timeline. I hope we can get that updating again shortly. As a workaround, you might consider an early migration to the Streaming API. The /spritzer resource should have about the same amount of data, but in an easier to consume format.

[twitter-dev] Re: Public Timeline Frozen

We're having a look. I'll update this thread when it is taken care of. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Thu, May 7, 2009 at 7:19 AM, Alan wrote: > > I've been seeing a ver similar issue since yesterday with the partner > feed - a very small

[twitter-dev] Re: Can Twitter please pick a From: and stick with it?

You do a ton of great things, Matt. We all make mistakes, but you and the rest of the crew there do a bang-up job. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On May 7, 11:24 am, Matt Sanford wrote: > Hi all, > >      I left last n

[twitter-dev] Sample code to automate the basic to oauth credentials exchange

Hi, We recently converted our site to use twitter oauth over basic authentication and automated the exchange of credentials so that we didn't have to keep multiple workflows around nor bother our users. Here's a helpful script in ruby which makes use of the great twitter and mechanize gems. (thi

[twitter-dev] Re: Can Twitter please pick a From: and stick with it?

Hi all, I left last night while they were rolling this back to the old long format addresses. Re-reading the logs this morning it seems like there was some sort of problem and it was rolled back. Waiting for the engineer in question so I can find out more details but based on what I'

[twitter-dev] Re: Can Twitter please pick a From: and stick with it?

Hi Matt, When you decide on the final format and deploy, will you let us know, please? I'm leaving my email filters in limbo until then. Thanks, -Chad On Thu, May 7, 2009 at 12:59 AM, TjL wrote: > > *sigh* > > Seriously? I've already started telling people to change their filters > and now th

[twitter-dev] Re: invalid xml char in public timeline

I'm seeing this same problem at the exact same line/column many, many times per hour since yesterday. This is also because the feeds we are receiving (partner feed) are repeating constantly. This is a separate issue, whereby only a small handful of feeds are being repeated over and over, and we

[twitter-dev] Re: Public Timeline Frozen

I've been seeing a ver similar issue since yesterday with the partner feed - a very small number of feeds are repeating over and over, including one containing malformed XML (which makes it nicely obvious, as it shows up in error logs with an invalid character at the same line/column each time).

[twitter-dev] Re: Public Timeline Frozen

To give you an impression of the scale of this issue, of the last 10 requests for the feed, I have received 5 repeats each of 2 distinct feeds: The first begins with status 1718278475 , and is malformed, due to the presence of an end-of-medium character in status 1718277608 The second begins with

[twitter-dev] Re: Default Device Notification

Hi -- The follow parameter (turning device notifications on or off) in friendships/create is not behaving as I expected. It appears that having the follow parameter in the post data turns device notifications on, no matter what value you give it. My (php) code was this: public function createF

[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] Re: Handling the OAuth flow when the user clicks Deny / Decline

many thanks - it happens, I guess. On May 7, 7:38 am, Cameron Kaiser wrote: > > You are kidding me? Is my message above reason to Ban me from this > > group? > > I can only conclude this was a mistaken click on somebody's part, so I have > temporarily removed the ban. We'll deal with it off list

[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline

> You are kidding me? Is my message above reason to Ban me from this > group? I can only conclude this was a mistaken click on somebody's part, so I have temporarily removed the ban. We'll deal with it off list. -- personal: http://www.cameronkaiser.com/ --

[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline

You are kidding me? Is my message above reason to Ban me from this group? On May 6, 4:41 pm, Mobasoft wrote: > Glad that you are finally getting around to this. > I posted it April > 10thhttp://groups.google.com/group/twitter-development-talk/browse_thread... > > On May 6, 10:28 am, jmathai wr