Idea 2:

👍

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

pixelfed doesn't support the @user syntax (it's pixelfed.social/qwazix and not pixelfed.social/@qwazix) so I think it's not a good idea to do the prismo thing.

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.

I'm looking into turning handles into links and I think I should link to the user on remote instances.

I opened an issue on tootsuite here

Ok will do.

Awesome! Sounds good.

Just pushed branch activitypub-mentions where mentions work on pleroma.

I'll test with pleroma and then open the issue with mastodon. I'll also look around plume.

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?

It seems that Mastodon ignores mentions in "Articles". Maybe now that mastodon has the [expand] functionality we should consider using "Note" when federating (at least up to a certain text length at least).

Yep, looks good

ok, how about this:

Looks great 👍

The current UI status, showing the success message after submission.

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.

So this seems to work well with only the script provided. Where were the uses of yesterday, today and tomorrow?

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.

@matt I have the template part done and working, just wondering if you remember off hand where we look up the last-selected publish choice.

I've been thinking about implementation details for this.

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.

I'll take this after T609 is in

I like the paper key idea, or even a set of recovery keys. Usually 8-12 random keys that the user prints or writes down. Then when needed they use one in place of a password, and are directed to set a new password. These are single use.

This was put on hold for now as the fix mentioned only allowed a single tag/category and the 3 supported feeds all allow multiple per item.

Perfect 👍

Looks like Category is missing from the feed Item type, there was an issue where a PR was mentioned but never opened. https://github.com/gorilla/feeds/issues/51

This is important for people with different workflows, so this is the next highest priority after T571: Import posts from WordPress and {T646}.

I've already started on this on Write.as Web, so I'll finish this up.