I was the first batcher!

• 19:28 @maudlinanodyne so, you actually did a test shipment? #
• 19:32 @sspaz1000 Twitter had issues giving us your updates apparently, let’s see how it goes next time, ok? #
• 19:35 @gwenix please use www.loudtwitter.com/password to recover your password, thanks! #
• 19:39 @awareoflust I see your tweets delivered to blackasmysoul.com/, is there something specific you would like to be fixed? #
• 19:41 @wickedoll Please send me a mail with the details (blog address, example of miss-post, twitter names, etc…) so that I can look at it. Thx #
• 11:36 @JonnieHardcore your LJ password is incorrect #

Automatically shipped by LoudTwitter

I was the first batcher!

• 20:38 @sharizap Your LT account use LJ openid for authentication #

Automatically shipped by LoudTwitter

I was the first batcher!

• 16:00 @Ninjoo oh, I see, this is precisely because you changed your settings, it added 24h delay. Will fix, thanks for the report #

Automatically shipped by LoudTwitter

I was the first batcher!

• 11:40 @tuesdayoclock thanks #

Automatically shipped by LoudTwitter

I was the first batcher!

• 10:32 @parisindecember meaning that the password you set in LT is not correct. We are not allowed to do the atom posting #

Automatically shipped by LoudTwitter

I was the first batcher!

• 16:18 @ladymeg sure, send me an email, I’ll look into it tonight after work #
• 21:07 @scify your tweets got shipped 2mn ago and are in the hands of LJ now, are you sure they aren’t there? (I can’t tell: your LJ is private) #
• 21:36 @scify I’m glad it now works! #

Automatically shipped by LoudTwitter

I was the first batcher!

• 20:17 @sadiequality LT couldn’t deliver your tweets because your LJ password is not correct. #
• 20:39 @mister_bitters Heh, there is nothing I can do about your pump, I’m sorry Good luck with that! #
• 14:45 twitter had an outage of its own, I hope it didn’t or won’t impact your shipping, I’ll keep an eye on it. #

Automatically shipped by LoudTwitter

I was the first batcher!

• 21:38 @crygaia let’s see how it goes tomorrow. Yesterday I wasn’t out of the woods yet. #
• 13:59 @komalwaqar that is expected, you have checked the ‘only lifetweets’ option (only tweets tagged with #lt) #

Automatically shipped by LoudTwitter

I was the first batcher!

• 15:53 @casidhe It is being slowly restored just the time for LJ to acknowledge our new address. stay tuned, nothing is lost #
• 15:54 @dillyparanormal if post was scheduled no earlier than 6 hours than the restore, yes. #
• 21:51 @noetica a shipment is strictly 24h, if you missed/will miss somethg, you can send a test shipment to you, so that you try to get a bitmore #
• 23:43 @noetica nope, it only send tweets for the day before your date. Sorry… #

Automatically shipped by LoudTwitter

I was the first batcher!

• 20:29 heads up… linode gave me the new server today, loudtwitter is changing datacenter tonight #
• 21:59 maintenance begins…. #
• 22:48 @linode hmmm 10-15mn per Gig of data, means per gig of the image? it will take much longer than I expected to move this server #
• 22:49 @linode actually at speed currently displayed in the queue manager: 17hours :/ #
• 23:11 longer maintenance bit.ly/6Xhv6 #
• 12:43 @lomeinie it’s not a crash, it’s a planned maintenance after the recovery, sorry for the incovenience (see my tweets) #
• 12:44 @haphazardry I’m in a planned maintenance as announced on twitter, sorry for the inconvenience #
• 12:45 @roxannablack we’re back after our planned maintenance (see my tweets for announcements). sorry for the inconvenience #
• 12:47 @bikiniklad yeah… planned maintenance, I’ll be back as soon as I can #
• 14:15 server just rebooted in sunny california (previously we were) in newark, NJ. Tweets scheduled for the past 6 hours are shipped now. #
• 14:16 earlier tweets are skipped, please wait tomorrow. Thanks. Sorry for the longer than expected maintenance. #
• 14:22 @fenghuo yes I am! #
• 14:35 @creamy_amande not problems, a planned maintenance, and I’m back! #

Automatically shipped by LoudTwitter