I think there are good reasons to not let corporate interests join the space we built to escape them, but I guess every instance is free to (de)federate with whomever they want.
So let’s say my instance (mander.xyz) defederates from Meta but another Lemmy instance that meander.xyz federates with (let’s say “misguided.ml”) does not. What happens when someone from Meta comments on a post from misguided.ml and others from misguided.ml comment on that comment? Will I see the comments on the meta comment, but not the original meta comment itself? Or will I not see the entire thread?
My guess is the branch where the meta comment starts and all it’s children will not arrive at your instance.
That’s correct, any thread starting with a Meta comment will disappear from your perspective.
On the other hand, assuming Meta hasn’t defederated mander.xyz, Meta users could still see and comment on posts that you made on misguided.ml. You wouldn’t see any of their comments, but users of misguided.ml would be able to.
Federation is a bilateral agreement
You will see all comments on “misguided.ml”
Except the one from Meta? So the comment thread would have an empty spot or something?
There wouldn’t be an empty spot, your instance would never know that comment was there to begin with. You would be able to see it if you clicked through to the other instance of course.
I don’t think so. It will have all comments including comments from Meta.
Ok, but I am talking about a nested comment structure right? So the Meta user comments on a post/comment of misguided.ml, and then misguided.ml users comment again on that comment.
If I don’t see the Meta comment in the middle, the conversation would be quite weird to me? I would see people respond to something I don’t see?
I believe how it works is the comment from the user on the defederated instance and ALL child comments of it do not show up on your instance. So it’s as if that conversation just stopped after the last person from an instance that you’re federated with commented. You wouldn’t see anything from defederated commenters or the replies to them, even if they are replies from Instances you’re still federated with.
Login to Beehaw and check out a post from a Lemmy.ml community on it, and then look at that same post while logged into Lemmy.world and you should see the differences - because Beehaw defederated from Lemmy.world.
Ah, sorry, I misunderstood. Could probably find some examples live examples by looking at any convo with folks from beehaw and lemmy.world or shitjustworks, and viewing that thread from the different instances
The fediverse is a natural response from corporate interests, which most of the cases involve freedom of speech and some dank humor.
If meta decides to join the fediverse to reduce their payload and spent less cash on hosting solutions, that is fantastic and they are welcome to do so.
But meta joining the fediverse will not mean to give them full control of the decentralized network, so there is nothing to fear of, naturally they will defederate uncomfortable communities in order to remain “normie friendly”
We can do the same but i believe our stance in the fediverse is to remain open, borderless and decentralized AF
I think there’s a chance meta or another big company will attempt to take over. This could be by creating a new client or library that everyone starts using and then suddenly make breaking changes that aren’t part of the official activitypub protocol.
Google used to use XMMP for it’s chat but eventually it was no longer compatible with 3rd party servers.
No idea what will happen, just don’t get too complacent. Being decentralized now doesn’t mean as much if a couple giant entities end up owning 90% of the network.
This is what could happen. Learn from XMPP and don’t let corpos into the Fediverse.
ActivityPup is an open and public protocol. Anyone can use it however they want, but as a community we do have some control over who we federate with, so excersize that control.
One of the strengths of the federal system is the freedom to choose to “federate” or “defer” any entity. This allows the community to maintain control and limit Slither io who can participate in their space.
So let’s say my instance (mander.xyz) defederates from Meta but another Lemmy instance that meander.xyz federates with (let’s say “misguided.ml”) does not.
Slightly unrelated, but if you don’t want your content to show up for Meta, unsubscribe from communities originating from instances still federated with Meta. The sunny side of fragmented communities means there are probably alternatives without that downside.
Personally, I find the idea of different versions of a comment section (in text and votes) both fascinating from a technical perspective but also horrifying as a simple user. For various reasons. Sometimes people refer to what’s going on in other parts of the comment section. Or I don’t want to repeat what others already said. This has so much potential for confusion.
So even for users from instances which are federated with Meta, this might be a reason to avoid engaging with Meta. Don’t comment on posts from Meta users, don’t comment on their comments. Your contribution will probably be invisible to most other users.
I wish that all federated software had an easy way to migrate your user, with all and posts, to another server whenever required. That way you’d be able to jump ship elsewhere if you disagree with your current admin’s defederation policies. Mastodon is really dragging the feet on that one, and both Lemmy and Kbin don’t even allow exporting your list of subscriptions yet.
Is there resistance against it on Mastodon? I thought it was just a technical issue? (I mean specifically post migration).
There are several hurdles specifically regarding post migration:
- How can an instance handle a truckload of new posts that were originally posted elsewhere, especially as they might cause a flood of notifications to old followers
- How to ensure that all references to old accounts and old timestamps are correctly migrated
- How to properly prove that the old account and the new one are one and the same, as malicious imports may be used for plagiarism purposes
- And last but not least, how to handle imported posts that may be violating the terms of service of the new instance!
That sounds quite challenging yes. 😬 Thanks.
to be sure that your posts don’t end up on the META Servers you need to post with ACL - Access Control List - but since lemmy does not offer that jet you may have to use an other fedi software with ACL
