SoylentNews - User contributions [en]

Historic talk:FeatureList

2014-02-10T18:08:30Z

Pr0ntab:

(Pardon my editing. If anyone is more familiar with wiki editing than I, maybe they would care to format this more appropriately. However, I would not appreciate any editing of my comments other than for format.)

;MODDING

:First: I recommend against allowing mods in any discussion in which you have taken part. Preventing mods only to "your comment chain" would be far too complicated to implement and there are too many potential holes to exploit if someone wants to cheat.

:: Technobabble removed --- I don't see why it's really a desirable feature. You're opening the door to people gaming the system by modding other comments in the topic that they don't like, in order to support the comments in that topic that they did make. If you mod all your enemies down, and your own and friends' comments up, you distort the whole picture. My opinion is no. It's just a bad idea to allow mods in the same forum you comment in. (Please understand that my intention here is to be constructive. I used to think this should be allowed on the original site too, but after giving it more thought I changed my mind.)

::: I understand where you're coming from; what I and others have experienced is that we don't bank mod points until such time they want to use them since they expire. Most of the time when I have mod points, I find myself annoyed that I can't contribute to a conversation that I'm now paying close attention to. Are you specifically concerned about an issue-poster who will hunt through articles once they have mod points to game the conversation?

:Second: I recommend against giving users the ability to mod ACs up. Why bother? They're ACs. Allow downmodding but not upmodding. That gives them incentive to create an account. (I realize this would penalize the occasional brilliant comment from an AC... still, I say: let them create an account.)

:: ACs do sometimes post very good content. Sometimes individuals mentioned in an article feel the need to post with some plausible deniability. I'd advise against this. Perhaps a feature might be to simply hide AC posts as a display option (but not the default).

::: "Sometimes individuals mentioned in an article feel the need to post with some plausible deniability." Regardless of the occasional "good" purpose this can be used for, this is called '''sock-puppet''' activity and is pretty universally despised in online forums. Encouraging this kind of behavior will not do your site any favors.

:::: I disagree. I feel that being able to contribute or add an additional detail anonymously (plausible deniability) is vital, especially because of the sensitive nature of some articles with respect to where people work. Remember that a moderator still has to moderate the anonymous post up, and moderators are aware that an anon reply to an authenticated post might be a sock-puppet if it looks strange or like someone is deliberately trying to sound like a second voice.

:::: Slashdot was not a site optimized for Facebook arguments about politics or DND. Even if you can "win" an argument with sock-puppetry; if you won an argument on Slashdot you have already lost. It's a site optimized for technical discussions and each post should be able to stand on its own merits and there are no winners or losers, just informative or bullshit; the only amplification (speaking from authority) should come from registered posts and reputation. That's why Slashdot allows some registered or high-karma accounts to post with more points by default. If there was some real weird conversation steering by a bad actor with sock puppetry combined with mod activity you're already talking about needing multiple accounts in good standing, and that takes resources. If it can be detected by the clustering analysis and investigated, then we could combat it. If it can't, then it's a sophisticated attack by someone with a lot of patience or money, and in which case I don't think we can prevent that.

:::: I think that a targeted attack that abuses the ability to post anonymously could just as easily be done without anonymous posting (and yet another account), so I think the value of being able to post something very valuable without fear of repercussion outweighs the ease with which someone might try to make their own argument seem popular. I'd rather fish the depths for a gem and take that "go ahead and post the master HDCP matrix, free speech is paramount" approach that Slashdot had than tell you to use a pastebin.

:Third: I do not think fractional mod points is a good idea. It adds unnecessary complication, decimal numbers use up more space in the database and add performance penalties, etc. If you want to make some mods worth more than others, make them worth more than one point. E.g., 2 points and 1 point rather than 1 point and 0.5 points.

:: You wouldn't store decimals, just the traditional modpoints times 2. The fractions are a UI detail and their conversion (and truncation) are a function of the code that prepares fetched data to be templated and rendered to HTML. The reason for adding this is so that the default rendering option still shows a -1 to 5 scale as before, but allows for Funny and Flamebait to be de-emphasized. It's really a matter of empowering the default, non-logged in view, which we can't ignore.

::: I know how it works. You are still adding needless complication. Regardless of whether it's "just display" or not, you are adding floating-point arithmetic that simply isn't necessary.

