Fediverse stuff

I think the two of you were definitely not on the same wavelength - in particular you understand the benefit of the fediverse, which seems to escape the other commenter.

It's worth explicitly spelling it out though, so I will do so here - static old time websites like old school forums can't communicate with each other. In fact things like Facebook and Twitter are single websites, just gigantic ones.

Now the other commenter is saying that with old time websites that we ourselves own, we control 100% of the data, and that's true. That's not new to the fediverse.

But, here's the problem. If I start a forum about hammers, and you join, then I control your data since it's my forum. Or, if you start the forum instead and I join, then you control my data.

For us to both be in control, we have to start separate forums. But then the two forums are islands without bridges, so we can't communicate with each other. Taken to the extreme case, we end up with a website per user and no engagement (it's just individuals talking to themselves in isolation).

What the fediverse changes is this - the two forums can communicate and share data. So we both start an instance (new school forum) and federate.

There's an additional benefit. Users who don't want to run their own websites, or instances, still benefit over having greater control of their data. Real life example - kbin.social went down some months ago, but I was able to pull back a large amount of my content anyways since fedia.io had a copy.

In summary, old time websites (non-federated edition) are still centralized. The website owner controls the data. With federation, individual users are better empowered to control their data without having to be website/instance owners.