Claire
Claire
@Gargron do you mind reviewing this?
This is not a client-side issue but a server-side issue. It's also caused by the ElasticSearch code path, which explains why it doesn't occur on all instances. The culprit is...
@FediVideos this is still the same issue, we already know it depends on servers because it depends on whether ElasticSearch is enabled
The thing is, it's done on the receiving end, the sent toot contains no indication as to what should be used for preview or not.
The choice of which link to use for the preview card (if any) is done server-side on a toot per toot basis, so introducing a user-specific setting would require significant...
I'd rather that we wait for the revamp of the filtering system before we make any such change. This can wait.
> can't you just mute the keyword `@username` or does that not cover the situation fully? You can approach that with filters on `@username`, but `@username` appearing in the text...
@kit-ty-kate with some logic similar to #7459 we could probably fetch private toots from a remote user, yeah. Fetching “up to the N last toots” on first follow is easy...
Yes, you would need to know the URLs, which you typically don't know when those are *replies* to a toot you can see. It's a bit of an issue, as...
Agreed wrt. regexps not being very user-friendly, although I do think being able to write regexps here is useful, maybe each filter could be either a word or a regexp....