Feb
1
Last night, some updates went into the released version of BeTwittered. Two features are added. The first is that replies and any other “@username” reference is now highlighted, and clickable. Clicking an @username reference will now take you directly to that persons Twitter home page. Also, there is now a settings page. Click on settings, and you’ll get, currently, two options: You can choose to logout of twitter, and you can choose to turn off user pictures in the timeline.
Related news: It appears that google may have fixed an issue they were having with their gadget directory. Since last night, BeTwittered and “Amazon Top 10 Geek/Tech Books” are showing up again. This means you can use “add stuff” on your Google homepage to get these gadgets again (and a whole lot of others that were also missing)
Comments
7 Responses to “New Features Added to BeTwittered”
Leave a Reply
I can’t use german letters “Umlaute” like “ä ö ü”. Are you considering implementing those “Umlaute”?
Thanks for letting me know about this issue. I’ll have to look into this for you. I’m not quite sure, to be honest, what I’d need to do to support more languages. I had assumed that PHP (the language BeTwittered is written in) handled this by default, but it may be something I’ve missed. I will have a look.
In my test version, I’ve gotten BeTWittered to work with the above mentioned characters that use the umlaut. Look for this to start working for you in the next couple of days. I want of fix a minor bug, and do some more throrough testing first.
How is the username/password info handled? In one of the other gadgets it is sent cleartext through a third party, which is less than secure. How does it work with yours?
FYI: tweets are not posting from the iGoogle gadget or the mobile beTwittered page today.
oh, wait a sec, they are posting, they are just not showing up in the BeTwittered list!
Hi Marc, Thanks for the feedback. I haven’t seen this before. It’s really helpful to know the post worked. I’ll try to duplicate it, or see if there is a way I can catch this as an error. Did you have the problem consistently? Or did it come and go?
THANKS!