@
Brian Ó 🐟 I have deeply mixed feelings about this. Aside from the debatable Freedom of Speech concerns, which i know we are not on agreement on, I think the larger concerns that I have is that all of this blocking/policing/censorship is done via one-off solutions, not part of diaspora*'s native capabilities, not within the individual user's control, and solely at the discretion of the podmin. That said, I understand where you and the other so-called #
cuckpods are coming from.
Perhaps if diaspora* provided a way to natively manage a pod in a manner that allowed the flexibility for the podmin to set global defaults, but also allowed users to change those defaults if they want to, then I wouldn't have an issue with it, even if the end result is basically the same as what you have done. Perhaps it is just a semantic distinction at some level, but in my view, there is a difference between configuring and using the platform to achieve a result and going beyond the platform to achieve a similar result.
I really would like to see configurable user and hashtag filters at the pod level, but in away that would enable individual users to edit those filters to customize their own experience.
The user filter would suppress posts and comments authored by users on the filter list. That content would still exist in the pod's database, but it would be suppressed. an individual user could then add or remove filters to achieve the desired experience. By allowing the podmin to set a global default, the podmin can then create the desired user experience for new users.
A similar mechanism should be available for hashtags. For example, if you don't want the #
nsfw content to be visible on your pod, then you add the appropriate tags to the global default filter on your pod.
