As mentioned in this forum post, we should start with a browser extension.

Sounds good. Just some other things to note about this approach:

Just to add to #2, we should probably just leverage the remoteusers table, adding a handle column (or however we name it). That would let us look up the handle and associated actor_id.

I think people will definitely expect mentions to turn into links, so we should address that now.

Awesome! Sounds good.

Hmm. Well that's good to know, but I think changing the entire post type really isn't the right solution. Do mentions work with Pleroma?

Yep, looks good

Looks great 👍

Yeah, just the script in that comment should be enough. I think the yesterday, today and tomorrow thing was in case we had those maps of dates to local translations -- so you can disregard.

Here's some starter code for handling when an admin presses the "Reset Password" button (ideally, put this in admin.go). It either accepts a new password or generates a temporary one.

This is another small one that'll be a nice usability improvement.

This would be another good one to tackle next. Let's use the same style, position, etc. as we do in the templates/chorus-collection-post.tmpl template.

That's in the javascript near the bottom of the page -- I believe it loads a default value named anonymous or draft via some h.js helper functions.

As mentioned in this GitHub comment, we want to support posting drafts with wf-cli, so we don't want this behavior.

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.

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

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