@neverpanic I think I saw what you’re describing… it doesn’t work backwards in your feed, but once the change is made it will sort the posts now, going forward.
Top-level
@neverpanic I think I saw what you’re describing… it doesn’t work backwards in your feed, but once the change is made it will sort the posts now, going forward. 7 comments
No problem! I was having the exact same issue, so I dug around. Some people suggested unfollow/follow, but it seemed too drastic. So I tried mute/unmute and it had the same effect, and there's no risk of offending a mutual. @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. 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. @hopeward @neverpanic I can confirm that it does work. |
@hopeward @neverpanic
I think it's a bug.
The workaround I've found is:
- put the account in the list
- mute the account
- refresh the timeline (not sure if it's necessary, but it doesn't hurt)
- unmute the account
Basically works for all of the similar situations where the effects don't seem to work retroactively.