:::: We could change the range. But I like the idea that the score is in a 0-5 "stars" range. Familiarity and all. I'd like it not to go into double digits (0-9) at the worst. And you're making a bigger deal out of it than it is considering PHP and Perl have no issue with floating point vs. integer scalars (and the database wouldn't store it). This isn't something to get worked up about. What I'd like to hear is a solid argument against finer weighting options.

::: "but allows for Funny and Flamebait to be de-emphasized" Why would you want to de-emphasize them? I think Funny is well-deserving of a full point, and Flamebait, while sometimes misused, is still a worthy mod.

:::: Slashdot already allows for user-defined weights for rating types. I have seen some user journals earlier on from slashdot devs where they talked statistics on how top-level comments end up getting overmodded (they receive a disproportionate number of different ratings to value the unauthenticated user score). Seeing how some comments quickly shoot up in score, I think this is still happening. I feel this would allow for a bit more fine-grained control for users who don't value Funny as much as you might. (I'm one of them, I like Funny, but I think it gets steam-roll mod applied sometimes, like the Reddit effect you mentioned earlier)

:Fourth: I would give a lot of strong thought to some kind of means to limit sock-puppet accounts and especially sock-puppet mods. I doubt there is any perfect way to do it, but having many times been victim of sock-puppet mods, I think it should be harder than in the original version. It should also be made clear to users that sock-puppets are considered the lowest of the low by the community. (They already are, but it should be made explicitly clear.)

:: Perhaps a new requirement is a feature in the backend that uses cookies and/or IP/browser fingerprinting to cluster accounts, and then further watch for correlated activity among them to identify potential sockpuppet accounts. A manual adjudication process would be necessary. While multiple accounts would not be specifically against the ToS, the site would reserve the right to ban accounts believed to be acting in bad faith (trolling, spam, sockpuppetry).

::: I agree. I think a form in the user area could be used to register a "complaint" about suspected sock-puppet mods. This could run an automatic routine to find correlations to cookies or IPs (cookies is probably more reliable). If that is above a certain threshold, it could be forwarded to moderators for a review. Just an idea, but that would give users a way to complain, without incessantly bothering moderators, yet allow moderators to act if anything is real.

:Fifth: I recommend adding an "I disagree" mod, which would be worth '''+1''' point. :)

:: Only if you change it to be "Devil's Advocate" and conversely a "Groupthink" downmod at '''-1'''. These are more descriptive rather than opinion-based tags (even though they really all are) which are easier to metamod and force you to think about your perception of the community attitude, not just your own.

::: It was just a joke. I like the groupthink idea, though (a "Kool-Aid" mod). I think it might be abused though.

:::: Some others have already expanded on this list apparently :)

:Sixth: ''"What about not-posting in the thread where you moderated? Good or bad rule? Maybe if you really must post, allow cryptocoin paying for post?"'' '''HELL NO.''' People should not have more say just because they have more money. This is a '''very bad''' idea.

:: Agreed. This is a dangerous precedence. Also, I don't think it's a good idea to incentive-ize anything beyond low UIDs, more browsing options (site scraping, CPU-taxing searches), maybe auctions for popular channel names to be owner/editor on.

;KARMA (CHOPS)

:I really don't think mod points or karma should depend on user's customized point systems. Leaving it open to customized scoring could make your karma system vulnerable to cabals of users, unintended consequences, or a form of "elitism" (Good Old Boy Syndrome). It's been known to happen. There should be a clearly articulable standard that cannot be modified by users. Anything else is subject to chaos. If you don't give users a clearly defined standard, they won't know how to behave.

:: Note about the above: if what was meant was that it '''shows''' differently to users based on their custom scorings, fine. But the internal base scoring should not be modifiable by users.
:: '''Eeep edit conflict''' ... YES that's what I meant and I agree

:A Karma (or Chops) system needs to go above what the original system uses (only a few levels, with "Excellent" being the top). The current system allows people to receive massive numbers of positive mod points, but still remain at "Excellent" karma, which can be lost in a single day; they can find their karma at 0 if they are ganged up on by others and receive only a few downmods in a single conversation. Yes, it does happen. Karma should be allowed to accumulate (negative OR positive) beyond just a few points on either side of zero. It need not go on forever, but people should be allowed to develop some kind of persistence of positive or negative karma. That way somebody with a few years of good karma won't find themselves below 0 due to a single flamewar. And vice versa.

