Twitterbot is the result of a night-and-half-a-day of hacking. It’s a Plurk bot that integrates your Twitter stream into your Plurk timeline, creating plurks for each tweet, and (attempting to) merge Twitter conversations into a single Plurk thread. It’ll also forward any response you make in these threads back to Twitter.
You can use Twitterbot by visiting its Plurk profile and adding it as a friend (not by being its fan). Within a couple of minutes it will request your Twitter name and password. Once these are provided, it will poll your Twitter account periodically for tweets to plurk.
You can shut it off by de-friending it, which will cause it to destroy all data it holds on you within a couple of minutes.
If you wish to use this, however, a few words of advice:
- You will, for all intents and purposes, be following everyone you follow on Twitter on Plurk. If you have thousands (or even a few hundred) of people you follow, you may find it difficult/impossible to keep your Plurk timeline reasonable. Twitterbot is not very helpful in this case.
- Capacity is limited. No idea how limited, but it’s limited, and further access will be forbidden once the limit is reached until it can be raised.
- There is a delay of up to two minutes before it notices you sending a plurk or friend request, and up to five minutes between receiving new tweets from Twitter.
If you want to use this, have fun! If not, eh. :p
This website has moved to a different server. If you can see this post, you’re using it. If you can’t, you aren’t, but you don’t know that yet anyway.
For trademark policy-related reasons, several websites of mine will be removed once Linden Lab’s 90 day grace period is up. I really do not have the time or interest to go about jumping nonsensical legal hoops.
The sites closing are the following:
- TSL Profiles
- TSL Blogs
- TSL Emporium (which was defunct anyway)
Additionally, a couple of other projects I was working on are cancelled. The Teen SL Blog has moved to
teenmetaverse.net.
Thank you, Linden Lab, for obliterating months of work. It is appreciated. I hate you people (or at least whoever came up with this stupid idea.)
AjaxLife has been updated to use libsecondlife 0.3 (+ fix for CAPS errors). In addition, teleporting is fixed.
Also, the SSL certificate should be valid now. Woo! 
I’ll update the svn when I can be bothered to boot Windows, which has the code on it.
Woot!
It doesn’t like being rotated to landscape and back again though.
Okay. So the server paniced and rebooted. Except it refused to finish the boot process.
[insert much prodding of assorted services]
So we’re back, after server load crashed and completely obliterated MySQL, requiring restoration of the database from backups. Fortunately, those backups were all of ten minutes old (excluding times where data couldn’t be collected), so it’s not too horrible.
I think everything’s back up. Except cron. Now to restart AjaxLife again. *waits impatiently on new server*
Don’t press strange buttons in Internet Explorer’s menus at school. You might get punished for it.
Depending on how things turn out, I may not be around for a while
Two hours later, things turned out okay, at least until Monday. And I can’t be any more specific for fear of wrath of various people.
Having spent the weekend in Cambridge, I’m now back at home. Woo.
And it’s the Easter holiday. Yay! 
This is my blog. Which will mostly likely be completely ignored by everyone (including me), but who really cares?
Today I set up my over-engineered “Coming soon” page on my new website. It uses AJAX to load a PHP proxy which loads another file on my other website containing its uptime. And this is for a page that’s supposed to be there because I’m too lazy to do anything. Right.
Mariel and I had fun taking pictures, like this one on this site’s homepage:
I’ll probably end up putting that off to the side somewhere. But for now, does anyone have any idea as to what to actually do with this site? Because I don’t.
