What is the point of limiting new users to three replies per topic?

(Ben T) #2

You should edit your post in that thread; as it will show as updated in the latest list. This is a similar discussion to (although this is about the 3 posts per thread):

(Jeff Atwood) #3

You bring up a good point – for topics you yourself have created, we should probably relax this requirement a bit or even remove it.

What do you think @eviltrout?

(Sam Saffron) #4

On this topic I find it mega confusing that we have 2 types of restrictions.

  1. Restrictions for users who’s accounts are 24 hours old or shorter
  2. Restrictions for “new users” as defined by trust levels.

I would strongly urge to fold in 1) into 2) … explaining this is hell.

(Jeff Atwood) #5

It is a problem if you put your evil hat on, and know how we calculate new users. Safety issue, becomes trivial to fill the forum with spam with one account, in about 16 minutes. :smile:

Have you met our friend tupac? New Question / Answer Rate Limits - Stack Overflow Blog

(Sam Saffron) #6

Our friend tupac is already covered by our standard rate limits.

This protection was introduced to stop brand new users from “dominating” topics due to patterns you observed at boing boing.

Anyway we can add “account must be 24 hours or older” to the new user priv, and communicate it to users somehow. I want users to learn what they need to do to become “regular” users.

At the absolute bare minimum 2 things should happen:

  1. Don’t let people type in 1000 words just to discover we are going to tell them they can not post, that is very poor form.
  2. Fix the error message: “You can no longer post in this topic cause your account is less than 24 hours old”

(Jeff Atwood) #7

I don’t feel any of this conversation is on topic here – the issue was on a topic the user created he wanted to reply more than 3 times. That is easily addressable without a bunch of scope creep. If it is your topic, I think you have a reasonable Manifest Destiny claim that you should be able to dominate your own topic with a zillion replies.

We also absolutely do not want to make people wait a whole day to get out of the new user sandbox.

Also have you even tried it? You get a small post it note notification above the typing area when you start typing that we won’t be accepting the post after you type a few characters. I suggest trying it yourself on try.discourse.org to see how it works, #1 is not even true.

(Sam Saffron) #8

Point #1 still stands ALSO, it is a lie this is not a “new user” restriction, its a restriction on accounts that are less than 24 hours old:

Point #2 still stands:

Both of these are bugs in my mind if we are keeping this “secret santa” behavior for accounts that are less than 24 hours

(Jeff Atwood) #9

If you don’t read the yellow box – which shows up even before you begin typing in the screenshot shown above – then we don’t want you as a user. What do you want the software to do, drive to the person’s house and have a face to face intervention with them?

The “sorry you can’t reply any more times” I think is a shared post rejection message – it applies to a number of rate limits on posting in the topic. @eviltrout would have to clarify.

And all this discussion is still totally off-topic. If you own (created) the topic, I don’t think there’s any reason to limit your replies, even as a new user.

(Sam Saffron) #10

Simple, disable the textarea, problem solved.

(Jeff Atwood) #11

That is fine, but won’t they then just create this new topic to junk up the forum?


(naturally in the wrong category)

It is really hard to cure the “user who cannot read” disease.

(Robin Ward) #12

I encountered this on my blog when I created my discourse install, because even as an admin I couldn’t post more than 3 times in 24 hours! I am going to fix both right now.

(Robin Ward) #13

Okay I’ve pushed a fix for admins / topic creators:

(Kane York) #14

Wrong link, this is the correct commit:


(Anthony) #15

Users don’t read any more than they need too. After posting a few times, you assume post it text = instructions you already know. I am blind to those instructions the same as with ADs.

(Dave McClure) #16

This still seems a sensible thing to do as well… no?

(Jeff Atwood) #17

As already replied earlier, no.

(Larry Salibra) #18

This limit is really confusing. There’s an interesting discussion going on in Using OneName/Namecoin blockchain as global nickname registry

@Jeremy and I asked @ryanshea some additional questions but he ran into this 3 post per thread limit after he had written up a long reply. He emailed reply to me, so now i have the answers, but no one else does.

I guess this is ultimately my fault because I forgot (until I started this post) that Discourse has an invite system that avoids this and instead just sent him a link to the topic. But it’s still annoying.

(Jeff Atwood) #19

He could also read topics here to earn trust level 1 on his own. But if you see him as a one shot who will only ever post in that one topic, yeah, that is what the invite button is for.

(Jeff Atwood) #20

I came to agree with you on this @larry. See our change here:

(Jeff Atwood) #21

Also @sam that error message was finally improved per your suggestion. Note what happened in the background of this image: