This is not the kind of thing one wants to see from an anonymity network. From forum.i2p.net:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Preliminary news about downtime Those of you who frequent the IRC channels will already know this, but many probably don't. 1. The conditions ================= On January 13, Sagonet, where www.i2p (== dev.i2p == squid.i2p) is located, experienced a power issue in their datacenter. This left some of the servers offline, until their owners issue remote restart commands. I have no way to issue a remote restart command for www.i2p, since I don't have login credentials. I have exchanged some e-mail with Sagonet folks. They did check the router which the server is connected to, and it seems OK. They did check the server, and it's online at a login prompt. But they cannot help beyond this with the server, and it's normal too. You don't restart your customer's servers at the request of a complete stranger. 2. The implications =================== This means that the "public facade" of the I2P project is down for now. The network itself is fine. This forum continues to operate, because it's hosted separately by cervantes, but when cervantes has to change IP address (not sure when) there's no way to update the DNS entry to point at this forum, so it may be lost eventually, and may have to pick a new name outside I2P. Short of luck (e.g. a cron job left by jrandom restarting the server) there appears to be no way to get the old server back into service, and no way (short of jrandom stopping by and supplying login details) of making full use of it again. As such, a new server is needed. 3. The changes to expect ======================== A new server will be found, and will be located at a different DNS name. It will probably run a web server and a version control server. I have the necessary files to restore the website, but not their change history. I also have I2P sources, but not their change history. I do have the complete change history for Syndie, since Syndie uses monotone for its version control, and every Monotone repository contains everything about a project. Without the old CVS server becoming usable again, we cannot probably rescue the complete change history for "i2p" and "i2pwww". Since CVS as a centralized solution is a poor platform for projects like I2P anyway, we might just as well pick a new version control system, and import the last jrandom-signed source tarball into it. I will need to talk with more people about version control. I'm naturally inclined to pick Monotone (distributed development and strong authentication are benefits, inability to host a repository on an HTTP server is a shortcoming). I've been also asked to try out "darcs" and "bazaar". I am testing them. I have received an offer to host the website by someone on the IRC channel (I will not be disclosing their nickname before asking their permission). Perhaps that person can host the version control system too. What they cannot host, is an outproxy service like "squid.i2p". If providing something like "squid.i2p" is required in future, I guess the requests can be accepted by some I2P server, and automatically directed where they truly belong, into a network dedicated to outproxying, namely Tor. The release process will need to change. Releases will likely be hosted inside I2P, on multiple servers. Instead of getting signed by jrandom, they'll be likely signed either by zzz or myself. We'll describe in more detail when a replacement website gets up again. You can check for info either here, on http://zzz.i2p, http://stats.i2p or http://complication.i2p . Sorry for the major confusion. It was not within my ability to foresee. Complication. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHjbwp+h38a3n8zjMRApHHAJ4rj7GmpOPEAkSBqWyTMo6hDyl28gCfcMr5 55qU3aePBIz/vFE9y6Cq/OI= =W0Ql -----END PGP SIGNATURE----- -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
