Defederate Meta

6 readers
1 users here now

This is a space on the Fediverse for organizing a widespread block of #Meta. Follow along on your favourite app from mastodon etc. Better yet, come and join in the conversation!

Please also see https://fedia.io/m/DefederateMeta/t/13712 for ideas on how to help out, and https://fedia.io/m/DefederateMeta/t/13685 for an explanation of why we want to #DefederateMeta

Rules

Rules:

We have zero tolerance for intolerance.

Absolutely no racism, sexism, transphobia, homophobia, ableism, xenophobia, or any other form of bigotry is permitted.

No spam, NSFW images, trolling, etc.

Keep it (mostly) on topic please. Fun is permitted :)

founded 1 year ago
MODERATORS
1
 
 

Decisions about who to federate with can be so much more interesting than just talking specifically about Meta. And from where I sit, this mag is dead due to ~~being so narrowly focused.~~ (edit: moving to another node… that explains it).

Consider that there are many nodes that are centralised and go against many digital rights values. E.g. all Cloudflare nodes are centralised and expose us all to corporate greed, manipulation, exclusion, and privacy abuses.

I propose renaming to something like “DefederateTechGiants” or “DefederateTechnoFeudalism”.

2
 
 

With the launch of Threads, there's been a lot of interesting talk about the safety and privacy risks it poses to people on the fediverse, if and when Meta begins federating. But it's also worth examining the risks to the social systems.

First, some background

Kbin and Lemmy are link aggregators. They work a lot like Reddit: users uprank or downrank posts and replies, and this mostly determines what content ends up having the most visibility. Reddit calls this upvoting/downvoting, and that's useful terminology - at the social level of the app, no one user has significantly more power or influence than any other. There's a certain level of democracy in this type of model.

But if Meta's Threads ends up federating with Kbin & Lemmy, using the ActivityPub protocol they have in common? Things could get a lot less egalitarian.

Threads Breaks Kbin & Lemmy

For example: let's say a Lemmy user has some followers on Threads. Suppose the Lemmy user posts something about a celebrity's new diet pills. Maybe one of those Threads followers replies, and tags the diet-pill celeb account. The post gets boosted by the celeb, and appears in the feeds of their millions of Threads followers. Even if only a small fraction of those accounts boost the post, it still easily becomes the all-time top post on Lemmy.

Now imagine things like this happening all the time. The Kbin/Lemmy rankings stop being egalitarian. A large account on Threads can instantly make a post show up in millions of people's feeds, and make it much more likely to get boosted. Your front page is now filled with posts about diet pills and limited edition sneakers.

But it gets even worse than this: Meta's algorithm is part of this dynamic too. After all, they're the ultimate arbiters of what appears in Threads users' feeds. If the algo pumps posts with certain keywords to their users' feeds? Kbin & Lemmy don't stand a chance. You'll see whatever Meta's algorithms want their users to see.

Interoperability - it ain't all it's cracked up to be

Let's break down what just happened there. Both Lemmy/Kbin and Threads are using the ActivityPub protocol to communicate, making them interoperable. Post some text in one, you can read it on the other. Boost in one, that boost shows up in the other. And so on. The standard narrative here is that interoperability is a noble and worthwhile thing in and of itself; walled gardens are opened up, new possibilities for collaboration/communication/creativity emerge, and everyone is happy and free.

Sounds nice! But clearly, some apps don't work very well when they're slapped together with others. The protocol does exactly what it's supposed to, but the applications are so much more than just the protocol. They're also systems that have social dynamics and power relations baked into their design, and even though none of the users in this example are trying to game the system - although they definitely could - Threads still makes the Kbin/Lemmy ranking systems useless. And if the ranking systems are useless, then what's the point?

The Point

Put another way: the computers can talk to each other just fine. But for our human purposes, at the social level, these two applications aren't really interoperable at all. Not all so-called interoperability is desirable or beneficial, and 'federation by default' shouldn't be assumed to be desirable or beneficial either. What's more, Meta is a monopolistic bad faith actor. Defederate Meta. Nothing good will come of them being in your network.

(see also part 2: Threads undercuts Mastodon's core mission with 'algorithm creep': https://mstdn.patatas.ca/@smallpatatas/110707812951733786)

3
 
 

Hi all, because this instance has tended to be somewhat unreliable, we'll be concentrating on the magazine at https://kbin.social/m/FediPact

Thanks for understanding during this whirlwind, hope to see you there :)

4
 
 

