Slash Boxes

Slash Open Source Project

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • Uhhmm, this is something that would be very very useful. Anyone knows where's the code for that version that worked with Slash 1.0? I'd love to try porting it to Slash 2.2...
    • I don't think it would be hard to do, the issue I keep thinking about is how do you handle the relationship of story to group? Maybe do section->discussion_title with comments underneath it?

      You can't grep a dead tree.
      • by J'raxis (2959) on Saturday November 17 2001, @02:23AM (#3691) Homepage
        That makes most sense. The newsgroups could be something like, slashdot.features, slashdot.yro, etc. In each group is a top-level post, the story, and all comments are replies to that. A comment ID would be analogous to a "Message-ID" header, and used in the "References" header for threading. What belongs in the "Subject" and "From" lines should be obvious; although if Usenet requires an RFC-compliant email address in the "From" line, this could get tricky... maybe default to “” Moderation could just be an extra "X-Moderation" header, or appended to the subject in parentheses just like it is on Slash sites.

        Remaining questions: Should the Content-Type be text/html or should everything be reduced to text for news readers? I know I hate HTML email, Usenet would probably be just as bad. Moderation could possibly be done through control messages ("cmsg moderate [cid] [value]"). Posting and replying should not be difficult, just make sure you strip out the client-assigned Message-IDs and replace with correct comment IDs. The References line would be correctly set by the client to the replied-to-comment’s Message-ID.

        Of course there’s plenty of routes for abuse here, multiposting, crossposting, munged IDs, identities, no authorization on a per-post basis. All this stuff would have to be checked on the back-end for correctness, and an appropriate error status returned ("501.2 Slow down, cowboy!").

        The analogies seem simple enough, now as for the coding in Perl... :)

        Liberty in your lifetime []