Added many, various rules with TODO placeholders for others #6

CAPNAMENOWUPVOTE · 2018-03-22T16:50:29Z

Here's my take at it. Far from complete. I have /r/linuxrules to test out the changes though. - /user/CAP_NAME_NOW_UPVOTE/

isugimpy · 2018-03-25T18:14:20Z

rules.txt

+## Spam-blog rules
+## Keep in mind there's various other sections about project-specific whitelisting
+##----------------------------
+    domain: ["phoronix.com", "omgubuntu.co.uk"]


Could we please not mark Phoronix as spam? Some of what they do is just quick links to other blogs, but there's a lot of really good value in their benchmarking.

OMG Ubuntu isn't blogspam. This seems to be motivated by that hurt individual user/magikarpkult that claims he was banned on OMG Ubuntu and now goes around all over reddit trying to ban the site everywhere. He was in contact with r/Linux about it as well and succeeded with his trolling, or at least that's what he says.

Blogspam would be characterized by a site that just aggregate other sites. OMG Ubuntu isn't in that category, the site has much original content that isn't found elsewhere. The owner is trying to stay ahead of other sites and refuses to cover stories that are already covered everywhere else.

The reason the owner gave for not writing much about KDE yet:

I can't cover everything I want to sadly! It's usually the case that by the time I hear about a KDE release or change it was 5 days ago and every other blog has written all there is to write about it.
KDE developers don't tell us about new releases or keep us in the loop in the way that developers of other desktops top. The easier that devs make it to write about their project, the more likely it is to get coverage.
(Source)

The reason he gave for not writing about the Krita 4.0 release:

Krita's PR team didn't ping us about the release, so by the time I knew it was out I was too late; every other site that covers Linux had already posted about it. Not much point in repeating what most people already know about.
(Source)

There's no reason to ban OMG Ubuntu altogether. This can be handled on a case by case if any unoriginal posts shows up.

The reason OMGUbuntu was marked as blogspam is because we'd rather have the official release (for instance, from KDE's blog or Ubuntu's official blog) than an article written by a 3rd party.

But, we can leave that to a vote.

Agree with your reasoning, but content originating from a official blog isn't always telling everything there is. Often details will be spread over several posts or other mediums making it hard for people who are not already closely following the projects to get a understanding of what's going on. Some projects don't even have a medium that they actively use, this is specially true for the smaller projects.

Voting would be appreciated. I think a voting on r/Linux would be the right thing to do for any site that are not obviously spam, as there are probably details here that should be discussed before banning.

Would it be more prudent to have the OP be the original source, with allowing Phoronix and such in the comments? That way, you get the official announcement, and gives a reason to visit the comment section and participate?

@LE3M - /u/magikarpkult comments did not go into my decision to include it here, really I ignored that users comments. The fact that it is blogspam is why it was included here (and I understand it, OMGUbuntu was banned already as well). r/linux is not r/Ubuntu; if we were talking about r/Ubuntu rules then maybe we'd have more of a discussion right now for allowing it. And yes I know they do more than just Ubuntu, but its still Ubuntu focused.

We should go the route of the main link being the original submission on /r/linux. These rules don't prevent the comments from posting links to OMGUbuntu etc sometimes they can add more context for a discussion. That's what the comments are for, and if the different discussions are in the comments of the official source then we avoid the issue of multiple posts containing the discussions.

Re: Voting on rules - I moderate other subreddits and voting on rules never works out. The most vocal users are not always right. For me, being able to submit the rules on GitHub is how I'm helping shape /r/Linux.

As pointed out through other discussions, when Phoronix was unbanned for posts, /r/Linux basically became /r/Phoronix. Same happened with OMGUbuntu.

Voting on rules won't be a "Hey, they voted this way so it's final." It's more of getting a pulse on the community. The rules may be influenced by the results, but it won't be fully democratic.

As nice as it sounds to take the vote, users will ask "the votes said ___, why is it ___." Not to let it stop you from doing said vote, and you probably already are aware that users will say that.

