No, having the mere ability to edit tickets makes it a BBS (illegal), whereas not having the ability makes it a mailing list (legal). You need to have a way to disable the editing feature altogether and make it a mailing list, or you are liable.

Certainly you cannot be familiar with all the law in the world? There have been numerous cases in which people have been found guilty of administering Facebook groups, so it seems like it would hold for issue trackers as well. This is a matter of great concern for me as I do not want to be fined or imprisoned for running an issue tracker.

(I'm not saying you, being an American, are at any risk, I'm saying many European users (e.g. all Swedish users) of the platform who administer their own issue trackers are, whether they host the site or not)

In informal conversations, it's often useful to write newlines without beginning a new paragraph.

In Markdown, this requires you to use two spaces. There is no good reason for this, and it's extremely annoying - when would you ever want to put a newline in the message but not have it encoded in the HTML?

I propose that a departure from the specification is made so as to emit a newline with each newline in the input.

It seems like you can edit posted issues. This causes some regulatory issues in with regard to many European countries' hate speech laws: any administrator of such a site is liable for all content posted there, even if he or she is not the host or operator. Conversely, hosts are not responsible. However, e-mail conversations are exempt, and thus logs of mailing lists should also be.

It would be really nice to have an option to disable all editing of content and have it work like lists but with a HTML form to send e-mail, to achieve the legal fiction of it being a nice front-end around a mailing list. Otherwise, users from my country and many others would be prohibited from using the issue tracking service to its full extent, having instead to rely on lists for both discussion and issue tracking. In particular, messages from anonymous users couldn't be permitted, as it's possible to craft messages which, while illegal, are not readily detectable as such - there is a significant regulatory uncertainty in the field.

Here is an English translation of the relevant Swedish law:

https://web.archive.org/web/20060504212948/http://www.sweden.gov.se/content/1/c6/02/61/42/43e3b9eb.pdf

In the documentation for todo, it just says there are several. Nothing about which ones. It would be nice to document it somewhere.

Is this the issue tracker for all documentation or just for man code? sr.ht-docs isn't in todo.

order: the order in which tickets are displayed. By default this is by time of last update Wouldn't it be better to sort them by time of last activity? It seems more reasonable that some really old ticket someone submits new information to should be on the front page than some ticket that's just fairly fresh, even if it has no activity.

It's regrettable if tickets which don't grab attention get lost, but it's arguably even worse if tickets which do grab attention get lost. In the worst case, you can always bump a ticket which has fallen down, but it's in poor taste to intentionally duplicate a ticket.

Perhaps easier is to have a set of hash(user ID + thread + message) and check if it's unique. Can't see why you would want to post the same message twice in the same thread.

There's a bit of friction in creating a new webmail address. If you would just have to fill out a captcha I think that would prevent most spam, along with IP blocking and more conventional measures.

People could still fill out your captchas and spam, but that goes for webmail as well. If you're going to start requiring only 'good' email providers like Gmail, you're effectively deputizing them to do phone verification and all that icky stuff and then turning a blind eye to it.

On a similar note, another very cool thing to lower the friction would be so-called 'tripcodes'. You write your username and password while posting, and it posts your username along with the hash of your password. If you want to create an account later on, it could attach all the comments you posted by seeing if your supplied password hashes to anything interesting.

If I am at https://todo.sr.ht/~sircmpwn/todo.sr.ht, I can see the builds by going to https://builds.sr.ht/~sircmpwn/todo.sr.ht. But if I click the header link "builds," I go directly to the main page of builds. This is a bit confusing, since if I'm at todo it will show todo in darker text.

It would be nice if I could see for example the git for a project by clicking on the git text in the header.