Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:1
· Slash
· Slash
· More on News
· Also by Krow

Current Slash Tags

posted by Krow on 12:27 PM March 24th, 2003   Printer-friendly   Email story
News
Keep in mind that the type="op" is the syntax that is saved. Most have multiple forms. Also keep in mind that to use links you need to have Slash::Relocate installed and Slash::Blob. For image and file uploads all you need is Slash::Blob.
Read one for the entire list:
Links: Title is optional. Slash::Relocate autofills it with the HREF.
<SLASH HREF="href" ID="id" TYPE="HREF">text</SLASH>
<SLASH HREF="href" ID="id">text</SLASH>

Stories: If Title is not filled in they it will come from story's actual title.
<SLASH TYPE="STORY" STORY="sid">text</SLASH>
<SLASH-STORY STORY="sid">text</SLASH>
<SLASH STORY="sid">text</SLASH>
<SLASH-STORY STORY="sid" TEXT="">
<SLASH STORY="sid" TEXT="">

Comments: (not completed) title is optional or comes from the title of the discussion
(DISCUSSION filled in automatically)
<SLASH TYPE="COMMENT" COMMENT="cid" DISCUSSION="id">text</SLASH>
<SLASH COMMENT="cid" DISCUSSION="id">text</SLASH>

Journals: (not completed), title is optional or comes from the title of the entry
(USER filled in automatically)
<SLASH JOURNAL="id" USER="uid">text</SLASH>
<SLASH TYPE="JOURNAL" JOURNAL="id" USER="uid">text</SLASH>
<SLASH-JOURNAL ID="id">text</SLASH>

User:
(USER or NICKNAME is accepted for op)
<SLASH USER="uid" NICKNAME="nickname" TYPE="USER" >
<SLASH USER="uid" NICKNAME="nickname">
<SLASH USER="nickaname">
<SLASH USER="uid">
<SLASH NICKNAME="nickaname">
<SLASH NICKNAME="uid">
<SLASH-USER uid="uid">
<SLASH-USER uid="nickname">

Image:
<SLASH TYPE="IMAGE" ID="id" TITLE="title">
<SLASH-IMAGE ID="id" TITLE="title">

File:
<SLASH ID="id" TITLE="title" TYPE="FILE">Some text</SLASH>
<SLASH-FILE ID="id" TITLE="title">Some text</SLASH>

Page Break:
<SLASH TYPE="BREAK">
<SLASH-BREAK>
(I am posting this here instead of on a comment because the lameness filter keeps catching me... Hahaha)
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.

Current Slash Tags 10 Comments More | Login /

 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.

  • (I am posting this hear instead of on a comment because the lameness filter keeps catching me... Hahaha)

    If THIS doesn't prove the lameness filter is too tight, I don't know what does. :-)

    How about a [code] option in the pull down (instead of Extrans)?

    --


    "How about you interface with my ass? By biting it!" --Bender
    • To be honest extrans gives me a headache :)

      But the lameness filter squashed me for too much whitespace. To be honest I am more likely to just delete the filter for this site.
      --

      --
      You can't grep a dead tree.
      • Bad idea. Perhaps it could be loosened up some? Deletion is an open invitation to ASCII Art, etc.

        (Interestingly enough, it bit me when I tried to post this. A subject of "YIKES" triggers the caps filter.)
        --


        "How about you interface with my ass? By biting it!" --Bender
        • How about an override mode of the filter(s), based on seclev and/or karma?
          --
          lottadot [lottadot.com]
          • Seclev - an excellent idea.
            Karma - a BAD idea. :-)
            --


            "How about you interface with my ass? By biting it!" --Bender
            • What about, the higher your Karma, the more leniant the filter is, and if your seclev is high enough, it's disabled all together.
              • Well, two things:

                SECLEV has to be set by a site operator (or, as we used to call them back in the good old days, a SYSOP). As such, karma is not relavant or related to that - you have to DECIDE to give someone access to that feature.

                KARMA is something anyone can aquire - known, trusted, or not. ALL the trolls on slashdot start out by whoring an account for karma until they hit the cap - then, they post trolls or flood stuff until the account is drained. Lather. Rinse. Repeat.

                Basing the looseness of a filter on Karma is maddness for this reason, in my humble opinion, but I'd LOVE to see a way to exclude filters based on seclev. This would allow us to give a sort of 'trusted' status to friends, or people we know aren't going to abuse such trust, without letting the system make the decision for us.

                Right now, I use the author flag that way to give unlimmited moderation to a select few. Not the best use of it, but it works. I'd like to see some logic in the filter like 'if seclev =>1 then !filter posts' so that I have a choice there as well, or perhaps a 'not filtered' checkbox for trusted users.

                --


                "How about you interface with my ass? By biting it!" --Bender
                • Yes, I realized karma can be whored.
                  That's what moderation and banlists are for.

                  But if the system is automated by virtue of karma, then the website's admin *doesn't* have to *do* anything. It's less overhead for them. The people who have good karma, those are probably your most active people on the site, and most trusted, so you don't want to inconvenience them with making it a friggin pain in the filter ass to post a simple message.

                  Re: seclev

                  Personally, I *hate* the seclev system. It's too limited.

                  I'd
                  --
                  lottadot [lottadot.com]