I'm not so sure about releasing this widely as a service necessarily, however I am quite happy to add you to the list – in fact I've just begun to aggregate and syndicate your updates.

I think my preference would be to err on the side of caution in the short term, while I assess how well things are working. So limiting the number of feeds coming through (at least initially) seems like the safest plan.

That said I'm happy to assist/advise others on how they can set up similar systems if they desire and will continue to document the process I'm working through – including issues or pleasant surprises. It's not very difficult and yet lets you retain control over your data (whether you choose to release it under open licenses or not).

One of the main considerations at this stage is load and capacity. I have no idea what sort of strain syndication will exert on the system – or what thresholds may exist after which things start to have trouble. I seem to recall that one of my colleagues at UNSW ran into problems syndicating the feeds of many blogs, and which ultimately started bringing down the server. I don't expect it would happen in this instance – because he was pulling in several hundred blogs-worth of data – however it is a possibility to bear in mind.

I've also just discovered that the feeds from individual users are being handled differently from those of hashtags. @ references and weblinks are being made formatted as clickable links in the instance of hashtags, but not for individual users – and I have no idea why that's the case.

Realistically there's a fair amount of work and investigation I want to do to ensure the system is reliable and effective. So as long as you're happy for things to be occasionally unpredictable you're more than welcome aboard.