New IRC Server

July 2nd, 2009

We wanted to thank Shawn Boyle for setting up irc.dod.net and our chat page. For a while now Shawn has been managing the Project DoD ventrilo server, and when we started talking about running a FreeNode IRC server, he stepped right up. When we never heard back from the FreeNode folks Shawn setup an new IRC service for our users, and we’ve been using it for a few months now. We plan on running the service on more servers soon, so stay tuned.

Project DoD Needs New Hardware

June 27th, 2009

It’s time for new hardware. Once again we have pushed our current hardware well beyond its warranty or any reasonable meantime to failure. We are out of memory constantly, we are out of CPU frequently, and we are seeing I/O storms that bring the box to its knees. If none of this matters to you, then consider the fact that we are pushing seven years on the original hard drives for our server. Hardware failure will happen very soon, and like our last hard drive, it may happen next time we loose power to the box.

We have been working for months to find a great deal on hardware, and we think we’ve found a good balance between total junk at a low price point, and high quality hardware at unreasonable prices. In the past we have used one primary server for everything and another secondary server for backup services. We are changing this model completely to be more secure, to reduce downtime, and to dynamically expand and contract with load. We are calling this new model a “cell“, which we believe necessary to build the type of infrastructure outlined in our mission statement.

Project DoD is looking for 30 people to each make a $250 tax-deductible donation towards new hardware. If some of you cannot make a $250 donation, then consider this: Project DoD is also looking for 250 people to each make a $30 tax-deductible donation. In short, we desperately need your financial assistance. So please make a donation to our new hardware fund. You can view how close we are to our goal, and the specific hardware we’re looking at on the donations page.

Finally, if you think there is anything you can do to assist us with fund raising please let us know. This is a very hard year for non-profit organizations because of the economy, and while we’re sure you’re sick of hearing about the economy consider this: 2009 is the first year in nine that the collective has been unable to support itself. What’s more, this year has been our most active ever. It’s unfortunate that we need to replace our hardware now, but we also believe we are well positioned to execute some very exciting and revolutionary plans if we can pull through. So please stay tuned for more information on what we’ve been working on, and how it could change collective hosting in the future.

Nagios Monitoring

June 19th, 2009

We wanted to extend a thank you to Dave Rawks for helping us with our Nagios monitoring. Nagios is an highly configurable enterprise-class monitoring service that puts our old Perl scripts to shame. Nevertheless, it’s non-trivial to configure, and even the documentation warns that Nagios is not for the weak at heart. As we scale, this new monitoring service will too. The whole collective should benefit as a result of Dave’s work, which has greatly improved our response to problems at the granularity of a single service on a single machine. Thank you Dave, your name says it all.

rsync Binaries Installed

June 19th, 2009

Upon request we’ve installed the rsync binaries on Project DoD’s servers. We are not, however, running an rsync daemon.

Donations Update

June 9th, 2009

We’ve been working very hard at finishing our donation system so that it does everything we ever wanted it to. There has been lots of behind-the-scenes work on restructuring our user databases so that the idea of a “doduser” is separate from a “user”. The former being a login account that allows people to make contributions through the account manager, and the latter being a real user on our servers with hosting or mail access.

We have also made roles for each user that allow them to be a volunteer, a member, or any other role we define in the future. This has taken a considerable about of work to change all of our source code, and we still have a bunch of work ahead of us. Nevertheless, all of these changes should be done in a few weeks.

For now, we have added a new page off the donations page that allows you to view our financial records over the history of the organization. We hope you find this interesting and informative. I should say that in our early years we used to just use our bank records as documentation of our Expenses. A few years ago they started archiving those records so that we didn’t have access to them in digital form. It was around that time that we started keeping our own records, but some of the earlier years are sparse. Remember, we’ve been around since 1998, and there was a day when we used to pay $850.00 a month for a T1.

BTP page done and DEFCON paper submitted

May 21st, 2009

That’s right, the BTP page is done and our DEFCON paper is submitted. We should hear back from the guys at DEFCON by June 15th about our paper. Either way, it’s looking more likely that we will be releasing the code to the public in August 2009 no matter what. The site is invite only for the moment to control the release, which should also help us flesh out some community needs before August.

We’re excited to show the world what we’ve done, and allow the code to evolve into something even better. As some of you know, James and I put this project on the back burner a long time ago, so we have very high expectations that the community will step up and take over development. If you’re interested in leading development on the BTP code, please let us know.

BTP Mac client done

May 17th, 2009

