I’m sorry if this is the wrong place to past my problem, but I’m desperate to find a solution. I have BeTwittered as an app on my iGoogle, and when I try to load it on my desktop the text box and my username show up, and the loading circle spins, but nothing else loads. None of the tweets load, and I can’t do anything with the application. I have enabled 3rd party cookies on firefox, and am at a loss for what else to try. If I try to log out and log back in I get an error 401. Please help!

Sorry to hear about your problem. I personally run into that one regularly because I’m messing around with Twitter quite a bit.

That error originates at the Twitter servers. It’s basically saying that there have been too many request for your Twitter account. They are pretty liberal, but it’s still not too hard to go over.

This *usually* happens if you use more than one or two twitter clients at a time. Twitter doesn’t separate the tracking per client, they track by account, unfortunately.

The solution might be as simple as waiting about 20 minutes. If that doesn’t work, you can try changing the setting for refresh rate in BeTwittered. The default is 3 minutes, but you might want to increase it a bit.

Let me know if this doesn’t help!

Thanks,
Robert

http://i44.tinypic.com/2uyt7yd.jpg

Is there something I can do?

You are actually on to something, I’ll have to look into it more. It may be too complicated to do well, but I’d have to write javascript to parse the timeline when it appears, and every time the browser window changes size. It may be ugly, though, trying to put words back together again when the browser window gets bigger. The outcome could be a Frankenstein’s monster… :-0

Thanks for your thoughts. I’ll be rolling this idea around for a few days, I think!
Robert

I’m wondering if there are internal browser functions (though there may be a general, standardized function) to measure the onscreen display length and to measure the display length of a set of characters and force a line break.
At the very least I would think there would be some sort of box that would force the text to go to the next line.
:/
Maybe not, just a couple thoughts born out of enough knowledge to be dangerous but not useful.

Thanks for letting me know you are seeing that issue.

That scrolling is an issue I haven’t figured out how to fix in a nice way, and is a bit of a problem that plagues web designers. I’ve searched and searched for a good solution.

The good news is that it will go away when the offending “tweet” scrolls off of your screen. It’s caused by-a-very-long-word probably strung together somehow like I just did. HTML code doesn’t have a nice way to handle that sort of thing.

Please do let me know if I’ve misunderstood, though. If I have, I’d like to know so I can look into the problem for you.

Sorry!
Robert

P.S. Don’t know if it matters, but my Betwittered it positioned on the right side of the page.
You’re welcome to contact me at my email.