fedidb.org no longer has a list of FediPact instances for some reason.

The list below is being updated manually, so if an instance is incorrectly listed, or its signup status has changed, please let me know.

Sizes are MAU.

Asterisk denotes instance that is not on the official FediPact list, but has made a public announcement.

I've limited this list to instances with 25+ members in order to avoid both overwhelming readers, as well as the smaller communities that may not be able to scale up as quickly, or might otherwise find this disruptive. If you'd like your instance to be on this list, please let me know and I'll add it :)

full list of FediPact instances at
https://fedipact.online/
(and as always, thanks to @vantablack for her amazing work!)

INSTANCE SIZE SIGNUPS?

  • mas.to 24633 yes *will block initially and gauge effect
  • mastodon.nl 7592 yes
  • piaille.fr 7344 yes *"wait and see" with "very negative" outlook on meta
  • kolektiva.social 6719 yes *announced publicly
  • mastodon.art 6088 yes
  • pixelfed.social 6571 no
  • chaos.social 5876 no *announced publicly
  • mastodon.scot 5232 yes *will block initially and gauge effect
  • nrw.social 4856 yes
  • tech.lgbt 4400 yes
  • mastodon.ie 3986 yes
  • aus.social 3717 yes *announced publicly
  • beehaw.org 2408 yes
  • botsin.space 2383 yes
  • mathstodon.xyz 2285 yes *will block initially before determining future steps
  • mastodon.nz 2280 yes
  • pixelfed.de 1761 yes
  • eldritch.cafe 1502 no
  • climatejustice.social 1485 yes *announced publicly
  • livellosegreto.it 1307 yes
  • mastodon.radio 1034 yes
  • wien.rocks 1027 yes *announced publicly
  • octodon.social 1019 no
  • rollenspiel.social 898 yes
  • yiff.life 791 no *announced publicly
  • todon.eu 739 no
  • mastodon.eus 727 yes
  • blahaj.zone 669 yes *announced publicly
  • bark.lgbt 642 yes
  • lemmy.dbzer0.com 598 no
  • queer.party 597 no
  • discuss.systems 594 yes
  • vis.social 589 yes *announced publicly
  • kind.social 525 yes *will block initially and consult members before any change to that policy
  • social.coop 511 yes
  • sunny.garden 502 yes *announced publicly
  • toot.cat 442 yes
  • todon.nl 430 no
  • bsd.network 429 no
  • types.pl 419 yes
  • ludosphere.fr 415 yes
  • feddit.nl 407 yes
  • oldbytes.space 386 yes
  • scicomm.xyz 385 yes *announced publicly
  • mspsocial.net 364 no
  • merveilles.town 360 no
  • sociale.network 361 no
  • freeradical.zone 358 no
  • libretooth.gr 358 yes
  • veganism.social 357 yes
  • retro.pizza 344 yes
  • mastodon.design 341 yes
  • xarxa.cloud 328 yes
  • tabletop.social 313 no
  • 4bear.com 306 yes
  • vulpine.club 283 no
  • tenforward.social 255 yes
  • toot.site 249 yes
  • aussie.zone 246 no
  • stop.voring.me 242 yes
  • esperanto.masto.host 237 yes
  • funami.tech 230 yes
  • hackers.town 225 no
  • is.nota.live 222 yes
  • toot.portes-imaginaire.org 219 yes
  • mograph.social 217 yes
  • eightpoint.app 210 yes
  • lounge.town 210 yes
  • functional.cafe 210 yes
  • babka.social 208 yes
  • oc.todon.fr 208 yes
  • strangeobject.space 207 no
  • dragonscave.space 204 yes
  • corteximplant.com 201 yes
  • plush.city 191 yes
  • toot.si 190 no
  • dmv.community 190 yes *will silence meta instance(s)
  • kfem.cat 176 yes
  • genart.social 175 no
  • fedi.at 163 yes *announced publicly
  • mastobate.social 158 yes
  • pl.nulled.red 158 ? no
  • musicians.today 154 yes
  • icosahedron.website 152 no
  • outdoors.lgbt 150 yes *announced publicly
  • toki.social 148 yes
  • egirls.gay 145 ?
  • mk.absturztau.be 143 yes
  • mastodon.education 143 yes
  • sunbeam.city 143 no
  • cloudisland.nz 140 no
  • mastodonmusic.social 138 yes
  • unstable.icu 138 yes
  • catcatnya.com 135 yes
  • pagan.plus 135 yes
  • mastodon.mit.edu 133 yes
  • aoir.social 132 no
  • lingo.lol 131 yes
  • hispagatos.space 130 yes
  • smashingly.gay 130 yes
  • snowdin.town 123 no
  • dftba.club 119 yes
  • pony.social 118 yes
  • toot.garden 112 yes
  • hellsite.site 111 no
  • gensokyo.social 109 yes
  • wobbl.xyz 108 yes
  • cathode.church 106 yes
  • climatejustice.rocks 103 yes *announced publicly
  • climatejustice.global 100 yes *announced publicly
  • kafeneio.social 99 yes
  • indiepocalypse.social 93 yes
  • anticapitalist.party 89 no
  • pounced-on.me 88 yes
  • pipou.academy 84 yes
  • pawb.social 82 no
  • mastodon.com.pl 80 yes
  • recurse.social 80 no
  • fedi196.gay 77 yes
  • tacobelllabs.net 76 yes
  • tooters.org 76 yes *announced publicly
  • queer.group 75 no
  • deadinsi.de 74 yes
  • lgbt.io 74 no
  • indieauthors.social 72 yes
  • fandom.garden 70 no
  • sonomu.club 68 yes
  • meemu.org 65 yes
  • super-gay.co 64 yes
  • rage.love 62 no
  • efdn.club 61 yes
  • pixelfed.art 61 yes
  • toot.lgbt 60 yes
  • solarpunk.moe 59 yes
  • procursus.social 58 yes
  • theexpan.se 58 yes
  • polyglot.city 56 yes
  • india.goonj.xyz 56 yes
  • matapacos.dog 56 yes
  • nightcity.bar 55 yes
  • skastodon.com 54 yes
  • bantu.social 54 no
  • kitsunes.gay 52 yes
  • luzeed.org 51 yes
  • beach.city 49 yes
  • transfur.social 49 yes
  • gnusocial.net 45 yes
  • kitsunes.club 44 yes
  • craftodon.social 42 yes
  • nixnet.social 41 yes
  • floofy.tech 41 yes
  • chilemasto.casa 41 yes
  • autistics.life 39 yes
  • pleroma.envs.net 39 yes
  • cyberpunk.pics 39 yes
  • flipping.rocks 37 yes
  • ilyamikcoder.com 37 yes
  • bookwyrm.gatti.ninja 37 yes
  • iusearchlinux.fyi 33 yes
  • 0w0.is 32 no
  • blobfox.coffee 32 yes
  • girldick.gay 31 yes
  • evil.social 31 yes
  • comicscamp.club 31 no
  • simcha.lgbt 30 yes
  • Discordian.social 30 yes
  • laserdisc.party 30 no
  • systerserver.town 30 yes
  • WEATHERISHAPPENING.NETWORK 29 yes
  • cutie.city 28 yes
  • lediver.se 28 yes
  • slime.global 27 no
  • donotsta.re 27 yes
  • tsukihi.me 27 yes
  • seafoam.space 25 yes
  • gamemaking.social 25 yes
