I am running a course on Discourse, and all of my students are suddenly complaining that there is a 'Reply Limit" imposed upon them. I have never had this before? I changed all of their statuses to ‘member’ thinking that was the issue, and then went to Settings/Postings/NewUserMaxRepliesPerTopic and changed it to 100 but they are still having problems.
Well, the definition of the word “consecutive” might help:
con·sec·u·tive – following continuously.
“five consecutive months of serious decline” “share prices fell for three consecutive days”
synonyms: successive, succeeding, following, in succession, running, in a row, one after the other, back-to-back, continuous, straight, uninterrupted
So if someone adds that many replies in a row to a topic (aka consecutively), they will be prevented from adding even more replies until someone else replies.
In other words, this is (generally) a bad pattern for discussions:
So the underlying platform for Discourse is made up of Linux running under Docker, Ruby on Rails, Redis, PostgreSQL, and a few other things that I can’t immediately think of. The word “row” is a term of art for SQL-esque databases, so, presumably, that’s a setting for configuring how many replies get stuffed into a single database row.
Actually, that might make it worse. Under the rule against surplusage, anyone reading that list is going to try to come up with a definition under which all of the given “synonyms” actually mean something different.
If you really want me to try to write a description, though…
Number of posts a user can make to the same topic, without giving anyone else a chance to reply, before being prevented from posting again.
I would remove ‘in a row’ and replace it with ‘consecutively’.
For clarification, in your replies, are you trying to make me feel more stupid than I already do? Are you trying to make a joke? Are you serious? I’m interested in understanding the context of your replies.
I can’t speak for Jeff, but I can say that reading this thread it doesn’t come across that he’s trying to mock or belittle.
As terms go, here in the UK ‘in a row’ is a much more commonly used term than consecutively. It’s used in all kinds of fields; we talk about seats in a row, days in a row, personally I would expect more people to know and use that term than to ever reach for consecutive. Both terms appear on the setting, so hopefully people will be able to grasp at least one of them - there aren’t many good alternatives, lest we be reduced to referring to successive or ensuing responses.
Either way, it appears as though you have your solution.
That’s fairly misleading, particularly when there’s no measure of time involved in that setting. Consecutive posts aren’t a rate limit - the setting exists to encourage people to think out their responses and minimise excessive thread bumps. As pointed out earlier the majority of communities don’t encourage such behavior, which is why the default is 3 but it can be overridden if needed.
“successive” I guess does not work cause brain reads “success” but “continuous” kind of works imo if we want to avoid consecutive, however it is somewhat open to interpretation.
I guess we can wait for now and see if others find the language confusing here as well. I am big on improving copy to make sure things are as understandable as possible by the widest possible audience.
Is the ‘max consecutive replies’ setting meant to apply to users own topics also? Doesn’t seem to be limiting consecutive replies in a users own topic for me.
How do flagged/hidden replie work into this situation?
If I user makes 3 consecutive replies, but before a new reply from anybody comes in, one of the 3 replies is flagged and hidden, can that user reply a 4th time?