SoylentNews

I'm going to simply write this quickly now. I have had very long discussions with a member of the community known as kolie who has been negotiating to try and keep SN operational, and help provide a realistic plan for both rebuilding the site, and migration. I was approached after the shutdown post was put up via public contact information. He has offered help in the form of hosting, capital, and helping coding a replacement for rehash. He has convinced me that there are enough people in the community that it might be possible to pay down the technical debt.

I was asked to formally take the gun off SN's head, since it doesn't help recruit volunteers if there's a death sentence.

I am more than a little reluctance to do this, simply on the basis that there has been a long history on this site of saying "we'll do X", and then X never happens. The situation was also discussed prior with Matt, and quite a few other people before I finally made the decision after it became clear to me that the situation had become completely untenable. I spent weeks looking for an alternative before I finally resided myself that there were no other viable options. But sometimes you can be wrong, and sometimes you can get outside help.

One of my cited reasons for shutting down SN was that calls for help were left unanswered. However, said call finally got answered and came at the 11th hour, and as an unsolicited DM by someone who wanted to see the site go on. We have been discussing this at length since Monday, in a conversation that at this point has been longer than everything said in a private, staff channel for the last six months. So, I accept the possibility I can be wrong. More specifically, I hope I am wrong.

So, ultimately, I will put my faith in someone I have never met before. It might be absurd sounding, but that is ultimately how SN started. A bunch of people who never met coming together to make a replacement for Slashdot. I will take steps to keep SN going past the 30th. This may involve the legal entity changing, as the PBC already voted to dissolve itself. I will write more on this next week, since frankly, I need time to sit back and reflect. I also need to write some emails.

The staff have told me that they will not work with me going forward. For my part, the feeling is mutual.

There are also the facts that I listed in the shutdown letter. SN's codebase is effectively unmaintained since the departure of TMB. I've already discussed the state of infrastructure to death, but there's an objective truth here: SN's VMs were exposed to the open Internet on end-of-life operating systems for years and the database cluster had been in an extended failure with corrupted log tables. As I see it, the staff allowed SN to degrade to the point that it was about to entirely fail. As I understand it, they see me as acting rashly and irresponsibly in attempting to address the situation. I freely admitted I could have done better.

At the end of the day, the only worse outcome than a volunteer shutdown is one where the site is either compromised, or lost in a crash. SN was one hard shutdown from an unrecoverable cluster failure.

That is not a viable state of affairs. That is a liability nightmare that at the end of the day the PBC is responsible for, which was the basis on which I intervened.

Finally, I'm only still here because SN has never been able to accommodate people leaving, especially as no one has historically been willing to take over legal responsibility for the operation of the site. I resigned three years ago. SN needs actual governance by people who can ultimately say that Z, Y, and X need to be done, and have the ability to either have it done, or can help raise the money to help get it done.

So, I guess we'll see if miracles happen twice.

~ NCommander