#!/usr/bin/env python

from BaseHTTPServer import HTTPServer
from CGIHTTPServer import CGIHTTPRequestHandler

serveradresse = ("",8080)
server = HTTPServer(serveradresse, CGIHTTPRequestHandler)
server.serve_forever()

And that's it. I've experienced two small downsides. First, I couldn't get it to serve CGI out of /, so I've needed to build the project under /cgi-bin, and second, it seems to get angry if I try to output unicode. But both of these are bearable for a simple dev setup, and will be easy enough to fix when I deploy to a real server.

1. Make a new twitter account. I chose retweetmont as an account name.
2. Open up your RSS reader, and subscribe to a feed in this format: http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=retweetmont (obviously replace "retweetmont" by your secondary user name
3. When you find a link you'd like to read later, just retweet it on this secondary account, and voilà, it'll show up in your RSS reader for later consumption. Easy as pie!

How shall I invest you?
In rest, or work, or play?
Or in seeking something greater?
Not right now, I've got all day...

Some developers over at XDA have been working on porting Cyanogenmod 7 to the Samsung Infuse 4G. While there is not yet an official Cyanogenmod release, there is a working rom available at the link above. While I would have preferred to wait until the Infuse code is added to the official Galaxy S branch to set this up on my phone, the recent CarrierIQ news gave me sufficient motivation to go ahead with this rom.

The instructions in the linked thread have everything you need, including instructions on how to root. I used a different method to root my device when I first got it (installing a different kernel using Odin), which actually caused me a bit of trouble; after rooting I had reinstalled the stock kernel, which bootlocked my phone. It took me a while to realise this was the problem, but once I did I just reinstalled the community kernel and everything went smoothly from there.

So far my experience with this rom is quite good. I have found that Swype has been a bit crashy, so I've had to reinstall it a couple times, but other than that have experienced no bugs.

EDIT: The link was to a thread that was no longer being updated, so I changed it to an active one.

I've always been frustrated by the fact that SSL certs for a website run in the $70/year and up range, which sets https (without having to deal with annoying untrusted certificate warnings and errors) beyond my limited, hobbyist budget.  However, I recently heard about StartSSL offering free basic certs, so I set it up today.

After a bit of fiddling (the SSL way of doing things is new to me), it's all up and working! At first only Chromium was calling my site verified, Firefox wasn't giving a bad cert error but was not convinced of the site's authenticity, and Fennec & the Android browser were giving me unknown cert errors. It turned out I hadn't installed the chain certs (a new concept to me), but once I got those in, everything was golden.

Vive les logiciels libres!

A couple of key tools making it workable on the tablet are easyswipe for gestures and onboard for the onscreen keyboard. I had to build my own onboard keymap for the device. The desktop environment is LXDE, to keep things light and snappy.

For instructions on how to do this, check out this thread at precentral. The first post will get you into a basic Ubuntu environment, then my instructions on how to get to a nice desktop are down on page five of the thread.

So this morning I wandered over here to my blog to post about ethics and software, specifically on the topic of why I appreciate Free Software and avoid Apple products, but I noticed this comment on a post about a script I had written (good thing I decided to look through my auto-filtered comment spam folder!). Chris Irwin had found the script, and made it better, implementing a feature I had not bothered to figure out how to do for myself, and posted the source.

This is the greatness of open software: find something that is almost what you need, but not quite, so change it! Share, and share alike!

I took a look at his code, and adopted it myself. And then I modified it more, to make it a little better still. Here's the latest version: maildir-indicator.py Chris licensed his changes under the GPL3, so the same license applies to this.

Honestly, it seems like the answer to that question is not much. It allows us to share photos. It allows us to keep up to date on what our friends are doing. It allows us to write blog posts, comment on friends' interactions, photos and posts. The thing is, we've had applications to do all of this for decades. Think about it: blogs, flickr and its ilk, message boards... facebook hasn't actually developed anything new here. Yes, now they're moving into voice & video chat, but again, that's nothing new. The only thing that facebook does that's new is to aggregate these activities together in one centralised, easy to use place. And they make a boatload of money by manipulating all that data we've entrusted to them to sell us stuff.

Now, my opinions on centralised, monolithic cloud apps are well known (short version: I think they're terrible for freedom, personal data ownership, and privacy). And yet I use facebook on a daily basis. But wouldn't it be nice if we could simply add the aggregating glue that facebook excels at on top of the technologies that already ran the social content before FB existed? I mean, build a facebook-like interface that would let us see and interact with friends blogs, photos, statuses, etc, but let the data stay on those distributed systems? So if you comment on a friend's blog post that shows up on your social feed, that comment gets pushed out to their actual blog, be it wordpress, blogger, drupal, or whaever other platform, instead locking everything in Facebook's own servers? It's kind of like an RSS aggregator, with the twist of pushing data out rather than just pulling it in.

I've been mulling this idea for a goodly while, and this week (since I wanted a vacation project) I started coding up a prototype. It's still in really early development, but it's gradually coming together, and is showing promise. I'll surely post more information in the coming days. Here are a few notes on what it does/will do:

• Aggregate social data from a number of sources (blogs, twitter, image feeds, etc). So far, I've got twitter and rss incoming
• Allow a Person (or friend) to not simply be linked to one such service, but many -- ie, Joe could have a blog, twitter feed, image feed, etc, all of which are attributed to a unified Person on the feed (this is implemented)
• Allow transparent replying to each of these feeds. This is without a doubt going to be the most difficult part, particularly to open up as many services as possible. I'm hoping to build this on OpenID as much as possible.

It actually seems pretty simple, doesn't it? I'd love to hear what others think of the idea. While I realise that it's unlikely that this will spark a revolution, I'm hoping it'll prove interesting at least to a certain community. If and wen I get it to a point where it's useful, I'll release the source and set it up as a public service.

If by any chance you have programming inclinations and would like to help out, drop me a line. I'm building it on python and django, so obviously familiarity with these technologies would help...

Go to stopspying.ca to sign the petition to have this legislation scrapped.