Wikileaks needs hacker volunteers

It would be nice if they said how much money they need and what their expenses are.<p>I also wonder if they could work with a recognized non-profit in order to make gifts tax-deductible (e.g. give them money to EFF, then EFF funds wikileaks).

I'm a big fan of Wikilekas, but I see several things wrong with this approach.<p>First, it's the way they ask for donations. They close the website and it's almost like "If you want Wikileaks, you have to pay". I don't think this helps their cause in any way. I remember seeing a banner while the website was still live, but that didn't last long.<p>Also, I don't think they reached a point where then can't hold the website online. It's not like it's new.<p>Like someone else said, they don't tell what their expenses are, nor how much money they need.<p>On the technical side, I don't see the need for having MediaWiki running. It's not the most lightweight application, and since most of the publications are done by the team behind the project, maybe having an approach like <a href="http://cryptome.org/" rel="nofollow">http://cryptome.org/</a> would make it less CPU hungry and would not depend on so many resources.<p>Since someone mentioned the mirror on Freenet, here is the mirror on the Onion land: <a href="http://gaddbiwdftapglkq.onion/" rel="nofollow">http://gaddbiwdftapglkq.onion/</a>

Here's a simple way to contribute - rate and comment on their Knight Foundation application:<p><a href="http://tinyurl.com/wikileaksknightapp" rel="nofollow">http://tinyurl.com/wikileaksknightapp</a>

anyone know what kind of development work do they need ?<p>It would be helpful to know what are they looking for - and whether we can contribute, with our specific skillset

If you want to know more about the future of wikileaks, check out this talk from 26C3: <a href="http://mirror.fem-net.de/CCC/26C3/mp4-ipod/26c3-3567-de-wikileaks_release_10_iProd.mp4" rel="nofollow">http://mirror.fem-net.de/CCC/26C3/mp4-ipod/26c3-3567-de-wiki...</a>

There's a Freenet mirror of Wikileaks. That might help with the technical difficulties.

They should get their own ASN and IP ranges. Then they could start peering and heavily multihoming which would make the site more stable and save them money.<p>Also varnish cache would help.

It is too bad that they have to shut down access to the entire site to stay alive. I wonder if that will hurt their search engine rankings.

Perhaps they could switch YAWS from Apache? Also maybe a similar wiki-software, like Zotonic.

Well, I sent them email asking what they need for power/bandwidth/rackspace, to add a node usefully.<p>I doubt I'm the only person on HN who has large amounts of computing resources to spare. I suppose we'll see what's required to help.