Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Get rid of minimum character requirements

Parent

Get rid of minimum character requirements

+3
−3

Various places in Codidact where a user enters text seem to have a minimum character requirement. If you enter fewer characters than that, the system keeps the "submit post" button greyed out, pops up a message that a minimum number of characters are needed, or the like.

Let's get rid of these limits. Some reasons are:

  1. It's just plain annoying. I've said all that needs to be said, and the system is forcing me to add more.
  2. It's nannyware treating people like children. This is not how to treat contributors.
  3. It's ineffective anyway. When I get a nanny-message, I'll develop an attitude of living up to the letter of the law, not the spirit. I'll pad the text with dashes, blanks, "blah, blah", or whatever. That actually makes the post worse as a result of the supposed minimum quality control.

    (I just found out that padding with "&nbsp;" works to fool the system to let you post a short flag reason, but then it shows "&nbsp;" literally instead of rendering it as a space. Again, that made the flag reason worse for the moderator to read, not better.)

  4. Length is not quality.

    If someone asks a clear yes/no question, then a simple "Yes" or "No" can be a legitimate response, especially in comments.

    I just tried to write "Opinion-based" as a flag reason for closing a question. That's all I felt needed to be said, as I believe this will be obvious to the mod that looks into the flag. Again, this is my call to make, and the mod's how to respond to it. I resent the system treating me like a child based on some arbitrary metric.

  5. There are already better quality controls. Real humans will eventually judge everything you write here, with the associated consequences. Let those mechanism do their job.

    A simple "Yes" could be correct and useful to the OP. More background might be better, but I wouldn't downvote "yes" when it's right and directly responds to the question as asked. I might possibly upvote for the unambiguous succinctness, depending on context.

    In other case, "Yes" could be a patronizing dismissal. There is no way the system can tell the difference. The voters can, so let them.

It strikes again

I just tried to raise a custom flag with the comment "Not an answer". I felt this would be quite clear when looking at the flagged answer. However, it wouldn't let me raise the flag. I had to waste time reading the popup, and then add two garbage characters. Now the comment is "Not an answer..". This is stupid.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+6
−0

Prevent zero only

  • I'm comfortable with preventing users from posting zero character comments and posts.
  • I agree there are times when insisting on 15 characters is unhelpful.
  • For comments, I see no reason to make the minimum higher than 1.
  • For posts, I'd expect them to be longer but 15 is arbitrary so why not have 1 and let users flag problematic posts?

There may be some other settings where 1 is not appropriate, but I can't think of a reason not to use 1 for comments and posts.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

I'd be happy with this (4 comments)
I'd be happy with this
Olin Lathrop‭ wrote over 1 year ago

That makes sense. There is no legitimate reason to post an empty message. That's probably an accident anyway, so good to trap. Otherwise, keep the system out of the way of author intent. +1

Michael‭ wrote 12 months ago · edited 12 months ago

>0 after trim(), maybe, to get rid of spacebar-only stuff?

There's also an argument to be made for >0 after stripping [^[:alnum:]] to prevent posts of ., but this might get weird if someone tries a real post of entirely symbols and punctuation that is too clever by half.

trichoplax‭ wrote 12 months ago

I can't imagine a punctuation only comment outside of code golf, but it does seem easier to avoid the special case by not preventing punctuation only comments anywhere.

trichoplax‭ wrote 12 months ago

Yes I like the idea of using trim before testing to avoid whitespace only comments.