March 1st, 2004



Hey, Livejournal now has a feature where they can hold your public key and make it available.

My high security public key is here and you can get at it off my info.

I've also gotten in the habit of signing my emails (digitally). It takes no extra effort, and means that a recipient is able to verify that the email actually came from me, and wasn't tampered with. Not that I expect that to be the case, but hey, it doesn't hurt. There's also the fact, that as it becomes more and more standard practice to for the government to collect emails for intelligence gathering, the more important it is to secure ourselves from that intrusion. Since high power encryption is classified as a munition (to regulate it's export to other nations), then access to it falls in the category of the "right to bear arms".

And I'm not being fecesious either. The purpose of the "Right to Bear Arms" was to be able to arm ourselves against an oppressive government. The constitution was never designed around a large standing army that was better armed than the populace. At the time, Military Hardware was not far off from Civilian Hardware. Now that's not the case, and one has to wonder if allowing Civilians access to tanks and assault helicopters is a good idea anyway.

However, one area where we _can_ (sort of) compete with the government is technological weapons. You don't need expensive hardware to write and launch a virus. You don't need a supercomputer to encrypt your data- but it'll take a supercomputer to break it in a reasonable time. I think the right to bear arms has to be extended into the "Right to Bear Tech". Access to information processing tools is as key a right as any other in the Bill of Rights. Access to information is key; the right to tech is a combination of the right to bear arms, freedom of press, freedom of assembly.

It should not be impinged upon.

Hey look! It works!

I finally got the XML-RPC server working! What does this mean?

It means ChainRPC (formerly ChainChat) is ready to hit into the serious development. Over the next few days I'm going to get the basic Chat interface and logic done. I'll also implement connection sharing.

I've come up with a few other things that I want to use ChainRPC for. In addition to traditional filesharing, I want to let it serve as a BitTorrent tracker (and have a specialized FileShare for Torrents only). One thing though that I think can be _really_ groundbreaking, if I can get it working- this is a doozy of a project in itself- TCP/IP RAID. Yes, that's right, a Redundant Array of Independant Drives that operates over the internet. The available storage increases with every user connected- and some encryption is used to keep your data private.

That's a much later extension of the project though. First, the chat service.