When changes at Hivemind level are more effective, there still can be things that could be done purely on the frontend side. We could maybe add a custom parameter to the community account so that it can follow someone else’s mute list. When a post from a community is loaded, the frontend can load the external mute list and hide if needed. It would be faster if it was on Hivemind but still acceptable when done on the frontend. To be tested.
You are viewing a single comment's thread from:
Yep, makes sense can be done on the frontend too. I think that one of the disadvantages though is that all frontends would have to implement that separately.