Sorry about the 1 hour and 11 minutes of downtime. My host apparently made a typo on their core router, which basically killed their entire network. Site will probably be slow for the next few hours, but should be back to normal soon. Before the downtime, I was working on moving everything over from nuclearscripting.com, which expires in the next few weeks. I'll hopefully be able to finish that tomorrow. Sorry again about the downtime.
Sorry for the continued delay. I suppose my lack of IEMs (went to Bestbuy recently, but they didn't have anything that looked good) has caused me to drift away a little.
The past few days I've mostly been doing a few security updates after mod_security started (and still is) catching an attempted exploit. There hasn't been any issues with the exploit (it fails every time) but I think I might add a ban system to ban the IPs that are attempting the exploit. The bans shouldn't be noticeable, as so far the IPs that have been involved haven't downloaded anything (builds, user uploads) at all in over 6 months, nor have any related IP addresses.
Moving along, personalized builds haven't had much work recently, though I hope to start working on them after I get my build back up and running.
A final thing. When testing a few things, I happened to notice something odd. Can a few people test going to http://chrisjs.com/a.php and see if there's any reference to ABi? If there is, can you post a comment and include your operating system and browser (include browser version - ex. Firefox 3 beta 3, not just Firefox; IE7 instead of IE) so I can figure out if this affects others?
Just a few updates. My site is now having all the mail sent to Gmail instead of my host, since it seems easier to keep track of it all. Unfortunately, this results in a slight problem - the svn updates won't be recorded, meaning that auto updates will be broken for a few days while I figure out a way to get around the issue. I'll manually update the build around 10:00 AM EST each day, around 4:00 PM EST, and around 10:00 PM EST. I can't say for sure how close it will be to those times, but I'll try to keep it updated at least two or three times a day.
In addition, one of my other domains, nuclearscripting.com, expires next month - March 18. Since I don't need it, and nothing's really been done to it, I plan to let it expire. The major impact that this will have is all the links from there will stop working on that day. I haven't look recently, but I believe the main things that are there are just copies of the OF, so it shouldn't be too much of a problem. However, within the next few days I plan to move all the needed files over to this site, take nuclearscripting.com down, and replace it with a message that the site will stop working on March 18. The message will include a link to the file on this site, so hopefully it won't cause many problems.
As I mentioned a few days ago, I managed to kill my Sennheiser CX300 by having it plugged into my computer and accidentally having one of the earbuds laying near my pocket - went to get up, ripped the wire. Luckily, the other earbud still works, but it doesn't sound nearly as good. A few people have recommended replacement IEMs, and depending on what Sennheiser says about repairing them, I might take a look at some of the replacements.
Patches. There's quite a few patches that I need to update, which I plan to do either tonight or tomorrow. There's a possible patch I might add to turn off the WPS after the backlight turns off. Back when the reduce power consumption patch was being tested, battery power lasted up to 15% longer when not in the WPS.
Personalized builds are getting there I suppose, but as I said before, I'll mainly only be working on them when I get a chance. Users who donate will have higher priority, but even so, it may take a day or so before I get the build working. If anyone has any patches they'd like added to the form (or any other suggestions) feel free to let me know.
I think that covers everything for the moment 
Well, there goes my CX300s. Had them until September until I accidentally got up without realizing they were partially wrapped around me - left earbud wire went snap at the base. Decent wire inside them though.. Anyway, I'm trying to figure out which IEMs to get - if you have any suggestions, let me know.
Anti-aliased fonts are now fixed and should be working properly, after kugel gave me a sync'd patch that seemed to work a lot better.
All fonts from http://savannah.gnu.org/download/freefont/ were converted into three different sizes: 15, 10, and 8, and can be found at http://chrisjs.com/fnt . I plan to implement a way to have fonts converted on the site, in case any other ttf fonts are wanted.
Just a few updates on personalized builds. Even though I'm not officially compiling the builds yet, I have compiled one for testing purposes. A few things to note:
The old wps patches are now removed from the form - it's either viewports or nothing. In addition, the custom list/menu patch is going to be removed rather soon, as that seems to have multiple bugs in it, and it's a closed patch soon to be replaced by FS#8457.
Another problem. Even with a perfect build (no failed hunks, etc) it still takes about an hour to get the build ready, add patches, and compile. Even though I haven't officially started, 7 requests have been verified, which would take around 7 hours to do. Seeing how much time this would take (both real and cpu time) I'm most likely going to have to separate things a little. Even with ads (oh boy...now we're talking about money..) I'm not getting a whole lot of money, and compiling only 7 builds on the server would most likely force me to move to a different hosting plan because of high resource usage.
As of right now, all donating does for you is lets you view the site without any ads. Once I get personalized builds ready, donating (only one time needed) will also get you higher priority in terms of having the build compiled. Mainly, the build would be compiled on the server, while users who don't donate would have their build compiled on a separate computer at my house. The main advantage here is that the builds on the server can be updated from where-ever I happen to be, while builds at home could only be updated when I'm at home. In addition, since I'm already busy with my build, school, etc., the builds compiled at home would only be compiled/updated when I get a chance, while builds on the server would be compiled/updated as soon as possible.
--
Comments on any of that? I figure this way, personalized builds are still free, but I'd have a little extra money for hosting. Also, for those wondering, donations and money made from ads are only used to pay for the site and hosting, not anything else.
The anti alias patch is in my build, but I haven't ported any fonts. If you want any aa fonts in the build, link me to a ttf font with a license that'd permit it to be used in the build.
Just a few updates...
The font issue is fixed - there was an issue in one of the files that caused the menu font to not change, which caused problems for some themes. Also, there's been some progress in USB support - apparently both reading and writing now work, but there are still a few problems.
For two people that were testing (gevaerts and rasher) it's been reliable, though there seems to be an issue reading from the MicroSD card. Because of the chance of problems that could occur, I probably won't add it until I test it thoroughly, just to be on the safe side. Apparently, there was a report of it cutting of the last character of all filenames, and hosed the filesystem, so if there was a bug, it could be rather bad.
I haven't had a chance to work on personalized builds today, but it seems that all the information is being saved properly, the verification email is being sent, the builds are being verified without problems, and I'm receiving the verification email. For the most part, I believe I need to integrate it into the site, get automated compiling working, allow users to update the build, and allow users to change the build. Automated compiling would probably be done last, due to the massive amount of time it could take - and whether it will be possible. For now, changing and updating the build could be done by emailing me (I'll set that up either tomorrow or Monday), except that'd also mean that it'd be done manually. Integrating it into the site probably won't be hard. Slap the site design on it and have the downloads tied into the upload script.
Come to think of it, I need to work on the upload script a little. Would it be better to have the link for it http://chrisjs.com/upload, or http://chrisjs.com/download? /upload would make sense for uploading the files, but /download would make sense for those downloading...maybe I'll allow both to work.
In a little over a month, I need to start paying for hosting again (I originally paid for a year, because of a promo code). I've gotten enough money from donations and ads that I should be fine until July, so that hopefully won't be a problem.
Just a few updates. Personalized builds now need to be verified before I start working on them. I've mostly got the verification script finished, so I could probably manually process a few requests soon. Little bit more testing, but aside from that, it's ready - except for automated compiling. Link is http://chrisjs.com/custom.php for those wanting to test it, but keep in mind, I currently am not compiling the builds. If anyone finds any bugs in it, or has any suggestions, let me know in the comments.
