# Suggestion of Junior Moderating vs Request to Members

**URL:** <https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672>\
**Category:** About This Message Board\
**Created:** [May 8, 2021, 5:25pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672 "2021-05-08T17:25:24Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [May 10, 2021, 6:06pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/21 "2021-05-10T18:06:27Z")

</div>

Change 1 character. Problem solved.

This is a minor issue with the software design and not an option. But change 1 character.

---

<div class="post-metadata">

**Author:** ![naita](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/naita/32/5862_2.png) [@naita](https://boards.straightdope.com/u/naita)\
**Post date:** [May 10, 2021, 6:11pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/22 "2021-05-10T18:11:37Z")

</div>

Suggesti0n of Junior Moderating vs Request to Members

---

<div class="post-metadata">

**Author:** ![Darren\_Garrison](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/darren_garrison/32/92_2.png) [@Darren\_Garrison](https://boards.straightdope.com/u/Darren_Garrison)\
**Post date:** [May 10, 2021, 6:13pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/23 "2021-05-10T18:13:57Z")

</div>

Okay, there does seem to be some time limit. To find an old thread I picked a random word likely to be used in a discussion and searched for threads before a specific date (just plugged in this date in 2005). I picked “Morons who won’t see good films” (a 2005 pit thread) and was able to reuse that title. Does anybody know the time limit? Finding it by trial and error would be tedious and annoying for everyone.

---

<div class="post-metadata">

**Author:** ![Darren\_Garrison](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/darren_garrison/32/92_2.png) [@Darren\_Garrison](https://boards.straightdope.com/u/Darren_Garrison)\
**Post date:** [May 10, 2021, 6:16pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/24 "2021-05-10T18:16:31Z")

</div>

(FWIW I was looking for threads that mentioned movies, not morons…)

---

<div class="post-metadata">

**Author:** ![TriPolar](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tripolar/32/3008_2.png) [@TriPolar](https://boards.straightdope.com/u/TriPolar)\
**Post date:** [May 10, 2021, 6:40pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/25 "2021-05-10T18:40:03Z")

</div>

> [@Darren\_Garrison](#):
>
> Well, it is across all the site – I just tried to start another “Suggestion of Junior Moderating vs Request to Members” in MPSIMS and it wouldn’t let me.

I suggest from now on when this happens we add the word ‘corn’ to the title to disambiguate it.

---

<div class="post-metadata">

**Author:** ![gnoitall](https://avatars.discourse-cdn.com/v4/letter/g/bb73d2/32.png) [@gnoitall](https://boards.straightdope.com/u/gnoitall)\
**Post date:** [May 10, 2021, 7:12pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/26 "2021-05-10T19:12:19Z")

</div>

> [@TriPolar](#):
>
> …add the word ‘corn’ to the title to disambiguate it.

That’s just begging to have the thread cornfielded. 😬

---

<div class="post-metadata">

**Author:** ![CardboardBoxx](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cardboardboxx/32/7079_2.png) [@CardboardBoxx](https://boards.straightdope.com/u/CardboardBoxx)\
**Post date:** [May 10, 2021, 7:54pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/27 "2021-05-10T19:54:49Z")

</div>

I think it may be a difference between how discourse changes apostrophes from the changeover to how it changes apostrophes in new threads. In the old one it was omitted in the URL, in the new one it was replaced with a hyphen.

---

<div class="post-metadata">

**Author:** ![CardboardBoxx](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cardboardboxx/32/7079_2.png) [@CardboardBoxx](https://boards.straightdope.com/u/CardboardBoxx)\
**Post date:** [May 10, 2021, 8:00pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/28 "2021-05-10T20:00:08Z")

</div>

I tested a thread title “Faking to be handicapped and Disneyland”, which has no punctuation, from 15 years ago and it wouldn’t let me create it.

---

<div class="post-metadata">

**Author:** ![naita](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/naita/32/5862_2.png) [@naita](https://boards.straightdope.com/u/naita)\
**Post date:** [May 10, 2021, 8:34pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/29 "2021-05-10T20:34:32Z")

</div>

How does one fake being Disneyland?

---

<div class="post-metadata">

**Author:** ![Max\_S](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@Max\_S](https://boards.straightdope.com/u/Max_S)\
**Post date:** [May 10, 2021, 9:52pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/30 "2021-05-10T21:52:02Z")

</div>

Someone wanting to make another topic like that could use the title, “Disneyland and faking to be handicapped”

~Max

---

<div class="post-metadata">

**Author:** ![Do\_Not\_Taunt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/do_not_taunt/32/2968_2.png) [@Do\_Not\_Taunt](https://boards.straightdope.com/u/Do_Not_Taunt)\
**Post date:** [May 10, 2021, 9:55pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/31 "2021-05-10T21:55:14Z")

</div>

I just find it rather strange. Sure, it’s easy enough to work-around, but what’s the point of such a limitation?

Anyway, sorry for the hijack!

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [May 11, 2021, 2:19am UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/32 "2021-05-11T02:19:38Z")

</div>

> [@Do\_Not\_Taunt](#):
>
> I just find it rather strange. Sure, it’s easy enough to work-around, but what’s the point of such a limitation?

I presume that it is because the URLs are based on the titles, and you need to have a unique URL for each thread. They could have added an option to add a number at the end or something to disambiguate, but, knowing how “opinionated” Discourse is (@codinghorror’s word, not mine), I suspect there was then some argument about “encouraging people to write unambiguous titles” that was considered more important.

If I had developed it, I would have had Discourse warn the user that said title had already been used before, and to make sure their title was unambiguous. But, if they continued, it would still post, and the URL would add a number to disambiguate. Mods could, if they wanted, choose to get a notification about such, so they could then check and make sure the title is indeed not ambiguous.

Especially since Discourse also encourages closing zombie threads, it just makes sense that a newer thread may warrant the same title as an older one. Thus the resulting impression is that the user is having to workaround a limitation, which can make any software feel unfinished.

---

<div class="post-metadata">

**Author:** ![Do\_Not\_Taunt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/do_not_taunt/32/2968_2.png) [@Do\_Not\_Taunt](https://boards.straightdope.com/u/Do_Not_Taunt)\
**Post date:** [May 11, 2021, 5:36pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/33 "2021-05-11T17:36:10Z")

</div>

> [@BigT](#):
>
> I presume that it is because the URLs are based on the titles, and you need to have a unique URL for each thread. They could have added an option to add a number at the end or something to disambiguate, but, knowing how “opinionated” Discourse is (@codinghorror’s word, not mine), I suspect there was then some argument about “encouraging people to write unambiguous titles” that was considered more important.

Well, it was a rhetorical question, but I basically agree that it is probably a (questionable) design decision that Discourse made in order to facilitate having unique conversations or some such.

The URL pattern, FWIW, appears to be [https://boards.straightdope.com/t/{thread-name}/{thread-id}/{optionally-post-number}](https://boards.straightdope.com/t/%7Bthread-name%7D/%7Bthread-id%7D/%7Boptionally-post-number%7D). So even if the thread name were non-unique, the thread ID would be. Ergo, URL uniqueness doesn’t require unique thread names nor the workaround you propose.

---

<div class="post-metadata">

**Author:** ![GreenWyvern](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/greenwyvern/32/2834_2.png) [@GreenWyvern](https://boards.straightdope.com/u/GreenWyvern)\
**Post date:** [May 11, 2021, 6:07pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/34 "2021-05-11T18:07:38Z")

</div>

> [@Do\_Not\_Taunt](#):
>
> Sure, it’s easy enough to work-around, but what’s the point of such a limitation?

FWIW, I think that Discourse is right not to allow duplicate titles.

It can only lead to confusion, and to replies and links to the wrong topic – and there’s no advantage to allowing duplicate titles, as far as I can see.

If you really MUST start a new thread with a duplicate title, instead of bumping the existing thread on that subject, then add a suffix yourself, ‘Part 2’, or ‘2021’ or something.

---

<div class="post-metadata">

**Author:** ![GreenWyvern](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/greenwyvern/32/2834_2.png) [@GreenWyvern](https://boards.straightdope.com/u/GreenWyvern)\
**Post date:** [May 11, 2021, 6:32pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/35 "2021-05-11T18:32:36Z")

</div>

In fact, it looks like there’s a Discourse setting for duplicate titles, and you can currently have

- No duplicate titles
- Allow duplicate titles in different categories (probably what’s set here)
- Allow all duplicate titles  
&nbsp;

> **[Could we check the duplicated topic title for the each category only?](https://meta.discourse.org/t/could-we-check-the-duplicated-topic-title-for-the-each-category-only/98790)**
>
> First of all, I would like to say “thank you very much” to the Discourse team. You had a great, smart and interesting forum. We are using the Discourse as a platform for our website 😃 Then we have one case that needs your help. Currently, the...

---

<div class="post-metadata">

**Author:** ![Do\_Not\_Taunt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/do_not_taunt/32/2968_2.png) [@Do\_Not\_Taunt](https://boards.straightdope.com/u/Do_Not_Taunt)\
**Post date:** [May 12, 2021, 8:10pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/36 "2021-05-12T20:10:52Z")

</div>

> [@GreenWyvern](#):
>
> FWIW, I think that Discourse is right not to allow duplicate titles.
> 
> It can only lead to confusion, and to replies and links to the wrong topic – and there’s no advantage to allowing duplicate titles, as far as I can see.

Well, this is something like eleventy-billionth on the list of things I care about, but I disagree. I think your concern is probably best addressed with a time-limited (and possibly forum-limited) period of uniqueness, rather than an all-time, all-space limit.

> [@GreenWyvern](#):
>
> Allow duplicate titles in different categories (probably what’s set here)

Assuming ‘categories’ means ‘fora’ (I can never remember Discourse’s nomenclature for these things), I think we determined that’s not what’s set here. The block is across all fora. See post 19 by @Darren_Garrison.

---

<div class="post-metadata">

**Author:** ![Omar\_Little](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/omar_little/32/269_2.png) [@Omar\_Little](https://boards.straightdope.com/u/Omar_Little)\
**Post date:** [May 12, 2021, 11:06pm UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/37 "2021-05-12T23:06:23Z")

</div>

To get back on topic of Jr. modding vs. member suggestions:

I can see how minor suggestions to other members that may make them better members of the community may seem just that - minor. But that’s the perception of the person making the suggestion. You never know how that’s going to be received. You minor suggestion, may be their ultimate affront. It’s probably better to just flag the post for follow up by a mod, and let chaos reign until one of them looks at it.

---

<div class="post-metadata">

**Author:** ![jnglmassiv](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@jnglmassiv](https://boards.straightdope.com/u/jnglmassiv)\
**Post date:** [May 13, 2021, 2:34am UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/38 "2021-05-13T02:34:31Z")

</div>

> [@Omar\_Little](#):
>
> I can see how minor suggestions to other members that may make them better members of the community may seem just that - minor.

I’ve dropped my protest, mostly because I hadn’t realized that failing to use minimally descriptive thread titles actually **is** a rule violation and so it does appear a bit more like Junior Moderating than I’d first thought. And also, because the thread title remains unchanged after a lot of Moderator attention. I still think it’s wrong and dumb to allow dippy thread titles in GQ and CS (to a lesser extent) but I’ll grin and bear it.

More broadly though, members make requests to other members pretty frequently and they’re not always nice. ‘Try reading for comprehension’ is one you see a lot. “Point out where I said [this that or the other]” is another.

---

<div class="post-metadata">

**Author:** ![Do\_Not\_Taunt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/do_not_taunt/32/2968_2.png) [@Do\_Not\_Taunt](https://boards.straightdope.com/u/Do_Not_Taunt)\
**Post date:** [May 13, 2021, 2:51am UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/39 "2021-05-13T02:51:01Z")

</div>

> [@Omar\_Little](#):
>
> To get back on topic of Jr. modding vs. member suggestions:

Get your own thread! 🙂

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/codinghorror/32/4242_2.png) [@codinghorror](https://boards.straightdope.com/u/codinghorror)\
**Post date:** [May 14, 2021, 1:24am UTC](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672/40 "2021-05-14T01:24:59Z")

</div>

> [@GreenWyvern](#):
>
> It can only lead to confusion, and to replies and links to the wrong topic – and there’s no advantage to allowing duplicate titles, as far as I can see.

I think the only solution is for @GreenWyvern and I to get married.

Having a bunch of duplicate titles isn’t just bad for you, it’s bad for SEO, it’s bad for everyone else who wants to find, well… anything.

[Previous page](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672.md?page=1)

[Next page](https://boards.straightdope.com/t/suggestion-of-junior-moderating-vs-request-to-members/941672.md?page=3)
