Ah…
Bah someone want to remind me I have a blog here…
Anyways, Time to get onto the real subjects. Installed XP on my system again, boy was that a challenge… NTLDR decided to bite the dust after the first part of the install process, took me 2 days to figure that out… The reason was because XP was on K:\ and NTLDR was on C:\ along with Windows Vista… so I had to reinstall the Vista Bootloader and add XP to it, it worked! So here I am on Windows XP, man is this shit ugly! And the performance is moot, Vista is far more stable and reliable then Windows XP on my system and runs better too!
Time for an update on quantumRadio, its progressing pretty well (ok I still have a shit load of work to do…)… Yea that’s about it on the qR front…
Ok RazorIRC’s time to shine. I’ve started work on RazorIRC again, defiantly going to use Lua for the scripting engine, I’m also going to provide a converter to convert mIRC scripts to RazorIRC Scripts, though at the moment I have no clue how I’ve going to do it. While I develop Razor’s script backend I’m going to have to write the script database backend on the razorirc website, along with the user system (used for another feature of Razor) as they work hand-in-hand. Scripts that are in the RazorIRC script database will be able to ’self-update’ with the built-in Script Update Engine (SUE for short… ha sue…) that’ll be part of the scripting backend, SUE will be based around the update system we’re going to use to update the actual client, all custom in-house systems.
There’s also another more advanced feature, one that’ll make use of the RazorIRC website’s user system, we’re going to be working on our own chat protocol that’s loosely based on IRCX, the server will use a central user database (our website for our official server) and will allow you to send private messages to offline friends/contacts, user profiles, reserved nickname (this means no nickname changes) and avatars, and on top of that an IRCX layer so that IRCX supporting IRC clients can connect and chat (When an IRC user connects we plan for it to look and act like nickserv/various other irc services, this should solve the issue of nicknames). The name of this protocol? EdgeChat, yea I know it’s using Razor’s codename and that it’s a direct reference to RazorIRC, I’m short on names…
So I bet this question has popped up in your mind, ‘How is people wanting to use your new protocol going to have their own user system used instead of yours?’ simple, the first release of EdgeChat Server will also include a way to interface with PhpBB3, IP.Board(This may or may not come, someone needs to buy me a damned license!), Ruby on Rails plugin and a standard interface that you can modify to use whatever system your using. 
We’re primarily going to support PhpBB3, a generic php5 interface and Ruby on Rails with the first release though, all you’ll have to do once you get the interface up and running is point to your site in the configuration file for the server Now if you want to use our user database you will need to acquire a developer key/administrator token which will allow you to link 1 personal server to our database, you will still be the Server OP, no one else (unless flagged by YOU, these flags will be stored locally next to your server install in an XML like file) this way you still have full control over the options and settings of your server.
Our initial version of EdgeChat Server will be written in C# using the .Net 2.0 SP1 framework, it will be a GUI application that can be minimized to the System tray, if EdgeChat after the initial release we will be working on a native binary for Windows and Linux written in C/C++ or Digital Mars D, either way the release after the initial version will be a demon with a GUI monitor (separate executable from the server) the GUI monitor will be Windows Only but it will also be able to monitor remote installations via SSH.
I think that’s all…
Matt.