the show times are not showing the right time if look at it and also the dsate and time for mny user will not show right like eastern fdont show it shows cal. time also not recinsine your pc time so cnat get right info

When I try to verify my account I get:

Error: Failed to connect, check network connection. #6

Any ideas?

A tweet I sent at 14:18 yesterday showed up as having been sent at 21:59. Both of the other tweets I sent the same day have the correct timestamps.

What caused this, and is there any way to fix it? It makes no sense, and is less than useful, to have tweets from lunchtime appearing as if they were sent late at night.

how long does shipping usually take?

I know that pubDate should be in rfc822 date-time format (something like: "%a, %d %b %Y %H:%M:%S GMT" -- argument for strftime() or strptime()), but my RSS feed supplies pubDate in the format "%a %b %d %H:%M:%S %Y" (default format produced by asctime(), ctime() functions).

Could twitterfeed add support for such format?

I've created a yahoo pipe to fix item's pubDate as a workaround, but maybe someone has this problem too.

Timing -- Sorry to put this in the wrong spot, but I dunno where else to put it: I live in Thailand, where it's now 5:00pm. However, Sandy thinks it is 6:00pm. Is there a way to fix this? (I assume it has to do with the US Savings Time system -- we don't change times, this close to the equator.)

Having a setting that allows the user of twitter to set his own parameters for followers/following

Stale Date- twitter users would pick a number of twitters from 1 to 50 and a number of weeks from 1 to 50. This number of post over time would determine who is automatically removed from your followers/following list. So if you were really open you could say to be on my list you have to post 1 time in 50 weeks. Or you could be a hard and say you have to post 50 times in 50 weeks.

With each user setting this up the Twitter software would go through on log in and check your parameters for inclusion, and boot those off your following/followers list who do not meet your requirement. Your first log in could take a while but it would be faster after that.

This means that everyone would have some requirements.

Those who are not using twitter will slowly get fewer and fewer contact. If they decide to start using twitter again they can always re-friend some one.

This would save cycles of computer time for those who are using Twitter and slowly minimize those who just joined to some one reach a membership number in some silly contest.

Nothing is bad about bringing people into twitter with contest but if they are just there to link to a few people and not ever show up again what good are they. This way they can still stay a member of twitter but they are limited in their footprint over time.

I like to express times in 24 hour clock format, but without a : or . in between. Surely I can't be alone in this? So long as the user types "at" before the time, could Sandy not start recognising times like 0900 and 2100? I don't think that's too ambiguous, and it would stop me accidentally scheduling all my reminders for the beginning of the day (i.e. 0700 digest).