:: This already happens from what I understand. Karma isn't totally capped right now on slashdot; there's a functional limit for display purposes and mod perks. I think there's a weighting system where karma for everything older than a few months or so "sum from back then", capped at the functional limit, and then all the subsequent karma-affecting activity since then allows it to go above or below that number, and it's again capped at the limit for checks. And then they summarize the oldest month on some periodic basis into the new "sum from back then", but they again are capping it when stored so all the extra upmods in the past can't outweigh current downmods now.

::: I don't think they really do this. I say that because I have had many years of good /. karma, with consistently many more upmods than down, only to see it literally disappear in a single day, over a single discussion in which I took a "politically incorrect" position (about 5 downmods). I had to re-build it from scratch. I thought that was really pretty terrible: losing years of reputation in a single discussion. That should not be allowed, but was.

:::: They do do this. But it relies on an external script to do some stuff (it could be more nuanced on the slashdot in production vs. what's in the CVS). And I've done this too (got downmodded a lot), but have not experienced what you experienced. Or perhaps I posted enough other stuff that got upmodded subsequently that it didn't matter the next time I checked.

:: I'd like to continue using such a system so that you're given the ability to carry Chops above the "Excellent" threshold value, but summarization means that you can't "bank" good behavior limitlessly and it also cuts down on expensive database queries for long-lived accounts.

::: I don't think limitless would be a good idea either. But I also don't think big queries should be necessary. Just accumulate points in a field of the main user record. Allow the accumulation of a certain amount of points above "Excellent", or below "Terrible" (or whatever the low limit is... I've never been there). I don't see the utility of maintaining complex running averages, when a simple accumulator achieves most of the same goals, as long as you let it go somewhat above the top visual rating and below the bottom visual rating. (And as I mentioned before, I don't think the original site actually does averages, either.)

:::: What I'm hearing is that the summary-ization threshold is too low. Are you okay with it turning everything beyond "4 weeks ago" into a past total and starting point for karma (capped at 150% the display?). Let's say the display limit is "10" for excellent. That means you could have 15 upmods banked from a month ago, plus any recent upmods, and then need that many downmods to happen to you all at once to put you at zero.

:Care should be taken to avoid multiplication of karma points, either positive or negative. I.e., you should not receive more positive points for having positive points.

:: I can't think of a situation where this occurs as exists or proposed (except with sockpuppetry... )

::: I agree. I just thought it was worth mention because I had at first misunderstood your description of how reputation is scored. The "Reddit effect" is somewhat minimimized on Slashdot because comments don't move to the top based on their score. But on Reddit (if they still do it the same way) it is a serious positive feedback effect, in which mediocre comments can get shoved to the top if they get a few upmods early, while more insightful comments get buried in the noise. That's not directly related to karma (chops), but the effect should be avoided in any scoring system.

:::: Agreed.

Historic:FeatureList

2014-02-07T23:42:41Z

Pr0ntab: /* Requirements */

== Overview ==

I'd appreciate if everyone would just start adding or removing things they think need to be in the to-be variant of this site

Rather than isolate the things that slashdot already had (we should be familiar with it), let's just explicitly state what we want to see, with the idea that most of it is a copy or inspired by the original. But we can possibly explain, refine, or restrict our focus to the bits that matter.

== Requirements ==

* UTF-8 clean for anything that doesn't end up in a URL (i.e. tags, titles, channel names, user names)
** Of course, some combining marks would have to be filtered, and the resulting text round-tripped through NFD->NFC to prevent certain types of attacks against users or making text difficult to index.
* [http://blog.stackoverflow.com/2011/04/stack-exchange-partners-with-mathjax/ MathJax] support both in comments and in submissions. Mathjax is the math rendering engine used on [http://stackexchange.com/ stackexchange]. This will allow scientific discussion between us, people who can read math.
* Channels (like yro, politics, apple) as first class objects
** "Primary" channels that have DNS shorthand (http://apple.altslash.org/ being equiv to http://altslash.org/ch/apple/)
** "Secondary" channels that users could create and play editor that use the more verbose syntax (http://altslash.org/ch/baseball/) that is reminiscent of subreddits
** User channels (i.e. journals) as we've always had
* display user IDs.

* Submission queues for all channels with membership at the discretion of the channel owner; being able to submit also implies up/downvoting submissions and tagging
** Editors/channel owners only
** List of users who can submit
** All of my friends (for user journals)
** All users with mod status
** All registered users
** Everyone

* Articles are also first class objects
** Perma-link independant of channel
** Articles can be cross-posted to other channels by a channel owner (built into the UI if the editor manages more than one channel)
* Comment key features
** Comments are first class objects, just as before, just like articles
** Comments can be edited for a short period of time by owner
*** HOWEVER: Edited comments get a new ID and it links to older versions in the new one. This detail is made prominent to viewer if a comment reply happened before an edit.
** Allow alternate markup options (bbcode, markdown, wiki markup)
*** Provide a mapping to actual div and styles that will be applied, or HTML equivalent codes

* Allow moderation in same article that you've posted in; only disallow moderation '''to your own reply chain'''.
** You're obviously not allowed to moderate in your own accepted or posted article (treating all comments as replies)
** Does "reply chain" include parent? If not, how do we deal with threadjacking:
**# AC posts first comment on a new article (let's presume it's an upmod-worthy comment, not fristpsot)
**# I post my unrelated comment as a reply to AC's FP, in order to achieve greater visibility
**# I downmod the AC to -1
**# Now AC is invisible to anyone with threshold != -1 (including many with mod points and threshold=0, who would have modded AC up on his own merits)
**# Unless/until users with threshold=-1 and mod points happen by to rectify things, my comment is now the first thing most users see.
**# ??? ''(sorry, can't resist...)''
**# Profit!
***Actually, not just the immediate parent like I said, but 'all' ancestor comments. Otherwise as step 1.5 I just reply with an AC troll (which someone else will rightfully downmod), then in step 2 I reply to ''that''; now that the original AC first post is my comment's gp, so I can still downmod it.
** ''' Good point ''' you should be prevented from moderating any children ''''and''' ancestors of your posts (but sibling chains are still fair game)

* Moderation Engine
** Moderation tags only (default scores)
*** Offtopic -1
*** Interesting +1
*** Troll -1
*** Insightful +1
*** Groupthink -1 ('''New!''')
*** Devil's Advocate +1 ('''New!''')
*** Overrated -0.5 ('''new default weight''')
*** Underrated +0.5 ('''new default weight''')
*** Flamebait -0.5 ('''new default weight''')
*** Funny +0.5 ('''new default weight''')
** Users assign own weights to tags in the range -2.0 -> 2.0 with 0.5 increments
** System rounds x.5 towards 0 in comment spill / threshold logic, display capped at -1 and 5.
** A score for the default weights is saved for the comment for use by article spill (for googlebot or "load all comments" from anonmyous user)
** An optional cryptocoin tipping system, when you like someone's post you can give him a small cryptocoin tip. That might also work as an additional moderating system. Non-moderators could mod-up comments (Insightful, Funny, etc) by eg. 0.5 points by spending some money.
** What about not-posting in the thread where you moderated? Good or bad rule? Maybe if you really must post, allow cryptocoin paying for post? (eg. "Warning: you have moderated in this thread, if you really want to post you need to spend cryptocoin on that" (??))

* Moderation strategy
** Chops instead of Karma
** Chops are derived from:
*** Articles accepted for submission
**** But NOT articles self-authored on a channel you're an editor of
*** Comments that are replied to by others without a troll modifier
*** Positive moderation (as judged by the mod action with respect to their own point value weights... so if they think funny is bad, it counts against you)
*** Positive metamoderation outcome (see below)
** Registered users that have used the site > [threshold] days, posted > [threshold] times, and have positive chops get moderation duty
*** The more chops, the more mod points per day, with a total cap for unused
** Meta-moderation is available to users that have used the site > [big threshold] days and have > [threshold] chops
*** Metamoderation is not "special", a meta-mod capable user can see a random selection of recent mods at any time and metamod.
*** Metamod takes 2 mod points <==Explain??
**** Metamod actions are like moderation actions, you spend modpoints on them. But they are twice as expensive as direct moderation. The theory is that users with more chops (and thus more modpoints to throw around) are more likely to spend some of them on metamoderation.
*** Metamod can spend a mod point to "re-roll" and see a new set of random moderations
*** A moderation is undone when it's "score" goes negative. It is "reapplied" when it goes positive. If the score dips to -3, the moderation is removed entirely.
*** A user is not rewarded or punished for the metamod specifically.
**** A running total of positive and negative meta-moderations against them is calculated
**** Certain threshold for positive and negative meta-mod counts result in fixed deltas in chops
***** Having >5 positive metamod could be +1 chop score. >10 +2, >20 +3; >3 negative is -1, > 5 is -2, > 10 is -3
** Your current chops as of more than 4 weeks ago is rolled into a fixed amount capped at 1.5 times the "Excellent" value and 1.5 times the most negative "Worst Poster" value.
*** On a weekly basis a task is run across all accounts that collects chop point actions since the last summarization date forward a week (actions that happened about 3 weeks ago), applies these to the last +4 weeks ago score, truncates it to the ranges above, and stores it in the database with the new summarization date for that user's account.
*** This prevents a user from "banking" actions that give them more chops to only later be a jerk.
*** However it lets you be a bit grumpy in the short term since the value can go above the thresholds when calculating the current display/privs value (query all the outstanding chop actions for this user, add the point values to the historic value, store it for easy reference later, cached for an hour)

Historic:FeatureList

2014-02-07T23:34:23Z

Pr0ntab:

Historic talk:FeatureList

2014-02-07T23:30:28Z

Pr0ntab:

Historic:FeatureList

2014-02-07T22:47:59Z

Pr0ntab: /* Requirements */

== Overview ==

I'd appreciate if everyone would just start adding or removing things they think need to be in the to-be variant of this site

Rather than isolate the things that slashdot already had (we should be familiar with it), let's just explicitly state what we want to see, with the idea that most of it is a copy or inspired by the original. But we can possibly explain, refine, or restrict our focus to the bits that matter.

== Requirements ==

* UTF-8 clean for anything that doesn't end up in a URL (i.e. tags, titles, channel names, user names)
** Of course, some combining marks would have to be filtered, and the resulting text round-tripped through NFD->NFC to prevent certain types of attacks against users or making text difficult to index.
* [http://blog.stackoverflow.com/2011/04/stack-exchange-partners-with-mathjax/ MathJax] support both in comments and in submissions. Mathjax is the math rendering engine used on [http://stackexchange.com/ stackexchange]. This will allow scientific discussion between us, people who can read math.
* Channels (like yro, politics, apple) as first class objects
** "Primary" channels that have DNS shorthand (http://apple.altslash.org/ being equiv to http://altslash.org/ch/apple/)
** "Secondary" channels that users could create and play editor that use the more verbose syntax (http://altslash.org/ch/baseball/) that is reminiscent of subreddits
** User channels (i.e. journals) as we've always had
* display user IDs.

* Submission queues for all channels with membership at the discretion of the channel owner; being able to submit also implies up/downvoting submissions and tagging
** Editors/channel owners only
** List of users who can submit
** All of my friends (for user journals)
** All users with mod status
** All registered users
** Everyone

* Articles are also first class objects
** Perma-link independant of channel
** Articles can be cross-posted to other channels by a channel owner (built into the UI if the editor manages more than one channel)
* Comment key features
** Comments are first class objects, just as before, just like articles
** Comments can be edited for a short period of time by owner
*** HOWEVER: Edited comments get a new ID and it links to older versions in the new one. This detail is made prominent to viewer if a comment reply happened before an edit.
** Allow alternate markup options (bbcode, markdown, wiki markup)
*** Provide a mapping to actual div and styles that will be applied, or HTML equivalent codes

* Allow moderation in same article that you've posted in; only disallow moderation '''to your own reply chain'''.
** You're obviously not allowed to moderate in your own accepted or posted article (treating all comments as replies)
** Does "reply chain" include parent? If not, how do we deal with threadjacking:
**# AC posts first comment on a new article (let's presume it's an upmod-worthy comment, not fristpsot)
**# I post my unrelated comment as a reply to AC's FP, in order to achieve greater visibility
**# I downmod the AC to -1
**# Now AC is invisible to anyone with threshold != -1 (including many with mod points and threshold=0, who would have modded AC up on his own merits)
**# Unless/until users with threshold=-1 and mod points happen by to rectify things, my comment is now the first thing most users see.
**# ??? ''(sorry, can't resist...)''
**# Profit!
***Actually, not just the immediate parent like I said, but 'all' ancestor comments. Otherwise as step 1.5 I just reply with an AC troll (which someone else will rightfully downmod), then in step 2 I reply to ''that''; now that the original AC first post is my comment's gp, so I can still downmod it.
** ''' Good point ''' you should be prevented from moderating any children ''''and''' ancestors of your posts (but sibling chains are still fair game)

* Moderation Engine
** Moderation tags only (default scores)
*** Overrated -1
*** Underrated +1
*** Offtopic -1
*** Interesting +1
*** Troll -1
*** Insightful +1
*** Flamebait -0.5
*** Funny +0.5
** Users assign own weights to tags in the range -2.0 -> 2.0 with 0.5 increments
** System rounds x.5 towards 0 in comment spill / threshold logic, display capped at -1 and 5.
** A score for the default weights is saved for the comment for use by article spill (for googlebot or "load all comments" from anonmyous user)
** An optional cryptocoin tipping system, when you like someone's post you can give him a small cryptocoin tip. That might also work as an additional moderating system. Non-moderators could mod-up comments (Insightful, Funny, etc) by eg. 0.5 points by spending some money.
** What about not-posting in the thread where you moderated? Good or bad rule? Maybe if you really must post, allow cryptocoin paying for post? (eg. "Warning: you have moderated in this thread, if you really want to post you need to spend cryptocoin on that" (??))

* Moderation strategy
** Chops instead of Karma
** Chops are derived from:
*** Articles accepted for submission
**** But NOT articles self-authored on a channel you're an editor of
*** Comments that are replied to by others without a troll modifier
*** Positive moderation (as judged by the mod action with respect to their own point value weights... so if they think funny is bad, it counts against you)
*** Positive metamoderation outcome (see below)
** Registered users that have used the site > [threshold] days, posted > [threshold] times, and have positive chops get moderation duty
*** The more chops, the more mod points per day, with a total cap for unused
** Meta-moderation is available to users that have used the site > [big threshold] days and have > [threshold] chops
*** Metamoderation is not "special", a meta-mod capable user can see a random selection of recent mods at any time and metamod.
*** Metamod takes 2 mod points <==Explain??
**** Metamod actions are like moderation actions, you spend modpoints on them. But they are twice as expensive as direct moderation. The theory is that users with more chops (and thus more modpoints to throw around) are more likely to spend some of them on metamoderation.
*** Metamod can spend a mod point to "re-roll" and see a new set of random moderations
*** A moderation is undone when it's "score" goes negative. It is "reapplied" when it goes positive. If the score dips to -3, the moderation is removed entirely.
*** A user is not rewarded or punished for the metamod specifically.
**** A running total of positive and negative meta-moderations against them is calculated
**** Certain threshold for positive and negative meta-mod counts result in fixed deltas in chops
***** Having >5 positive metamod could be +1 chop score. >10 +2, >20 +3; >3 negative is -1, > 5 is -2, > 10 is -3

Historic:FeatureList

2014-02-07T22:45:48Z

Pr0ntab:

== Overview ==

I'd appreciate if everyone would just start adding or removing things they think need to be in the to-be variant of this site

Rather than isolate the things that slashdot already had (we should be familiar with it), let's just explicitly state what we want to see, with the idea that most of it is a copy or inspired by the original. But we can possibly explain, refine, or restrict our focus to the bits that matter.

== Requirements ==

* UTF-8 clean for anything that doesn't end up in a URL (i.e. tags, titles, channel names, user names)
** Of course, some combining marks would have to be filtered, and the resulting text round-tripped through NFD->NFC to prevent certain types of attacks against users or making text difficult to index.
* [http://blog.stackoverflow.com/2011/04/stack-exchange-partners-with-mathjax/ MathJax] support both in comments and in submissions. Mathjax is the math rendering engine used on [http://stackexchange.com/ stackexchange]. This will allow scientific discussion between us, people who can read math.
* Channels (like yro, politics, apple) as first class objects
** "Primary" channels that have DNS shorthand (http://apple.altslash.org/ being equiv to http://altslash.org/ch/apple/)
** "Secondary" channels that users could create and play editor that use the more verbose syntax (http://altslash.org/ch/baseball/) that is reminiscent of subreddits
** User channels (i.e. journals) as we've always had
* display user IDs.

* Submission queues for all channels with membership at the discretion of the channel owner; being able to submit also implies up/downvoting submissions and tagging
** Editors/channel owners only
** List of users who can submit
** All of my friends (for user journals)
** All users with mod status
** All registered users
** Everyone

* Articles are also first class objects
** Perma-link independant of channel
** Articles can be cross-posted to other channels by a channel owner (built into the UI if the editor manages more than one channel)
* Comment key features
** Comments are first class objects, just as before, just like articles
** Comments can be edited for a short period of time by owner
*** HOWEVER: Edited comments get a new ID and it links to older versions in the new one. This detail is made prominent to viewer if a comment reply happened before an edit.
** Allow alternate markup options (bbcode, markdown, wiki markup)
*** Provide a mapping to actual div and styles that will be applied, or HTML equivalent codes

* Allow moderation in same article that you've posted in; only disallow moderation '''to your own reply chain'''.
** You're obviously not allowed to moderate in your own accepted or posted article (treating all comments as replies)
** Does "reply chain" include parent? If not, how do we deal with threadjacking:
**# AC posts first comment on a new article (let's presume it's an upmod-worthy comment, not fristpsot)
**# I post my unrelated comment as a reply to AC's FP, in order to achieve greater visibility
**# I downmod the AC to -1
**# Now AC is invisible to anyone with threshold != -1 (including many with mod points and threshold=0, who would have modded AC up on his own merits)
**# Unless/until users with threshold=-1 and mod points happen by to rectify things, my comment is now the first thing most users see.
**# ??? ''(sorry, can't resist...)''
**# Profit!
***Actually, not just the immediate parent like I said, but 'all' ancestor comments. Otherwise as step 1.5 I just reply with an AC troll (which someone else will rightfully downmod), then in step 2 I reply to ''that''; now that the original AC first post is my comment's gp, so I can still downmod it.
** ''' Good point ''' you should be prevented from moderating any children ''''and''' ancestors of your posts (but sibling chains are still fair game)

* Moderation Engine
** Moderation tags only (default scores)
*** Overrated -1
*** Underrated +1
*** Offtopic -1
*** Interesting +1
*** Troll -1
*** Insightful +1
*** Flamebait -0.5
*** Funny +0.5
** Users assign own weights to tags in the range -2.0 -> 2.0 with 0.5 increments
** System rounds x.5 towards 0 in comment spill / threshold logic, display capped at -1 and 5.
** A score for the default weights is saved for the comment for use by article spill (for googlebot or "load all comments" from anonmyous user)
** An optional cryptocoin tipping system, when you like someone's post you can give him a small cryptocoin tip. That might also work as an additional moderating system. Non-moderators could mod-up comments (Insightful, Funny, etc) by eg. 0.5 points by spending some money.
** What about not-posting in the thread where you moderated? Good or bad rule? Maybe if you really must post, allow cryptocoin paying for post? (eg. "Warning: you have moderated in this thread, if you really want to post you need to spend cryptocoin on that" (??))

* Moderation strategy
** Chops instead of Karma
** Chops are derived from:
*** Articles accepted for submission
**** But NOT articles self-authored on a channel you're an editor of
*** Comments that are replied to by others without a troll modifier
*** Positive moderation (as judged by the mod action with respect to their own point value weights... so if they think funny is bad, it counts against you)
*** Positive metamoderation outcome (see below)
** Registered users that have used the site > [threshold] days, posted > [threshold] times, and have positive chops get moderation duty
*** The more chops, the more mod points per day, with a total cap for unused
** Meta-moderation is available to users that have used the site > [big threshold] days and have > [threshold] chops
*** Metamoderation is not "special", a meta-mod capable user can see a random selection of recent mods at any time and metamod.
*** Metamod takes 2 mod points <==Explain??
*** Metamod can spend a mod point to "re-roll" and see a new set of random moderations
*** A moderation is undone when it's "score" goes negative. It is "reapplied" when it goes positive. If the score dips to -3, the moderation is removed entirely.
*** A user is not rewarded or punished for the metamod specifically.
**** A running total of positive and negative meta-moderations against them is calculated
**** Certain threshold for positive and negative meta-mod counts result in fixed deltas in chops
***** Having >5 positive metamod could be +1 chop score. >10 +2, >20 +3; >3 negative is -1, > 5 is -2, > 10 is -3