The link goes to this users Mastodon post on the subject. I’m going to copy part of the text of his post without having to post the Threads post they were shown. Click through if you want to see for yourself, avoid if such things are upsetting to you....
I’m not entirely sure if such an instance exists, but just letting you know that in case you can’t find any, a reasonable compromise would be to join an instance that’s enforcing authorized fetch (and is blocking threads)
this will make it harder for facebook to read your data through federation alone (i.e. even if a post of yours get boosted by someone with followers from threads, it won’t “leak” there)
there are ways to bypass this of course but if facebook is found to do something of that sort they would out themselves as actively malicious which would definitely get a reaction even from the “wait and see” crew
the camera app may literally be the only thing that every OEM changes! even the most AOSP-adjacent OEMs have bespoke camera apps with their own secret sauce
it works wonderfully if you want a small tight knit community, but not for something that aims to replace something on the scale of twitter (without something extra like federation, which is still not ready in bsky/atproto)
mastodon implements it, pleroma/akkoma probably implements it, pixelfed implements it, firefish and iceshrimp implement it (sharkey has a PR implementing it opened just today), gotosocial not only implements it but enforces it, with no ability to turn it off
notably, none of the threadiverse software implement it, and no software other than the aforementioned gotosocial enable it by default.
mastodon.social sends a single federation activity to www.threads.net’s sharedInbox. threads’s internal systems handle all the visibility and routing to followed users and whatnot. the same thing happens in the opposite direction for threads->mastodon (or whoever).
now in theory this is an optional part of the specification and you can in fact send one activity per person if you really want to, but considering how widespread it is (and how relatively easy it is to implement) you’d have to be intentionally and explicitly malicious to not use a sharedInbox if the remote server indicates it supports it.
i have attempted to build my own federated stuff (none of them actually federated “in real life” though) so i did read the specs but quite a lot of these are from my memory and if there’s anything i know is that my memory fuckin sucks lol
you can disable the webpage and unauthorized API if you so choose. mastodon and pleroma/akkoma provide these settings. gotosocial hides all posts with an unlisted visibility from public pages.
authorized fetch only provides protection for activitypub, it’s just a single component of a layered stack of protection you can enable depending on your exact threat model.
the privacy threat model of Lemmy is significantly different from a microblog, which is the current target of threads.
(also have none of you heard of consent?)
cc @FaceDeer this reply also applies to your reply
I used to think that there would be 1, main ‘Fediverse’ with all of the ‘big instances’ connected to each other. The recent Threads debacle has shown me otherwise....
re active users: they’re a large open registration instance, they likely have a fair chunk of twitter people who joined during one of the many migrations and decided not to stick around.
if you were to focus this on just Lemmy itself as opposed to the wider fedi (“Especially given that there was just an update allowing for individuals to block instances they don’t like” implies that’s the case) you already have nothing to worry about as you encountering a threads user here will be even slimmer than encountering a mastodon user.
threads is primarily targeting the microblog/personal side of fedi. the incentives and privacy expectations are quite different compared to this side of fedi
considering most Minecraft mods directly mess with the Minecraft code as opposed to going through a well defined API (forge and fabric only provide so much) you can’t really make that work without outright stealing Minecraft code
the best you can make would be resourcepack and datapack compatibility. maybe whatever molang stuff bedrock’s up to
deleted_by_author
Explains a lot (lemmy.world)
What's the consensus on swearing here
Noticed not many people use curse words....
Instagram Users Shown Transphobia As Promotional Tool To Join Threads (neuromatch.social)
The link goes to this users Mastodon post on the subject. I’m going to copy part of the text of his post without having to post the Threads post they were shown. Click through if you want to see for yourself, avoid if such things are upsetting to you....
Lemmy MAUs climbing back up! You love to see it. (lemmy.zip)
rule (lemmy.blahaj.zone)
How to capture good photos on a smartphone (files.catbox.moe)
https://files.catbox.moe/chhqbb.pngSource
Rule (lemmy.blahaj.zone)
rule (files.catbox.moe)
If we're going to have an effective strategy against FB/Meta, we should clear up some misconceptions around defederation
((I’m not an expert, I’ve been reading up on things as much as I can. If there’s an error, I’ll happily correct it!))...
The Fediverse is working just as intended.
I used to think that there would be 1, main ‘Fediverse’ with all of the ‘big instances’ connected to each other. The recent Threads debacle has shown me otherwise....
Rule (lemmy.blahaj.zone)
41% of fediverse instances have blocked threads so far!!! (tech.lgbt)
What if we kissed under the Rule? (lemmy.ohaa.xyz)
MineClone2 0.85 – Fire and Stone (git.minetest.land)
cross-posted from: lemmy.world/post/9752285...
rule (lemmy.cafe)
Flatpak can look daunting... (feddit.de)
Disclaimer...
Integrating f-droid to lemmy
hope this post wont sink by the threads posts : D...