Claire
Claire
``` $ curl https://mastodon.murkworks.net/system/cache/accounts/avatars/109/298/856/993/767/281/original/121d1fa8f753ed45.png curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1) ``` your issue is really weird but lies at the reverse proxy's level, it...
What version of Mastodon are you using? > Same here: I have a filter set to hide the words “threads” and “Elon”, and if it works well for Home and...
Hm, this might be a regression in the streaming server, going to have a look. In addition, it looks like the “explore” page does not currently apply filters properly.
> I think this and #25952 are related. That's interesting, I will investigate further in that direction. > It just seems like it's not grabbing the correct filters at all...
Yeah, the explore part is not covered by 4.1.6.
@yllekz what version of Mastodon are you using, and what apps, if any? Filters should be case-insensitive, and there is no wildcard matching. Each keyword can be set as matching...
> Does the 4.1.6 refer to an app? My original problem was with filters not working within a browser. Hi! 4.1.6 refers to the server version. You can check it...
> infosec.exchange. Not sure the version. infosec.exchange seems to not have updated after the 4.1.6 fix was introduced!
I think so, yes.
This sounds fine, but I'd like someone using OpenStack Swift to test that it isn't breaking file uploads.