There are a few deeper issues to discuss that aren't part of this task:

@gytisrepecka I think we'll want to go with option #1, so we can factor in instance privacy settings, and have totally private media files if an admin wants it. I just updated the description with some ideas I have for the very first version of this.

So I have wrote a piece of code for image watermarking: takes JPEG file as input, uses PNG with transparency as watermark image and saves the output. Plan to release it as separate library with following functionality:

Partially implementing this as part of my work on T401: Post list paging and T714: Improve core navigation.

Getting much more important as Write.as grows past 500k posts on the platform.

To add to this list:

sub task status:

This is looking really good so far! Have been using it myself lately and it's been great.

I was looking around the other day for image processing libraries written in Go. There are some to compress or change format of the image, resize, etc.

What could be the better way to store uploaded images?

As discussed in #174, this is now the "silence" admin feature. See that PR for remaining items needed to resolve this.

Addressed in writefreely#189.

PR for writefreely is up including CLI flags, next is to add things like federated deletes for all collections including default (i.e. username) and and posts if they are being deleted as well.

status update

Looks like this function also already exists in writefreely under *datastore, but is still out of date and needs modification.

Note: implementation details are out of date and only apply to Write.as. For implementation in WriteFreely, refer to [deleteAccount()](https://phabricator.write.as/diffusion/W/browse/master/database.go$2674) func in rW.

{T706} solves our immediate needs for #write.as_for_teams, so we'll do that first. Then we can look at addressing this.

Noting here re: icons

progress so far

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