kruug · 2018-03-25T19:39:37Z

Previously, only Phoronix news articles were marked as spam. The benchmarks were still allowed.

CAPNAMENOWUPVOTE · 2018-03-25T22:11:02Z

I'd rather keep Phoronix banned as it's low quality content. There's more work I wanted to do including the re-implementing of allowing the benchmarks as a compromise to the Phoronix fans, but also wanted to look into some of the other poor blogspam sources or "news." ZDNet comes to mind as late news reporter, usually coming days after the events.

e-dt · 2018-03-27T10:05:51Z

rules.txt

+##----------------------------
+## Language/Profanity - (mostly from automoderator example)
+##----------------------------
+    title+body (regex): ["a(ss|rse|es)([ -]?holes?)?","b(i|\\*)o?(tch|\\*{3})(y|es)?","cocks?([ -]?suck(ers?|ing)?)?","cum(ming|[ -]shots?)?","cunts?","((mother|motha|mutha)[ -]?)?f(u?c?k?k|\\*ck|\\*{0,2}k|\\*{3})(er|ed|ing|s)?", "s(h(i|ar?|\\*)t|\\*{3}|h\\*{2})(s|ter|e|ting)?", "n[ioe0@][g]{1,}[aioe0@]{1,}r", "f[aioe0@]{1,}[g]{1,}[aioe03@]{1,}t"]


Profanity shouldn't be an instant remove, or a remove at all in my opinion

I agree that not all profanity should be instant removed and would like to move some of them to a report-only section. Some of the others should remain as instant removal, like the N word, though.

Edit: Also as noted, this particular section is from the automoderator example with some small changes.

…ffort posts rules, disguised links rules, amazon affiliate link rules, separated profanity into auto remove and just report

CAPNAMENOWUPVOTE · 2018-03-29T18:19:03Z

Made some changes. I couldn't separate out benchmarking properly for Phoronix, so left it banned as is. Can we get the old rule posted?

kruug · 2018-03-29T18:26:14Z

# phoronix
#domain: [phoronix.com]
url (includes): "phoronix.com/scan.php?page=news_item"
action: spam
#comment: This post has been removed since it is from Phoronix which is typically blog spam.  If your post is not blog spam please message the mods to have it approved.
comment: This post has been removed.  Phoronix News is considered blog spam.  If you feel this action has been made in error, please message the mods to review it.

CAPNAMENOWUPVOTE · 2018-03-29T18:31:12Z

Ah I see what you did there, removing only the news items ones. Benchmarks are tagged as articles but so are some of their non-benchmarks. I guess that could be a good middle ground for the Phoronix fans: Allow the articles including benchmarks, remove the news items. Thanks!

kruug · 2018-03-29T18:36:34Z

The non-benchmarks that are tagged as articles are typically articles that they are still the primary source on. Where people need to announce something for a smaller project where they don't have an official blog, or it's a smaller release that it's not blog worthy on their own, but Phoronix takes on the article.

…ile OS, various report reasons.

…d some filtering around, modmail on user reports

CAPNAMENOWUPVOTE · 2018-04-03T03:43:52Z

I'm out this week on vacation, so we can call my contributions done. Not sure on the long term plans for the pull request, I'll probably always have new things to add. Thoughts?

e-dt

General review -- looks good currently just a few nitpicks

e-dt · 2018-04-08T02:26:15Z

rules.txt

+#    Compliant with the site-wide reddit rules.
+#Comment Rules:
+#  All comments MUST be:
+#    Compliant with the site-wide reddit rules.


Are these still needed in rules.txt? Can we remove and leave README.md as the single definitive place for user-readable rules?

e-dt · 2018-04-08T02:28:17Z

rules.txt

+        Your [{{kind}}]({{permalink}}) in /r/{{subreddit}} was automatically removed for use of extreme profanity.
+
+        /r/{{subreddit}} is for productive discussion, so please watch your language.
+    modmail: The above post by /u/{{author}}, contained profanity not becoming of the /r/Linux community. The comment was removed. Please review users account for further action.


