From the perspective of looking at the internet of today, the future is 1996.

Change my mind.

Doesn’t seem to be working on latest Firefox ESR (or, according to the error message, on the web server backend they use)?:

Error
The following features required to run Godot projects on the Web are missing:
Cross Origin Isolation - Check web server configuration (send correct headers)
SharedArrayBuffer - Check web server configuration (send correct headers)

If we’re allowed to - and happily do - copy over content from for-profit websites with bots, it feels a bit weird to then get angry about that happening in reverse, no?

Not at all. It’s a matter of asynchronous power play.

We can do the former as a fight against power, but we have to fight for it. When they do it to us, it’s “just business” and we have no defense.

Literally obligatory reference

If your server hosts communities that follow others, that would still be the same as having users on your server follow those servers. It’s the same amount of communication.

Oh that’s a very good point! I had the wrong impression there was extra data sharing needed in this case but yeah, looking back it makes sense that the amount of data transfer is about the same considering the focus is on the verb (actor A sends to / pulls from actor B) rather on who is doing the action.

That’s good to see, but still doesn’t cover the case of what happens if those communities are in different instances. That’s the really big issue with merging (naturally or not).

Is there some kind of “so, you’re on a small instance,

Captain America advisors on the subject of the Fediverse? Now that would be on-point.

1 is absolutely the most important,

1 is literally the worst of the three, opening the Fediverse to a death at the hands of corporate. And I’ve already explained its other issues.

WHat if they’re defederated from a but not from b?

For a lack of better terms a Group […] would allow each indexed community to retain its independence

Affiliations? We’ve had those since the 90s, every fandom forum had its dedicated section for affiliates.

The people thinking solutions for these fediverse problems really need to sit back and look at the internet of the 80s and 90s. Webrings, affiliations, gopher, fanlistings, FTP, much of the problems we “seem” to have were already solved long ago.

And then the users who were in the moved-from server but are defederated from the moved-to server get automatically banne d/ blocked from it.

Thanks but no thanks. Sharing is the solution, not merging. Merging is the solution that corporate sells for every problem.

, but what is happening is option 1, aka merging of communities, naturally.

[citation needed]

I don’t see any community that has been mechanically, forcibly moved over to another instance. I can still post to !cats@a.net and !cats@b.xyz separately.

Bruh we just don’t do the addiction painkillers of corporate. Doesn’t mean at all that the pain is the point.

I’ve already went on on why merging communities is Bad for the Fediverse (and only really helps the big corpos that get into the Fediverse), so it’s good that the badness of that “solution” is acknowledged.

As for #2: multicommunities: I seem to recall Kbin already does that, so it should work. As for sub-issue 1, "To create a multi-community, you would have to know where each community is and add it to your list. ", well that’s what webrings are for! Let’s bring them back from the '90s. Basically get’s give the power of “static search” back to the users.

Numero 3 Electric Boogaloo: Making communities follow communities, is not much of a bad idea, but I’m wary fo the issues already mentioned in it. I’m mostly concerned also about it making it harder to maintain smaller Lemmy instances due to the extra communication overhead.

I would not want the future of my instance to be dependent of such a level of uncertainty, now or in the future.

You can always go to a big provider like Facebook. They’ll surely won’t have issues with your documented whining on Kbin.

Lemmy-wise admittedly none comes to mind at the moment. In fact this is the first time I hear of meneame, which is good to know so thanks!

Mastodon-wise there’s Chilemasto, Masto.es and Lile, admittedly haven’t paid attention to instance names to find others.

Honestly if the feds are going to even take the effort to move personnel to your house and knock your door, when it’s quite unlikely the server is hosted physically at your house in the first place, you could take the opportunity to offer them cheap consulting on technology, international cultures (anime and stuff) and federation.

Heck, you can aim at their ego. “I tricked you, right guys? That means I’m pretty good.”

It’s not as much about seeing, it’s about using, and profiting from.

This post under CC-BY-NC-SA.

Dunno where have you been the last year, or the last 55, but those who “never experience God’s grace” still experience all the graces of capitalism and techno-feudalism, which is what currently matters.

There’s nothing unique to the current Fediverse situation. In the days of old people had their own web pages and web servers too, and we had protocols to announce changes to people too (hello? RSS? X-Headers?), we linked to each other as well (directories, webrings) and we had chat (IRC). Yet we still landed on CorpoNet.

In fact I’d surmise the current situation is worse. Whereas with the old ad tried protocols you could actually host a web server with content on a potato, or on an old beeper, nu-protocols tend to be quite resource hungry. I oft hear that people have to pay two bills for Mastodon: one for the web service and another one for the amont of storage and traffic that it generates; from what I hear Matrix is similarly heavy compared to, say, IRC or XMPP. Dunno if it’s still true or not but I also recall that stuff like Lemmy depends on DNS, meaning you have to be able to buy your own domain and depend on that kind of central authority (wasn’t the point of Fediverse stuff to be decentralized?). Rather recently a good amount of Lemmy servers were oopsied because one of the .tld authorities pulled the rug from under an entire top-level domain name.