This wasn’t particularly common on the early web. There were a multitude of websites, but they were connected only by hyperlinks. There were few if any groups of websites that replicated each other’s content, as with the Fediverse.
It was, however, common with some non-web protocols. Most notably, Usenet and email have always been federated, though with very different goals than the Fediverse: not to resist centralized corporate control, but because connectivity to other servers wasn’t always online. Instead, you’d read and write your Usenet posts and emails on a nearby server, often at the university or business campus where you study or work, using your terminal or microcomputer. The server would then periodically call other servers with a dial-up modem, exchange all pending messages with a batch transfer protocol like UUCP, and then hang up until next time. Messages often had to be forwarded several times before finally reaching the intended recipient. This store-and-forward network was painfully slow by modern standards, but it was by definition federated. You could send and receive emails and Usenet posts even while your site was offline, and although others would not see your messages right away, they would see them eventually.
The Internet, by contrast, is ludicrously fast and always (well, almost always) online, so this sort of need no longer exists. Large websites still do use multiple servers scattered around the world in order to balance load, but unlike the UUCP system of old, it’s transparent to the end user. When you try to use such a website, a nearby server is automatically chosen for you by the network itself; this is called anycast routing.
Unfortunately, anycast routing has made it feasible for one company to control the entire network and use it toward nefarious ends, and now the old idea of federation has re-emerged as a solution to this new problem.
This wasn’t particularly common on the early web. There were a multitude of websites, but they were connected only by hyperlinks. There were few if any groups of websites that replicated each other’s content, as with the Fediverse.
It was, however, common with some non-web protocols. Most notably, Usenet and email have always been federated, though with very different goals than the Fediverse: not to resist centralized corporate control, but because connectivity to other servers wasn’t always online. Instead, you’d read and write your Usenet posts and emails on a nearby server, often at the university or business campus where you study or work, using your terminal or microcomputer. The server would then periodically call other servers with a dial-up modem, exchange all pending messages with a batch transfer protocol like UUCP, and then hang up until next time. Messages often had to be forwarded several times before finally reaching the intended recipient. This store-and-forward network was painfully slow by modern standards, but it was by definition federated. You could send and receive emails and Usenet posts even while your site was offline, and although others would not see your messages right away, they would see them eventually.
The Internet, by contrast, is ludicrously fast and always (well, almost always) online, so this sort of need no longer exists. Large websites still do use multiple servers scattered around the world in order to balance load, but unlike the UUCP system of old, it’s transparent to the end user. When you try to use such a website, a nearby server is automatically chosen for you by the network itself; this is called anycast routing.
Unfortunately, anycast routing has made it feasible for one company to control the entire network and use it toward nefarious ends, and now the old idea of federation has re-emerged as a solution to this new problem.
Wow this is fascinating, thank you. I had no idea that usenet was a thing. How long have you been around on the web?
Usenet is still a thing
Since the mid-1990s. By then, Usenet and email were mostly Internet-based already.