Opposed to all those other laws FDP is blocking, this one the FDP vehemently wants and its the SDP who has been blocking it.

No, only users who have as bad of a reading comprehension as you would be misled

This is not about federation between instances. It’s about how community discovery within federated instances works. Currently it’s definitely sub-par.

420!

I don’t want Harry Potter fans coming here, good god.

To quote you: That’s your opinion

Yes, lagging basically means that they servers are working on federating content that should have been federated a while ago.

The official himself not, no. But in a lot of countries they would either have a government Office or the public broadcaster release a communication phrased for children in order to properly make them understand what the warning means

Now thats a cute cat

It’s a good thing that such a big instance doesnt Update to hot code immediately

If it doesnt work it’s a federation issue

Regarding 3: you can. On Mastodon, simply meantion the lemmy Community in your Post and it will be posted to that community

Kbin has separate problems because it is a different software. Cant speak about that as I dont know what their problems exactly are.

As for Lemmy, if posts show up after days it’s probably because 0.19 is more resource-hungry than 0.18 which causes some servers/instances to lag behind in outgoing federation.

Mastodon is like the boring solid mainstay that will always be there and keep the fediverse alive. There are tons of other fedi projects that are more exciting, but they burst into flames way too often for my taste lol

True

Nothing. Currently it would not be visible at all. In the backend however federating means that the Threads servers might - at some point in the future - fetch data from lemmy.world (and not display it either, only let it sit on the server).

They can try to push ActivityPub development within the W3C without actually using it btw.

That’s actually an argument for defederating atm. Because Lemmy can’t pull Threads content, but Threads can without making that fact public.

That’s not dependent on federating at all. Meta is a member of W3C, they can be a part of developing and evolving ActivityPub at any point without actively running a service with it.

Once you implement ActivityPub, you federate with everything that uses ActivityPub. Your server might simply not see every other server yet, but you’re on the same network. With the current implementation, Lemmy will never display a Threads post and Threads will never display a Lemmy thread/comment. But they might send data to each other.

It all depends on how the Meta teams implements ActivityPub and which parts of it.