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 "town hall" (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 Can't start comment thread on Codidact Power Users

Post

Can't start comment thread on Codidact Power Users

+2
−0

I can't start comment thread on Codidact Power Users (but can on the other sites):

Image_alt_text

No error message. I guess this is due to some mod revoking my "Participate Everywhere ability" 12 days ago but I can now do anything e.g. posting questions, except starting start comment thread so I though my "Participate Everywhere ability" had been restored by now, so I don't understand what's going on. Anyway at least this a feature request to add an error message.

Mod message revoking my "Participate Everywhere ability" Hello,

This message is from the Codidact community team.

You have posted a large number of questions that are cut-and-paste copies of questions from other sites such as Reddit and Stack Exchange. These questions do not link to the other posts, nor have you edited them to improve them based on what you have learned elsewhere. In some cases, you have cross-posted the same question to multiple sites at the same time. Moderators have asked you to change this behavior but you have not.

There are several issues here:

  • This kind of cross-posting wastes the time of people answering the question. They won't know that you already got an answer on Reddit or that discussion on SE led you to edit the question there. This is disrespectful of our community members' time and attention.

  • Excessive copy-pasting from elsewhere makes Codidact look like a scraper site. We're not.

  • The sheer volume of these crossposts takes attention away from other questions.

This must stop.

In addition, the quality of the questions is often low, with little explanation and screenshots in place of text. We'd like you to slow down and focus on quality.

This doesn't mean you can never ask a question you've asked elsewhere. But do it one site at a time, link to the prior versions, and thoughtfully incorporate what you learned when you write the new question here. Share what you've tried already, just like if you had consulted the documentation or used a published example, and incorporate it. When you post a question on Codidact that you have previously asked somewhere else, the version on Codidact should be the best version of the question, not a blind copy. Slow down and be mindful of the other members of the community.

We are revoking the Participate Everywhere ability on your account across the network. This imposes a rate limit on questions. When you have enough positive activity to demonstrate that you have improved, you will re-earn the ability.

We are also reviewing your activity and expect to delete many of these questions. This will be a human review, not a SQL query, so it will not be instantaneous.

We welcome your participation with original quality content and hope you will also try answering other people's questions. A community has its best shot at success when people work together toward a shared goal -- asking, answering, editing, and making Codidact the best place it can be.

If you have questions about this message, you can send email to [email protected].

This is a formal warning from the moderation team. In the event of continued violations of the site rules, your account may be suspended. If you have any questions regarding the site rules, you can ask them in the Meta category of this site or on meta.codidact.com. If you have any questions about this warning or would like to dispute it, contact us.

☐ I have read this warning and will follow the rules from now on.

History

3 comment threads

Does the title not show up when you hover over the button? (8 comments)
Checking which abilities you have on a given community (2 comments)
Commenting on all posts requires the "Participate Everywhere" ability (1 comment)
Does the title not show up when you hover over the button?
Oleg Valter‭ wrote 9 months ago · edited 9 months ago

The reason for why the button is disabled is supposed to show up on hover as it's set in the button's title (I know, not the best UX on touch devices, but we are working on it) - does it not show up for you?

Oleg Valter‭ my bad, you are right, I was moving the mouse too quickly. The reason for why the button is disabled is supposed does show up on hover after ~1 sec.

Oleg Valter‭ wrote 9 months ago

Thanks for confirming, Franck Dernoncourt‭! We should probably show the message inline if a user attempts to click on the button - seems like my decision (we used to show a big error message next to every such button which lead to a lot of clutter on pages) to move the reason into the title is confusing.

trichoplax‭ wrote 9 months ago

If relying on hover is confusing (even on desktop) and not having the button at all could also be confusing, would another option be to replace the button with a link to the Participate Everywhere ability tracking page, perhaps with the link text being something like "Gain the Participate Everywhere ability to comment on this post"?

Thanks all, just to add some context, my setup might be a bit particular since I use dwell clicking rather than a physical mouse click. With that, I tend to move the pointer away fairly quickly, which made the hover-based explanation easy to miss at first. So it may just be me. Might be worth waiting to see whether other users report the same confusion before changing anything.

trichoplax‭ wrote 9 months ago

Thanks for clarifying. Ideally I'd like to see an approach that works for as many people as possible, including touchscreens. I didn't know about dwell clicking until you mentioned it. I can see why that wouldn't make hovering practical.

For other readers who also weren't familiar, dwell clicking allows avoiding clicking manually, by automatically registering a click when the mouse is hovered over something clickable.

Oleg Valter‭ wrote 9 months ago · edited 6 months ago

Hmm, sounds like popping up an error message with a link to your abilities page might be a good idea then? It would also automatically solve the touchscreen issue - tapping on the button would pop up the message.

Oleg Valter‭ thanks, that would indeed. But rather low priority imho.