sure, sounds good

Hmm yeah, good idea. I'd say we send them to some user page and show a message, but with the chorus config, things get complicated. Maybe just redirect to / for now, and we'll see how that works. I don't imagine it happening too often.

Here is the page so far. I thought of adding fancy click to copy javascript but decided to hold off until another time. It's not really important.

I think a rough process would be:

• download and extract into temporary location
• copy existing data to FILEorFOLDER.old, for each file or folder to replace
• move the new files to the existing locations, replacing them
• kill the server process, triggering systemd to restart.
• clean up temporary files
• keep .old around in case of some error? if so maybe old files should be moved elsewhere, it wouldn't take too much disk to keep a copy of the last installed version around though.

Right, those are all of them. And they only need to return the 404 status, not any other data.

For activity pub related endpoints, should it just be:

• outbox
• inbox
• following
• followers

Another thing to note: suspended users shouldn't show up in the Reader view.