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.

Comment extravaganza, or on the recent improvements to commenting experience on Codidact

+8
−0

This post focuses on the work we've done over the past couple of months to make commenting experience on the network better for everyone. I tried to outline as many changes as I could here, but do check up on the Recent feature changes post for 2025 for a comprehensive list (we've also made a lot of fixes and feature request changes that are not comments-related).

Improvements to comment rate limits

First of all, we are now much more upfront as to whether you can create comment threads or reply to existing ones — the buttons are always shown but disabled if you can't use them at this point for some reason (instead of letting you carefully craft your replies only to be slapped with an error message upon submission) with the exact reason shown on hover:

Screenshot of a comment thread with the reply button disabled due to it being archived

What's more, communities are now able to decide whether they want to allow new users (that is, those without the Participate Everywhere ability) to comment on posts of others (as opposed to only being able to comment on their own posts and answers to them).

Important note for site admins 2 new site settings are now available under the "Rate limits" section:
  • RL_NewUserCommentsOwnPosts for users without the Participate Everywhere ability when commenting on their own posts (or answers to them), set to 30 by default;

  • RL_CommentsOwnPosts for users with the Participate Everywhere ability when commenting on their own posts (or answers to them), set to 50 by default;

Improvements to inline thread views

Secondly, quite a few changes have been made to the inline thread views (when you expand a thread under a post's list of comment threads).

Large threads now take much less space and have a more consistent feel to them (it's still necessary to open the full view to show all comments on large threads, but we are already working on making it an inline action):

Screenshot of a part of an inline thread view with the "Skipping 2 deleted comments" and "Showing 5 of 24 comments" widgets outlined

Eagle-eyed readers might've noticed that there's now a "Reply to this thread" button at the bottom of the thread — yes, it's finally possible to reply to threads without having to open the full view:

Screenshot of the inline reply to thread widget

What one might've also noticed is that all actions on comments can now be taken inline too, including editing, deletion, undeletion, and flagging:

Screenshot of a comment being edited inline

Screenshot of a comment being flagged inline

Screenshot of a comment that's just been deleted inline

We haven't forgotten about curators and moderators either — if you have the necessary abilities and/or roles, all thread actions are now available to you from the inline view too:

Screenshot of the tools modal opened on the inline thread view

Improvements to thread titles

Lastly, we made a couple of upgrades for thread titles.

It used to be that if you referred to someone via an @-mention in a thread title, we would show the mention as is (with bare user id) — this is no longer the case. Provided the mentioned users still exist when you view such threads, we now render the mentions with usernames:

Screenshot showing a list of two comment threads with user pings rendered as @-mentions

As a consequence of the above, @-mention autocomplete is now available for the thread title fields both when creating new ones and renaming existing ones (for those who can do that).

Additionally, thread titles now sanitize formatting away as they are always rendered as plain text. In the screenshot below, the thread's title is automatically generated from its content — previously, you would've seen "> This is a quote **bold**, *italic*, and ~~strikethrough~~" rendered instead:

screenshot of a comment thread with formatting stripped out from its title


P.S. Should you notice any issues with the updates or want us to improve anything, please let us know via an answer here or a standalone Meta post (do check whether there's an existing report or a feature request, though, as it might very well be that we are on it already).

History

1 comment thread

Thank you for all your work on these changes and for writing it up for Meta! (1 comment)

Sign up to answer this question »