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

In the interim, this will be an extension

On mobile the split should be horizontal, with the preview up top. It should also scroll with the editor content.

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).

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?

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.

I've been thinking about implementation details for this.

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.

More user discussion here.

We decided on pherephone for the name: https://github.com/writeas/pherephone

We can at least get started on the frontend now.

We should investigate the feasibility of doing mentions with Markdown links, e.g.

Also tracked on GitHub #134.

I threw together an offline importer for this: rWFM / https://github.com/writeas/wf-migrate -- for reference in building this into the web application.