Comment A secession plan. (Score 2) 2219
We have the code... A new slashdot clone could be created but would lose the audience. A few important problems with a replacement site:
1) All current content locked up and owned by dice. The new site could point to the old articles and discussions allowing them to be viewed in archived form. Dice could shut this down legally or play cat and mouse at obfuscating the links.
2) user iDs would be lost. Here's a solution. New site starts ID numbers at 2,000,000 or whatever. Older names and IDs are reserved and can only be re-registered thus: Login with prior slashdot ID, use a random number or string to verify. Enter this code in the user journal, new site verifies matching code and opens up old username on new site. This is a problem for those who've lost their passwords but they couldn't recover on classic slashdot anyways.
3) Who runs the site and selects articles? If enough old timers get together and agree on management the new site (let's call it "backdot" for now) enough momentum could be built to drive over a large part of the community. This could splinter however. It needs enough prominent user support to work.
It's possible to move much of the user base somewhere else but would require a lot of cooperation. Herding cats comes to mind.