Nice, didn't know that. Haven't used sh for anything other than tickets. Pardon for my knowledge.
I have for this in GitLab, and hoped it would appear in GitHub.
Tracking progress, and listing everything deemed useful has been usually done in Etherpad.
I would suggest a 'whiteboard', what's editable by everyone (or only contributors, edit history should be enough to prevent abuse).
It's a great way to keep people working on the ticket from reading everything again; a summary, current status (collaborative checkboxes are on GL), and more can be accumulated there.
The current description could move to author's first comment, possibly highlighted.
Quite frustrating to lose all the user has written after doing a check 'did I just file a duplicate' (no you did not..), or adding additional details, refrencing other tickets.
One way to do this would be to also submit the ticket title and description with the search, include the title and description with search results. I have seen browsers retain the text content themselves as well. Don't know too much about it.
Light JS is also an option.. ..probably rather not.
Comment threads would be nice, keeping discussion organized, easy to start reading from zero (40 comments!), and if reply is in a thread, don't send everyone a notification.
Having other 'reactions'/'emojis'/etc doesn't really server purpose.
A simple +1 and -1 for the ticket would be nice.
Helps avoid 'me too'; indicating the count on ticket list provides developers a quick overview of demand.
Comments could have +1/-1 as well, maybe in the future, maybe never.
Pasting it gets the following preview:
Bibliogram Post by Tennyson Gallery of 2 images. @disclosure Hey Howard! Cooked somethin’ up for ya! feat. @erezzobarymusic #BeGuy
There are 2 videos.
No idea how to edit comments, newlines went poof, I didn't markdown correctly, I guess.
The idea would be foo hosts (or is user of) instance foogram. Foo visits a site: Right now: instagram.com -> foogram Idea: instagram.com -> foogram bibliogram.art -> foogram any other bibliogram instance -> foogram
You might end up on non-foogram bibliogram if somebody shares a link to the other instance. Having the trust of your own instance (under privacy and that the RSS feed you get doesn't go poof).