Oh, I see. So the solutions in @louis88 post were actually proposals and not concrete solutions that can be used right now.
Thoughts about this @jarvie @asgarth (Peakd) @quochuy (Hive.blog) @khaleelkazi
(LeoFinance) @good-karma (Ecency), @chrisrice (Dbuzz), @theycallmedan, @starkerz (3Speak) @themarkymark (STEM geeks) ?
The proposed solution described in that post can be good and maybe also easy to implement. Most of the code required should already be there as it is based on the decentralized blacklists.
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.
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.