3 ms·

Yes, getting a basic slashcode site up and running is top priority, according to the talk in IRC channel. They want to have it running today. Mediawiki site is

by pferde 13y ago

Yes, getting a basic slashcode site up and running is top priority, according to the talk in IRC channel. They want to have it running today. Mediawiki site is just a temporary thing.

davidgerard 13y ago
Have you ever run slashcode? IT IS HORRIFYING. It is really just ridiculously difficult to get running, really just ridiculously difficult to keep running, stupidly fragile to user-settable settings and the schema was written by Database Barbie. MediaWiki is a dream by comparison. I'm not sure what I'd recommend as a replacement. However, what I actually did when I last suffered Slashcode was replace it with WordPress and a suitable set of extensions (e.g. a submission extension). Which, for all its problems, didn't make me actually want to stab myself in the face repeatedly whenever I went to touch it in any manner whatsoever, including to post anything. The LessWrong codebase, which is a derivative of Redditcode, does pretty well for that site. https://github.com/tricycle/lesswrong https://github.com/tricycle/lesswrong Might suit a Slashdot replacement. Not many maintainers, could do with more.
- smacktoward 13y ago
  There's also Scoop (http://www.scoopdev.org/ http://www.scoopdev.org/), which came out of a late '90s exodus of disgruntled Slashdotters to a new site, Kuro5hin (http://www.kuro5hin.org/ http://www.kuro5hin.org/). They needed their own Slash-alike to run the site, and Scoop was the result. It actually ended up making more of a splash in politics than in tech -- influential early political blog Daily Kos was built on Scoop, and this led many other political discussion sites of that time to adopt it as well. (DKos migrated off Scoop a couple of years ago.) The quality of Scoop's code and the vibrancy of its development community can both be inferred from the fact that, in 2014, its FAQ warns you that it doesn't run well under Apache 2.
  - davidgerard 13y ago
    tl;dr a suitable replacement should have been worked on after the word changed from "weblog" to "blog".

by pferde 13y ago

Yes, getting a basic slashcode site up and running is top priority, according to the talk in IRC channel. They want to have it running today. Mediawiki site is just a temporary thing.

davidgerard 13y ago

Have you ever run slashcode? IT IS HORRIFYING. It is really just ridiculously difficult to get running, really just ridiculously difficult to keep running, stupidly fragile to user-settable settings and the schema was written by Database Barbie. MediaWiki is a dream by comparison. I'm not sure what I'd recommend as a replacement. However, what I actually did when I last suffered Slashcode was replace it with WordPress and a suitable set of extensions (e.g. a submission extension). Which, for all its problems, didn't make me actually want to stab myself in the face repeatedly whenever I went to touch it in any manner whatsoever, including to post anything. The LessWrong codebase, which is a derivative of Redditcode, does pretty well for that site. https://github.com/tricycle/lesswrong https://github.com/tricycle/lesswrong Might suit a Slashdot replacement. Not many maintainers, could do with more.

smacktoward 13y ago
There's also Scoop (http://www.scoopdev.org/ http://www.scoopdev.org/), which came out of a late '90s exodus of disgruntled Slashdotters to a new site, Kuro5hin (http://www.kuro5hin.org/ http://www.kuro5hin.org/). They needed their own Slash-alike to run the site, and Scoop was the result. It actually ended up making more of a splash in politics than in tech -- influential early political blog Daily Kos was built on Scoop, and this led many other political discussion sites of that time to adopt it as well. (DKos migrated off Scoop a couple of years ago.) The quality of Scoop's code and the vibrancy of its development community can both be inferred from the fact that, in 2014, its FAQ warns you that it doesn't run well under Apache 2.
- davidgerard 13y ago
  tl;dr a suitable replacement should have been worked on after the word changed from "weblog" to "blog".