Today’s social media transform us into merely numbers.
No problem for me.
Polish account: @Kierunkowy74
Mastodon: @74 or @Kierunkowy74 (alt)
This time is probably unrelated to @ernest’s supposed inactivity. Actually, his another /kbin server, https://karab.in has been brought back on 15 of February.
Why not kbin.social? Well, this server is co-administered by FTdL (Technology for People Foundation) (https://kbin.social/m/kbinMeta/t/177112).
Entire FTdL infrastructure was down from 16 o’clock in Cracow to this morning.
Already available on /kbin.
(but no instance blocking on our side)
Proposed solution 2: Multi-communities
They are already implemented on /kbin - as Collections
kbin.social is only PWA right now. There is Interstellar app for Android being developed right now, but it is available only via Github releases (no Google Play nor F-Droid). And it works only on https://kbin.earth (or instances of /kbin fork called /mbin) right now.
Reddit’s multireddits (a combined feed from multiple reddits) are a small step in this direction on a centralized social network, and there have already been requests for similar Lemmy functionality (“supercommunities”)
They are already introduced into /kbin - as Collections
Meta’s fediverses probably also won’t be able to compete with Threads on this. Threads plan to make federation opt-in is the right thing to do from a privacy and safety perspective, but also means that people in Meta’s fediverses won’t be able to communiate with most of the people on Threads. And Meta has the option of adding communication between Threads and the billions of people on other networks like Instagram (which already shares the same infrastructure), Facebook, and WhatsApp. Longer-term, it seems to me that this is likely to be a huge challenge for Meta’s fediverses, but fediverse influencers supporting federating with Meta have various arguments why it doesn’t matter.
Is it really Meta’s fediverses, when communication between them and their alleged owner is fairly little and actively gatekept by their alleged owner?
Nostr
Authorised Fetch existed long before Instagram Threads. When it is turned on, an instance will require any other server to sign their request to fetch any post. This prevents “leaking” of posts via ActivityPub to blocked instances.
This setting is turned off by default, because some software are incompatible with it (like /kbin, Pixelfed before June 2023, maybe Lemmy too), because it makes server load higher, and it may make some replies missing (at least on microblogging side).
Another one is No Agenda Social, running on regular Mastodon.
Some Misskey instances do not report their MAU numbers. Misskey total MAU is undercounted because of this, but, looking at Misskey instance stats I suppose, that it’s 20 000 at most.
All Misskey forks (Firefish, Iceshrimp, Cherrypick, Foundkey, Meisskey, Sharkey), that are listed by FediDB make another 10 000 MAU.
It’s available on Rebased/Soapbox
Most instance admins are federating with Threads/Meta.
Not on Lemmy. Sort this Fedipact list by software and choose Lemmy to see this.
I was looking for recommendations for alternative instances… I’d appreciate anyone actually responding to my comment.
OK.
Largest Lemmy instances blocking Instagram Threads are (according to fedipact.veganism.social) lemmy.ml, lemm.ee, lemmy.ca, Hexbear, feddit.de, Beehaw, Lemmygrad, lemmy.dbzer0.com, lemmy.blahaj.zone, discuss.tchncs.de, sopuli.xyz, aussie.zone, feddit.nl, lemmy.zip, midwest.social, feddit.uk, mander.xyz, …
Mastodon since 4.2 version supports allows its users to opt into appearing into search results. Just respect this flag with Mastodon users, and you will be fine, IMHO
It’s perfectly possible to create a watertight federated network excluding both federation and scraping from Threads/Meta on Mastodon using authorized fetch and whitelisting.
Authorised Fetch is not supported yet by /kbin
I didn’t know. But perhaps it works.
Both Iceshrimp and Sharkey should have better compatibility with Mastodon clients
You can do it on PeerTube. Even automatically.