Should posts about TempleOS be excluded, because these words are often needed to describe the actions of Terry Davis?

Of course, could just leave it manually done

I was writing rules about tagging alternate OS's and thought it'd be good to put a reminder about TempleOS since that comes around here and there. If I could exempt the comment section for the few TempleOS posts I would but I don't believe that's possible. The rules and reminder exist to note that just because Terry says it doesn't mean a comment about it will be allowed. The posts are rare enough that manual approval can be done if mods want to.

e-dt · 2018-04-08T02:29:02Z

rules.txt

+        Your [{{kind}}]({{permalink}}) in /r/{{subreddit}} was automatically reported for review for use of profanity.
+
+        /r/{{subreddit}} is for productive discussion, so please watch your language.
+    modmail: The above post by /u/{{author}}, contained profanity not becoming of the /r/Linux community. The comment was removed. Please review users account for further action.


Remove "The comment was removed"

I tested these on my other subreddits and I've now removed the modmail on moderate profanity. Reporting is enough.

jbicha · 2018-05-12T00:17:10Z

rules.txt

+        Your submission contains rehosted content, usually paird with privacy-invading ads.
+
+        Please re-post your {{kind}} using the original source with the original title.
+---


Please consider adding Softpedia to the blocked by default list.

…ore.

…nd added softpedia to be removed

Added many, various rules with TODO placeholders for others

59a720c

isugimpy reviewed Mar 25, 2018

View reviewed changes

e-dt reviewed Mar 27, 2018

View reviewed changes

Remove moderator exempt for most items, various domain tagging, low e…

924b4b7

…ffort posts rules, disguised links rules, amazon affiliate link rules, separated profanity into auto remove and just report

CAPNAMENOWUPVOTE added 2 commits March 29, 2018 17:50

Added some more profanity, special domain rules like templeOS and mob…

d02c565

…ile OS, various report reasons.

Modified report reasons for better use, added CC DOX protection, move…

a8b52e9

…d some filtering around, modmail on user reports

e-dt reviewed Apr 8, 2018

View reviewed changes

jbicha reviewed May 12, 2018

View reviewed changes

CAPNAMENOWUPVOTE added 2 commits May 15, 2018 09:58

Updated all sorts of rules, aligned with rules, added spamblogs and m…

1f9135c

…ore.

fixed some text around modmail since a lot of that has been removed a…

f6c7128

…nd added softpedia to be removed

kruug approved these changes May 15, 2018

View reviewed changes

kruug merged commit 0f660cd into LinuxSubreddit:master May 15, 2018

LinuxSubreddit deleted a comment from daftande May 27, 2018

LinuxSubreddit locked and limited conversation to collaborators May 27, 2018

Added many, various rules with TODO placeholders for others #6

Added many, various rules with TODO placeholders for others #6

Uh oh!

Conversation

CAPNAMENOWUPVOTE commented Mar 22, 2018

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LE3M Mar 26, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LE3M Mar 26, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kruug commented Mar 25, 2018 via email • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

CAPNAMENOWUPVOTE commented Mar 25, 2018

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CAPNAMENOWUPVOTE Mar 28, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CAPNAMENOWUPVOTE commented Mar 29, 2018

Uh oh!

kruug commented Mar 29, 2018

Uh oh!

CAPNAMENOWUPVOTE commented Mar 29, 2018

Uh oh!

kruug commented Mar 29, 2018

Uh oh!

CAPNAMENOWUPVOTE commented Apr 3, 2018

Uh oh!

e-dt left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

LE3M Mar 26, 2018 •

edited

Loading

LE3M Mar 26, 2018 •

edited

Loading

kruug commented Mar 25, 2018 via email •

edited

Loading

CAPNAMENOWUPVOTE Mar 28, 2018 •

edited

Loading

e-dt left a comment •

edited

Loading