View Single Post
dwould's Avatar
Posts: 529 | Thanked: 262 times | Joined on Dec 2008 @ Eastleigh, Hampshire, UK
#395
Originally Posted by skr0 View Post
Version 0.3.2-4
I am using Oauth

'Error retrieving tweets Server returned 400:'
No this only happens once or twice a day. Usually when I try to refresh by pressing the circular arrows bottom left; speech bubble to left; circular arrows bottom left.
I am not sure what the api rate limit actually is
If you go to: http://api.twitter.com/1/account/rate_limit_status.xml
it should in theory prompt you for login, unless you are already logged in, and it should show you whether you are at your api usage limit on your account. I kept blowing this limit in development of witter and consequently got my account white-listed to remove the limit ;-)
Basically if twitter returns a 400 there is not much I can do other than report that's what it told me.

Originally Posted by skr0 View Post

but I was playing around with the settings and may have moved away from the most efficient way of setting it up. I have:
Time line - 1 sec
Mention - 5 secs
DM - 30
Public - 90
given that you thought the settings were seconds... when they are actually miniutes, I'm assuming you're pushing the refresh pretty hard. which would back up the chances that you've blown your api limit.

Originally Posted by skr0 View Post
Followers: selected Friends and refresh and got the error 'Error retrieving tweets Server returned 400:' four times.

The + tab brings up a menu at the bottom +20 +50... but this does not load more Tweets.
hmm, it's supposed to, again helps to know if basic auth or oauth
No does not work, no not even get the timer spinning in the top bar.
ok, so this is probably a defect then. Please try running witter from x-terminal:
run-standalone.sh python2.5 /opt/witter/witter.py
this will spit out lots of output whilst it runs. It will be quite noisy to begin with, once it's stopped, then hit the +20 button and see what it says, it's possible that I'm not handling some error condition properly. Though I did try it this morning with 0.3.2-4 and it works ok for me
Originally Posted by skr0 View Post

"Sometimes when I launch the app there are only one or two tweets or none but when I check on twitter.com there are dozens."
Sometimes the twitter api doesn't seem to return the full list of tweets, I think it's their side rather than mine, as it happens occasionally.
Occurs more with retweets if that is helpful information.
ok again, if you run witter as above we should find out more about what's going on, it's possible that witter fails to parse something in teh tweets you're getting and that stops it in it's tracks. Do you follow any one that might lead to 'unusual' tweets?

I have considered making witter always log to a file, but I'm not sure that I want to incur the cost of this, it may well adversely effect performance, but would help in these situations.
Originally Posted by skr0 View Post
Your pint should have been delivered to you.
Many thanks
Thank you very much, you have the honor of being the first (and currently only) person to donate towards the development of witter.


EDIT: also may be relevant that twitter is currently showing the fail whale, and nothing is working ;-)
__________________
----------
N900
http://danielwould.wordpress.com
Check out Witter, a twitter client for N900
http://danielwould.wordpress.com/witter

If Witter isn't working for you, eg crashes/doesn't start, gives errors etc etc. Please run it from x-term using:
run-standalone.sh python2.5 /opt/witter/witter.py

This will generate diagnostic output. Without this I cannot help you.

Last edited by dwould; 2010-05-19 at 14:46.