@nepfag that's what I personally think about the matter, even if we have a proper access control that doesn't waste tons of cpu cycles, screenshots and copy/paste still exist. still, this is something people a lot of people wanted and mastodon has implemented it with their "safe mode" , so at this point we have 3 options
1) implement the feature as-is and waste a ton of cpu cycles 2) implement OCAP , which only requires httpsigs for capability negotiation and has more precise control over permissions 3) break federation with a (probably) sizable chunk of mastodon instances when a new version is released
the second one is the most sane imo, it would also allow us to compact databases further by purging follower-only objects
I guess if I'm going to change my legal name it's gonna be using lojban so the prononciation is a bit flexible yet clearly defined and compact. Kinda the other way around compared to my current one…
PSA: if you are a gamedev, indie developer or whatever and thought about registering on gamemaking.social , I recommend not doing so. the guy(s) hosting this instance blocked my instance because I asked why kawen.space was blocked. a simple question, instant block. I still got no answer, so in case you get any problems, or more precisely: they get problems with you, they will probably just block you as well, without any chance to solve whatever the actual problem is. people so uncommunicative and ignorant shouldn't be responsible for hosting a platform for your games.