Loudtwitter server has been attacked via lots of SPAM two days ago. It looks like it's not completely back up... I'll look at this today
Loudtwitter server has been attacked via lots of SPAM two days ago. It looks like it's not completely back up... I'll look at this today
Posted at 10:01 AM | Permalink | Comments (0) | TrackBack (0)
Got an issue with Daily Saving Time (&%#*!)
and Sao Paulo timezone... It's solved and tweets are flowing again.
Posted at 05:31 PM | Permalink | Comments (7) | TrackBack (0)
I just found an issue with DST, some of you changed time last night, and may received several loudtwitter posts instead of one. :(
Posted at 05:36 PM | Permalink | Comments (3) | TrackBack (0)
All my bad, I switched from the "production" database to the "test" database... which resulted in new users not taken into account and double posting (no case reported so far, but that could have happened). Sorry for the inconvenience!
Posted at 11:30 AM | Permalink | Comments (2) | TrackBack (0)
As a twitter user, you probably have been bothered by one of your contact saying
@bob tx!
You don't even know "bob"! But that ability of temporarily switching from a one-to-many to a one-to-one communication is part of the beauty of twitter, so you probably do it also. That's why LoudTwitter is now offering you the option of not posting these replies to your blog.
LoudTwitter lets you also get rid off timestamped bullet style lists. Your tweets will taste less twitter and more blog.
This kind of post is now possible:
Gorgeous sun in Potrero Hill. Will ride my bike to Golden Gate park.
Ran into my sister and her girlfriend, had good times with the dogs.
Cooking goat cheese tarte and crumble for dinner with Brad Pitt. Will probably have dinner on the deck by the pool with cats lurking.
Enjoy!
Posted at 10:22 PM | Permalink | Comments (2) | TrackBack (0)
araceli suggested to allow Loudtwitter with private twitter account, I see two ways of doing that:
Both methods require to fetch the content using authentication regarding to Twitter API, which I'm afraid will get me some troubles (I think Twitter puts some limit on how often you can pull protected content from a single IP address).
What method would you prefer?
Update August 2008: For now I have no intention to implement such a feature because of lack of time and because twitter might break this loudtwitter in the same way it broke last monthPosted at 11:22 AM | Permalink | Comments (10) | TrackBack (0)
Posted at 05:31 PM | Permalink | Comments (2) | TrackBack (0)
Posted at 05:33 PM | Permalink | Comments (4) | TrackBack (0)
Posted at 05:35 PM | Permalink | Comments (0) | TrackBack (0)