Post APmy8GHEFIFxYkzHeK by atomicpoet@atomicpoet.org
(DIR) More posts by atomicpoet@atomicpoet.org
(DIR) Post #APmy8GHEFIFxYkzHeK by atomicpoet@atomicpoet.org
2022-11-20T08:00:46.107252Z
1 likes, 0 repeats
I've blocked so many people on this instance over the past 48 hours.It's been a lot of work.
(DIR) Post #APmz9lyFzeyI6IOjoG by atomicpoet@atomicpoet.org
2022-11-20T08:14:09.140021Z
1 likes, 0 repeats
You want to know about moderation? Try having a thread get boosted nearly ~5,000 times. That will attract lots of heat. One thing I wish Pleroma had was an ability to lock a thread. Then I wouldn't have to constantly be playing whack-a-mole with folks who don't actually *bother* to read threads -- but still feel the need to respond.😣
(DIR) Post #APmzJb67H67DH1l76u by sean@social.deadsuperhero.com
2022-11-20T08:18:17.725326Z
1 likes, 0 repeats
@atomicpoet Two things I really want to see in fediverse apps in the future:1. Object Capabilities that can define what can be done with a piece of content, and by whom.2. An edit function that can be used to adjust it at any time by the author.
(DIR) Post #APn03r36Ifoo4CPCaW by atomicpoet@atomicpoet.org
2022-11-20T08:26:22.608410Z
1 likes, 0 repeats
@sean It's clear to me that *lots* of moderation tools still have to be built. If there's one critique I have about the Fediverse it's that it seems to be built for engagement first, moderation second.
(DIR) Post #APn2KhrLv4PuOh4dDk by sean@social.deadsuperhero.com
2022-11-20T08:52:01.410944Z
1 likes, 0 repeats
@atomicpoet Yeah, that's accurate. I think part of this is because of its history.See, OStatus used to be the standard used here for federation. It was pretty easy to implement - an object had a single feed with items in it, someone receiving those items would interact with it, a mechanism would slap those interactions back upstream. It was a much smaller network, used by enthusiasts. Privacy was a secondary concern compared to just making cross-server messaging work.Later on, two competing projects would independently come to the conclusion that OStatus couldn't offer enough to solve this problem: Diaspora, and Friendica. Friendica worked really hard to build a custom protocol to address this. Diaspora simply adjusted the OStatus formula to fix a few things and incorporate encryption and key-signing for messages, and largely called it a day. Both worked, but Diaspora became the popular one at the time.Friendica split off into half a dozen different research projects over time, developing a powerful protocol capable of securely moving accounts around, building communication relays with accounts, and even granting remote permissions to those who visit your page. This was Zot, and it remains absolutely brilliant, but at times is too complex for most people to understand.Which leads us to ActivityPub. ActivityPub is kind of a product of consensus between a lot of different stakeholders in a W3C working group. Some of these were fediverse people who had worked on OStatus and Pump.io-related stuff. Some of these were people more interested in data graphs or interconnectivity between applications.The people who had worked on most of the privacy stuff were absent. While privacy mechanisms were given serious consideration, their supposed suggestions for implementors were a little on the vague side, and didn't really account for some of the important lessons learned. There were also other developments happening way outside of the bubble that nobody was really aware of, like OCap.That being said, ActivityPub mostly came out in pretty good shape, especially now that there are implementations and standard conventions that developers rely on to make it all work. Right now, there's a lot of research going into how we can fill in the missing bits to give users a greater sense of control and flexibility of objects in a network.Anyway - a lot of the current state of things comes from the evolutionary history of these protocols, which ones became popular, and what technologies / research were readily available at the time to people involved. There were also a lot of blind spots towards things like risk reduction and harassment management, because these technologies developed from smaller spaces that likely didn't experience that stuff as much in the early days.
(DIR) Post #APn32UszW3vutzimDA by ludo@ruby.social
2022-11-20T08:42:42Z
0 likes, 0 repeats
@atomicpoet @sean Twitter provide a way to limit answers by the author's followers only. Cool feature of Pleroma to lock a thread :)
(DIR) Post #APn32VOBe4t2SkJgps by sean@social.deadsuperhero.com
2022-11-20T08:59:48.918525Z
0 likes, 0 repeats
@ludo @atomicpoet yeah, and those kinds of settings are honestly ones we need. But, in federated systems, they would need to rely on more robust systems to counter circumvention.Which is why Object Capabilities could potentially be a huge deal. An OCap-capable system could more easily conform to conditions like "only let my Mutuals collection respond to this", and the resulting object would just drop any potential responses from non-mutuals.@cwebber is doing amazing research in this space with Spritely, which could really put the whole network in a really healthy place one day.
(DIR) Post #APn5Uhl9RhxiqTdGfw by atomicpoet@atomicpoet.org
2022-11-20T09:25:38.242158Z
1 likes, 0 repeats
@sean I'm familiar with a lot of that history, but that's a killer summary. Of course, I think about all this now because this is a time I'm doing a *lot* of moderation.