5
 
 

How to Kill a Decentralised Network (such as the Fediverse) écrit par Ploum, Lionel Dricot, ingénieur, écrivain de science-fiction, développeur de logiciels libres.

6
 
 

For the moment kbin doesn't offer the possibility of blocking an instance. The only possibility if offers is to "silence" it, that means, the user don't see the posts from this instance, but the instance (Meta in this case) can access the data posted by the user.
Kbin is a quite young project, and it is still in development, then for sure the implementation of a real block/defederation feature will take a lot of time.
I was wondering whether some of the new kbin instances have decide to defederate from Meta. I was not able to find the information.
In other case I will need to delete all my posts, find new moderators for the two magazines I started, and delete my account without to have another alternative.

7
 
 

Experts say it underscores the importance of encryption and minimizing the amount of user data tech companies can store

8
 
 

I wrote an article outlining some of the reasons why I think we should defederate Meta.

9
 
 

We, the moderation and administration of tech.lgbt, are signing the Anti-Meta Fedi Pact in fellowship with our peer communities. (https://vantaa.black/pact)

There is over a decade of precedent that Facebook will not have users' best interests as their guiding principle but rather profit margins, if it joins the Fediverse.

We at tech.lgbt have long held the belief that corporation owned instances are a threat to the core of the Fediverse: freedom for users to be themselves and to be a part of their communities. The 2010s saw the loss of online freedom when the majority of the Web was consolidated into a few destinations, and Facebook entering here could lead us back to centralization. Furthermore, NDAs for server admins will constrain our sovereignty online by binding us legally from disrupting their business.

We are not products. We are people, and we do not welcome Facebook in this space.

#meta #FediPact #facebook #project92 #mastodon #fediverse #FediBlockMeta #FediAdmin #p92 #MastoAdmin

10
 
 

Vanta, @vantablack@beach.city , has set up the Anti-Meta Admin Pact, a cryptpad form for fediverse instance admins to show their support for fediblocking Meta (Facebook, Instagram, P92). Admins can sign the pact here:

https://cryptpad.fr/form/#/2/form/view/Xz2YqIlhXIFXCitQApFe6Dp14O54I6vuqTUUgo8WbdM/

Anyone can view who has signed the pact here:

https://fedipact.online/

11
 
 

It would be the cruelest of ironies if folks who are falling out of Reddit and trying to build a new community here on a community-controlled, non-corporate network were to find themselves getting sucked right back into invasive techbro-capitalism through a backdoor. But that's exactly what might happen.

For those new to the fediverse, Zuckerberg is transplanting the userbase of Instagram into a new Twitter-type social network (currently labeled P92, possibly branded "Threads") which apparently federates through ActivityPub. This service will be online soon, possibly within weeks.

When and if this happens, the scrappy little communities of the fediverse will be invaded by a single, centralized "instance" of millions, even hundreds of millions, all conversing under Zuckerberg's draconian rule.

But it gets worse, because we're all connected in the ActivityPub network. Lemmy and kbin are federating. Both of these networks are federating with Mastodon to at least some degree. The data - our expressions and relationships - are moving around, as intended.

When Zuckerberg federates, all of this data will then be moving to him. He will ingest it into his data-mining system for surveillance and monetization. Those expressions and relationships will again be enclosed as "free labor" for a psychopathic techbro billionaire.

We've all got a stake in avoiding this. Feel free to help spread the word; subscribe to the DefederateMeta magazine, and the #DefederateMeta hashtag is handy. Instance admins are particularly and respectfully invited to consider the issue and clearly state their intentions on the question of federating with Meta. We're trying to help organize #FreeFediverse admins into a united front, ping me or magazine mod smallpatatas if you're interested in tying in.

12
 
 

I plead my case to Mastodon's lead dev @Gargron here: https://mstdn.patatas.ca/@smallpatatas/110516124221635618

tl;dr - Meta will suck the Fediverse into its algorithmic orbit based on sheer size alone, unless we organize a large-scale Fediblock / defederation.

Curious to hear what people think.

13
 
 

Exclusive: Calls for Meta to curb rise in scams on its platforms, which will cost UK households £250m this year

14
 
 

archived 6 May 2023 13:48:40 UTC

15
 
 

The Markup found many sites tied to the national mental health crisis hotline transmitted information on visitors through the Meta Pixel

16
4
submitted 1 year ago* (last edited 1 year ago) by smallpatatas@fedia.io to c/DefederateMeta@fedia.io
 
 

Meta's upcoming 'P92' app is reported to have ActivityPub compatibility (link)

Many users and admins are opposed to federating with Meta, due to concerns including, but not limited to:

  • user tracking, privacy violations, and data collection (link 1, 2, 3, 4)

  • embrace-extend-extinguish behaviour (link)

  • poor moderation

  • corporate influence over the ActivityPub protocol

  • centralization of the userbase around a single server

  • psychological manipulation (link) of users via algorithm

  • monopolistic behaviour (link)

  • intentionally allowing (and profiting from!) anti-Black racism (link 1, 2)

  • poor treatment of workers (link)

  • facilitation of genocide on Facebook (link)

  • failing to mitigate the distribution of CSAM on its platforms (link)

  • New, June 16th allowing scams to proliferate on their platforms despite user attempts to file reports (link)

  • New, June 16th rolling back COVID misinformation rules (link)

  • New, July 1st putting the onus on parents/guardians to protect kids from online predators (link)

  • a long history of breaching user trust (link)

In order to continue to build a new kind of social media, which prioritizes users over profits, and openness over walled gardens, we need to stand together in opposition to Meta's digital colonization effort.

What's making it difficult to form a consensus is that most admins haven't been communicating with users about what they plan to do (let alone asking the users what they want).

So, one very easy thing we can do is ask our admins if they're planning to block Meta, and if they aren't, ask them to reconsider.