Senior Software Developer, Densho
Work as if you live in the early days of a better nation.
Right now there's
README.rstbut sr.ht only supports Markdown.
I get the whole UNIX-is-the-Hole-Hawg serious-users-don't-need-to-be-protected-from-themselves aesthetic, which totally works with the brutalist design which I also appreciate. It's true that if you're the only user it's easy to just git-push again, and it's also true that on this service deleting the Git repo doesn't also remove the tickets or other pieces.
But repository deletion is one place where I'd want the confirmation to be a little stronger. If you're running a serious project with a lot of contributors then deleting the repo might be a serious inconvenience. You might have to contact contributors to get various branches back, etc, etc.
I was also thinking about how the ticket owner or comment author's email is visible in theFromfield. Certain people might find that disconcerting. Of course, if things going on in mailing lists is a baked-in feature of the system itself that's just the way things are, in which case it would be good to write that up in your explainers so people know what they're signing up for.
When someone comments on a ticket an email gets sent out to the ticket owner (and presumably other participants in the ticket). In keeping with theemail-driven Git workflowidea, it would make sense for replies to these emails to show up as comments on the ticket page.
Replies to these emails are addressed directly to the ticket owner, so they don't go back into the system.
Ah, I see, comments go out as emails. Kinda impossible to take those back once you've sent them. It's a design decision.
Currently the todohomepage (https://todo.sr.ht/) only lists tickets for the user's own repositories. It would be useful to see links to tickets I've submitted or otherwise interacted with in other projects.
This page (https://todo.sr.ht/~sircmpwn/todo.sr.ht) displays aConfigurelink to logged-in but non-owner users; if you click it, the edit form is displayed. There is a smallyou can't edit thismessage but the Save button is present and clickable (yes I clicked it, in the spirit of collecting data for this bug report). This results in a 403 Forbidden but the form should probably non be live in the first place.