@lerekofatwgo @hopeward thanks for the tip, but that also doesn't seem to work for me, neither in Tusky nor in the advanced web interface.
Mayve those are the components that break this? I did have the impression the timeline was server-side, though, and my choice of client wouldn't matter.
@neverpanic @hopeward
Okay. Just tested on the app that I use: Megalodon.
The workaround works correctly with the app.
I use the normal web interface, but I tried it with the advanced one, and it also works.
It might be your instance that somehow caches your timeline and not even muting/unmuting manages to reset it.