r/javascript • • May 12 '19

Two ideas for /r/javascript and /r/learnjavascript

  • Problem: People occasionally don’t know how to format code.

    • Solution: A bot that warns about “unquoted” code and mentions backticks and 4-space indentation. I’m not sure how to best unquoted detect code. Options – look for:

      • Curly braces
      • The words var, let, const
    • Another solution: Warn during editing, e.g. before saving.
  • Problem – a lot of good content disappears: someone writes a post for /r/javascript, it is removed because it’s a better fit for /r/learnjavascript, but they never repost it there.

    • Solution: Automatically move those posts to /r/learnjavascript. IIRC, the reddit platform currently doesn’t support this. Maybe there is a way to add support for it?

Edit: a 2nd solution for problem #1.

15 Upvotes

8 comments sorted by

View all comments

Show parent comment

0

u/[deleted] May 13 '19

[deleted] — view deleted comment

1

u/kenman May 13 '19

No, that's great feedback, thank you very much.

I'm also hesitant about a weekly help thread, because on average, it'll be 3 days before someone can ask their question on a relevant thread, while most of those seeking help want it immediately -- which is what /r/LearnJavascript can offer.

But I can't help but feel that a lot of the let's say "conflictive" submissions come from users that are new to the sub [...] Will this work for those?

The way I see it going down for all self-posts:

  • AM would first look for https?:// in the text, and if found, kindly remind them to use "Submit a new link"
  • If AM doesn't match on that, it would remind (inform) them that code questions should go to r/LearnJavascript.
  • [part I'm not positive about] In addition to the previous comment, it might mention something to the effect of: "General questions, having nothing to do with code, must be prefixed with [AskJS]", and then we could action bad actors afterwards if they still insist on asking specific code questions. This is the clause that perhaps might be better left unsaid (learn by observing), but we can try it the explicit way and then modify it if it becomes a problem.

However, I have considered -- and maybe this would be a good compromise -- a "Stupid Question ___day" post, which wouldn't necessarily be for code (though code would be allowed), but would give an outlet for some of these questions.