Like you can "try" but that's not showing on my place.
@jalcine YES. Some people want not just to speak but to force others to listen, which of course is entitled nonsense. I feel like there's a Black Mirror episode about this.
I da beeessssssssst jacky🙌🏽
In the recent thread about commentsEnabled, the usual suspects made the usual arguments, but it comes down to "commentsEnabled = false" means that my server is willing to break federation by not threading replies.
On a personal level, "Don't @ me" means I'll block someone if they do. If that moves into the protocol layer, software that doesn't honor it will get blocked.
Not entirely sure if that's your context here, but... 😇
@kaniini Yeah, same. I'm like babbling about it now because it's on the top of my mind. I've been doing some (very light) stuff with moderation in Koype (mainly black/white-listing) but that requires a bit too much intervention and isn't preventative.
@kaniini can you expand a bit on future proof? Like allowing the sender to potentially send content in the future?
@kaniini nice! this looks very flexible (thank god for not tying authorization too tightly to this) and future friendly (you could deploy this _today_ and provided it's permissive, other clients would just 'fail')
Social is the primary social media platform for the forth coming fourth version of Play Vicious, a new initiative built to bring attention to the plethora of creative acts that don't get the shine they deserve.
For more details about the project and how to support, go here.