I should have posted about this a while ago, but the BTP controller program for the MAC is complete, and it’s impressive. The speed is amazing compared to the Windows controller. This comes from removing much of the abstraction that the AHK code puts on top of direct frame buffer access. I’m grabbing the full-screen bitmap once each round (which is set at one-tenth of a second, but tunable), and then checking against that bitmap for each frame. The speed increase from just this makes the frame color changes look like a quick flicker. While I could make this even faster by only grabbing enough buffer in the (x,y) to read the frames, it adds a little more code for little benefit. That is, the performance greatly exceeds my wildest expectations, and if it ain’t broken don’t fix it.

There is still a bit of a bug around capturing key-up events from the real hardware, but I haven’t been bothered enough to fix this. Some brief investigation seems to indicate that the buffer for events on the MAC is shallow, but I don’t know if that is actually the problem, and if it is, if I can tune it.

This code is not yet, and may never be, ported to big-endian architectures. There may not even be a need for this on the PPC anymore since the 3.1 patch. Like everything else related to the BTP code, we will be releasing this around our talk at DEFCON if it’s accepted.

Mission Statement (Request For Comment)

May 10th, 2009

As we mature, so does our organization. I’m throwing out the mission statement ideas that Dan Mays and I have been tossing back and forth over the past few weeks. Think of this as scratch paper, and please comment or suggest revisions if necessary. We are trying to form Project DoD’s future vision. These are ambitious goals, and it’s our “projects” that should set much more actionable and realistic objectives towards these ends. So, welcome to design by committee: please comment and correct this mission statement is _not_ written in stone.

GOALS:

===

Project DoD is a charitable 501(c)(3) nonprofit organized to:

(a) Sponsor or perform research and development of technologies that help all societies create a more just and equitable future. We firmly believe that freedom, privacy, security, and economic stability are fundamental human rights, and that a focus on any one goal should not come at the expense of the others. That is, to create a future where humanity is free of coercion, censorship, exploitation, abuse, poverty, and all other conditions through which the powerful impose their will on the less fortunate, one must enjoy freedom, privacy, security, and economic stability in equal measure. We are seeking to

(b) establish a globally distributed network of organizations and individuals committed to building an infrastructure that meets the objectives of (a) above. This infrastructure should be resistant against the collapse of any one supporting organization, the assault of any government, organization, or individual, or the physical destruction of any one part of its network. We believe such an infrastructure should be participatory, and that its members should be empowered by a fully democratic decision making process. However, such an infrastructure must also be resilient against mob-rule and vanguardism. We shall also

(c) resist any threat, social, legal, physical, environmental, or otherwise, that seeks to compromise the principals of either (a) or (b) above. That is, any threat that seeks to undermine either fundamental human rights, or compromise the mechanism we believe necessary to ensure those rights, must be challenged and neutralized. We are committed to engaging such threats using both legal and technological methods, so long as the means of engagement does not also violate principals (a) and (b) above.

Project DoD believes that it is often the most impoverished members of society that suffer violations of their fundamental human rights. For this reason, historically, we have been slightly more focused on empowering the underprivileged through our projects. Nevertheless, our vision is for all members of society, and will never be limited to just the poor. Please be aware that Project DoD’s mission is intended to be axiomatic, but broad. Each particular project that we work on has much more realistic and actionable objectives that serve the ends in this mission statement. Please find out more about our projects and how they are helping to build this future.

===

NOTE: this post was also sent to the Project DoD collective mailing list.

Project DoD is an official 501(c)(3) nonprofit

April 30th, 2009

Well this news is about a year late, but we thought we should give a shout-out to all the members that made our official nonprofit status possible. As many of you know, Project DoD applied for 501(c)(3) public charity status in 2003 after a good five years of operation. At the time we didn’t have the financial records to use our previous five years to pass the public support test, which meant we were put into an advanced determination period by the IRS so they could put us through the public support test at the end of another five year period. Well, in 2008 we passed that test and received documentation by the IRS stating that we are now an official 501(c)(3) nonprofit without any of the restrictions on organizations still in their advanced determination period. We want to thank everyone that supported us over the past 11 years, and we wanted to assure you that we are determined to forge ahead with our purpose. We have a bunch of technology and fund raising projects in the works, so stay tuned.

Updated my resume

April 28th, 2009

It’s been a while, but I’ve brought my resume up to date with my current experience, my objectives and qualifications, and my personal development. It’s getting a bit too long, but it’s all relevant and I can’t think of anything I want to cut. I am usually not trying to sell myself, so any prospective employers can swing by and read what they think is relevant. Handing this beast out is another story all together.