Alarming.

If you can think of two boats meeting in open water, there’s porn of it on the internet.

This was the best explanation of how this is hurtful that I think you could possibly put together. I came into this thread skeptical of this being a real concern. This changed my mind. Thank you.

The Meaning of Life, too. Those two Python flicks never get old.

I appreciate that his obit outlines how exasperating Kevin was. But ultimately he did a lot of good even if he did get a bit of a god complex from his notoriety. No matter how you slice it, 59 is too young, and Kevin was far from enough of a jerk to deserve that fate. I hope his family can mourn and find peace. See you on the flip side, Kevin.

I think it’s reasonable to argue, “a super like that also shares the post is functionally different from just a super like.” It doesn’t seem nit-picky when discussing the reasons why someone might choose one service over another to want to be precise about the mechanics of one of those services, no?

Uhhhhh. Not sure which fucking Lemmy instance banned you, but sounds like a real bum out.

I like both Orbit and Helios. I’m fine with Memmy, but understand the intent.

Honestly, “Orbit: A Fediverse Client” kinda has a nice ring to it.

I like both Orbit and Helios. I’m fine with Memmy, but understand the intent.

Honestly, “Orbit: A Fediverse Client” kinda has a nice ring to it.

For sure, but that doesn’t really address the issue.

Right?! We get it. “GOL” Okay. I don’t even like Squash, okay?

+1 to wanting this feature. Far be it from me to kinkshame anyone, but some of y’all are into some weird stuff. It hasn’t been too terrible to block community by community, but I gotta say - those of you who are into Fur are PROLIFIC with the genres and sub-genres of various yiff related activities. And actively participating! 😂

With the improvements Ruud and team put into Lemmy.World, my experience has gotten infinitely better. Lemmy is completely satisfying my Reddit addiction, and Memmy is an incredible app to navigate it all.

Overall, I’m really happy I made the switch. Had a 12 year run on Reddit, but Lemmy proves that Spez is wrong about where the value lies. If the content is water, there are dozens of ways to move it to different places, and right now Reddit looks like a leaky bucket in comparison.

I think the barrier to entry also helps a bit. The folks willing to put up with the rough edges that Lemmy has are also likely willing to participate with the intent of making Lemmy a success rather than just “hangers on” as it were. With a 1600% growth in “active” user population, there are definitely a ton of lurkers, yet. Once it becomes more approachable, we’ll see if the community feeling that Lemmy has begins to tarnish and fade as the volume of interaction and content rises.

The most important part of the federation process is played by whichever instance hosts the original post. They’re the hub and all other instances are the spokes.

So once Instance A defederates from Instance C, nothing Instance C users add to posts hosted by Instance A will be added to the master manifest. Basically, everyone is updating Instance A’s copy of the post, and that copy is then being redistributed to all other federated Instances.

Once Instance A defederates from Instance C, the only time their users will interact from that point forward is on a mutually federated instance. Both communities can comment and interact on a post hosted by Instance B.

Basically it works like this:

Instances A, B, and C are federated initially. When a user posts on Instance A, users on Instances B & C can see and interact with the post directly. Any comments they make will be sent back to Instance A as the “home” instance for that content.

Now let’s say Instance A decides they don’t care for the type of interaction they’re getting from Instance C’s users and decides to block - or defederate - Instance C.

To users on instance A, nothing changes other than new posts and comments from users on Instance C will no longer show up. To users on Instance B, nothing changes other than new comments from users on Instance C won’t appear in posts they interact with on Instance A. However, for Instance C, things are suddenly branched.

On Instance C, any posts that were created prior to defederation still exist in Instance C’s record. However, any comments that users on Instance C commit to those posts will no longer be distributed to users on Instances A or B, because Instance A maintains the “primary” record of the post. Similarly, Instance C’s users will not receive updated comments from users on Instance A OR Instance B, because again, Instance A is what determines which comments appear in federated instances. Furthermore, new posts created on Instance A will no longer show up in users’ feeds on Instance C. From the moment of defederation, Instance C’s copies of all posts on Instance A are now distinct, and the only new comments or updates they will receive will be from local users on Instance C.