I think it's because StackEdit was causing issues for a lot of people. For those people, problems ranged from StackEdit not loading and instead showing a white window to StackEdit not letting people encode their scripts using the Code icon.
Consider the scenario where a question receives only one answer. And it's wrong so its not accepted. Then the responder can accept their faulty answer after 48 hours. I would say then maybe we should have a reject button, but consider if it's already too hard to accept things then it will be doubly hard for users to reject things.
@sjr04Alt yeah, that's how people work, we can't really change that. changing the master requirement doesn't really help, because again, almost nobody will check their rank before checking the code, they'll likely check the code and not inspect the user's profile at all. /shrug
@kingdom5@DominusInfinitus When I said downvote I was talking about the claim to close the question. People will put out claims on questions that ask "what is the [insert positive adjective] way to do X?". Which falls under the category of primarily opinion based.
'These may be questions asking what is better, which method is recommended or "most efficient", when there are multiple reasonable answers. The answer to these questions is typically up to the preferences of the person answering the question.'
Notes are there to notify the user that they should update their question/answer (they show up in the users notifications). The goal is to allow the user to take the correct action to prevent rep loss. I often allow users time to fix or remove their content before taking action.
You have absolutely no reason for reposting your question. And for the code blocks, an edit will suffice.
My reasoning behind the endorsement of giving community moderators full claim weight was based on the consensus that anyone who is a community moderator is in that position because they use good judgment and help their fellow community members.
However, upon reading back on the other user replies again, I'm starting to see this from another point of view. I agreed with Zafirua in that this feature should be rarely used to begin with, and that putting trust into all of the community moderators individually to rarely use this feature may be a bad idea. We don't want people to treat pinning an answer as an "up vote," or "accepted answer" -- it should be much more valuable than that.
In fact, it should be similar to how locking a question should be used. Though, they will have still have very distinct purposes. Locking a question should only be done if a Q/A is very helpful to the community and thus shouldn't receive any more feedback. Pinning an answer, however, says the user went above and beyond expectations while answering the question yet still remained on topic and relevant to what the asker posted -- an overall great-quality answer.
Therefore, my conclusion is this: I don't think pinning an answer should be something that all community mods have to vote on -- that would just be kind of annoying to rally everyone together for pinning an answer (in my opinion, I'm open to what other people think). Instead, it should be something that is initiated by community mods, then voted on by the community (with some claim weight) and by other community mods (with more claim weight). I feel like this is a more balanced system, but again, please let me know what you think.
@sjr04Alt There are users with just the "moderator" rank, although I don't know if they actually have any different access/control over the SH site, or moderation abilities. That may just be Eryn, m39?
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Scripting Helpers was lost, please wait while we try to reconnect.