James Dreben 
Do you want #Meta to be blocked on *your* server when/if they #federate with #ActivityPub?
Yes
No
(just show me results)
Poll ended at .
The Nexus of Privacy@Jdreben thanks so much for doing this poll!
If my math is right, this shows that 63.75% of the people who expressed an opinion (51/(51 + 29)) want their server to block.
It's striking because the (still-active) poll at https://mastodon.social/@nexusofprivacy/110456124484821875 currently shows only 29% of people expect their instance to block -- and multiple admins of large instances said they're not blocking.
Of course who knows what #Meta will actually do but we could well be in for some interesting times!
maegul@nexusofprivacy @Jdreben For sure!
That poll you link to is a great idea … highlights how there may be real tension between user bases and their admins. It makes sense though. There’d be all sorts of reasons why someone joins a particular instance, but only few would guarantee seeing eye to eye on many issues. Too much is conflated into what an instance is for this to be otherwise.
Otherwise, all the polling I’ve seen indicates decently sized splits on this issue. Interesting times!
Jon (now at neuromatch.social)@maegul #NotAllThePolls! This one is pretty close to unanimous: https://indieweb.social/@jdp23/110449505980762006
In terms of the tensions between users and admins, incentives are potentially different. #Meta's participation has clear benefits for site admins who are willing to share their users' data with Meta, as well as #ActivityPub developers who want jobs at (or research funding from) Meta.
Jon (@[email protected])
A #FediblockMeta poll on #defederation Which (if either) of these two hypothetical instances would you want your instance to block? - G is a hub for right-wing coup planning; hosts accounts that spew hate and disinformation; and is run by white supremacists - M is a hub for right-wing coup planning; sells ads that amplify hate and disinformation; contributes to genocides; and has a long track record of privacy abuses, discrimination, and law-breaking @[email protected] [ ] Bock G (but not M) [ ] Block M (but not G) [ ] Block both [ ] Don't block either
@jdp23 @Jdreben @nexusofprivacy
Yes, your poll and its point is well made!
The issue is that many will think of the “normal” people they know on these platforms and ignore their worst aspects as your poll highlights.
How many admins went to share data with meta? I’m actually not sure how admins would be thinking about the meta situation?!
@maegul There are comments from admins of some of the larger instances in the responses to https://mastodon.social/@nexusofprivacy/110458834683496365 It's striking that nobody there mentions the data sharing. In other discussions, though, the attitude I've seen is that "well all this data is basically public anyhow, Meta could get at if they wanted, so federating doesn't really change things."
@nexusofprivacy @jdp23 @Jdreben
Thanks! Hadn't noticed these replies, and yea, they not surprising. So basically all the mega instances are gonna federate unless stuff gets real funky.
Also, shout out to @quintessence breaking down their (hachyderm.io) moderation policy in detail! -
https://hachyderm.io/@quintessence/110461367732303169
quintessence :blobfoxflooftea: (@[email protected])
@[email protected] @[email protected] @[email protected] @[email protected] I spent a bit thinking about how to articulate how we proceed with policy decisions like these. There are a few layers that we consider for a situation like this. There are a few parts, so please bear with me while I explain. Short version: we take into account a variety of factors when choosing to moderate an instance. Meta (and others) are not an exception to this, but just business as usual. 1/9