Yeah good point by @cendawanita about permissions (or lack thereabouts) for #kbin et al to scrape the #fediverse and put posts/toots into magazines. It feels like so many #Mastodon admins are blind to how the fediverse beyond Masto software & the Masto API actually works.
Seeing such folks write lengthy posts about defederating Masto instances running Vyr's search patch while the rest of the fedi has #FullTextSearch and the #Threadiverse scrapes it with next to no backlash. It's like folks don't know that there's a bigger problem with #ActivityPub re #privacy and #safety than Website Boy's latest antics, and we need to push for #FediverseSafety and privacy flags at a ActivityPub protocol level. Until then, everything is just a non-binding, non-enforceable agreement about cultural norms that there's seems no consensus on; and definitely no focus on minority safety, rather features some will claim are wanted by a majority.
@jo@cendawanita I agree this is mostly one level higher problem (at the protocol) rather than software implementation or etiquette/norm issue
The software boy/gal will try as they might to create some kind of privacy shielding around #activitypub weakness, but at the end it will be leaky as hell... privacy can only be applied (if and only if) the protocol supporting it in the first place, no amounts of social pressure or dev pull request will fix this deep state problem 😔
Add comment