SVN is down

[DPyro]

I can't access nemebean.com, no svn checkout for me

[foolsh]

Yep saw a post on reddit showing off Coldest.. traffic must be killing the server.
First thing I did was look for the source code early this morning.
I'm home from work now and..
sigh... can't even reach it with ping.
Guess I'll have to wait.
Unless someone has a tarball they could share.. you know just to hold us over till svn is up again.
Maybe the addition of bots would be a good place to start mucking in.

[Cybertron]

Actually it was just down.  Completely random coincidence that my ISP decided to die at the same time as all of the traffic.

Should be working again though.

[Tapio]

...And it's down again. Several days now I think.

EDIT: I'll take this time here to bash SVN a bit. This situation is one of the reasons why distributed version control systems (such as Git and Mercurial) are superior to centralized ones. When a distributed system's "central" repo goes offline I can still commit stuff, examine history, do branching and merging and everything in my local playground. When the official repo comes back online, I can just push my changes like nothing was wrong. Here with SVN I have a commit ready, but since I cannot commit it, I really don't want to code more since that would make it harder to create atomic commits later.

[Cybertron]

Yeah, I'm having to tunnel connections because my new ISP blocks HTTP.  The tunnel went down over the weekend for whatever reason.  Clearly I need a better solution.