> On a technical level, prioritizing big-world indexing over small world networking has multiple benefits.
It does ... if every node interacts with every other node on behalf of every one of its users. But if a PDS at pds.example.net mostly interacts with the fifty or so instances where its users have contacts while rarely to never interacting with 10,000 other instances, it doesn't need the BGS firehose, and it can integrate "app views" for its users directly into the same server.
Wow! I had forgotten about #Elgg. OpenUniverse and I had accounts on an Elgg instance in South America (time-wise, it was right after Mike's initial #Friendica instance closed, so we shifted existing conversations over) and got to see some of the posts about their #federation plans.
Note: this may have even been before changing the name from #Friendika to Friendica.
To what @lxo posted, because vertical scaling ("bigger servers") has its limits, the big #corpocentric #socnets split things up and use technological workarounds to appear to be one big server.
For example, one of the first things is to move the #database management system ( #dbms ) to a separate machine. Once this happens, hoizontally scaling the database by clustering (multiple servers handling the same db) is possible.
Next, we can perform similar clustering with the web server, and we can perform similar clustering at the processing layers.
Once we do this, we can expose things through various interfaces. This is what #cloud providers do with their separate compute, database, and storage services. Each such service relies on hundreds of servers pretending to be one.
Finally, we come to #federation, where we skip the pretense that everything is one big server and instead have many separate individuals and organizations running servers.
It isn't inherently more complicated, but it does mean users have to know that we're not all on big-centralized-server.com.
@lnxw48a1 @fu If I may pitch in on on th etopic of "how the fediverse works"...
Yes, you can explain it with the image of email and email providers. But you rely on "freedom" (whose?) to describe a structure that doesn't explain why newbies can and cannot subscribe to other people or otherwise interact with accounts and posts.
A different way is stop putting "freedom" into the centre β which in itself is a rather problematic hierarchical approach as it invokes the imagery of landlords dealing with their rowdy tenants β and explain to people the basics of #federation, from which most of the peculiarities and problems of fediverse interactions arise.
2015 I wrote a piece for Twitter migrants to GNUsocial primarily from the angle of a layperson, explaining the various oddities by pointing to and explaining from federation as the root cause. Perhaps this snippet is of some help:
At #disruptedtimes22, Jon Crowcroft praises #federation and talks about @matrixdotorg@twitter.com - where you can run your own services or choose whom you trust.
Wow I did not know how many (German) universities are already using @matrixdotorg@twitter.com for their probably hundreds of thousands of students and staff.
Back in late 2016 I'm glad the #Fediverse (comprising OStatus/ActivityPub-compatible social networks) and the #Federation (comprising Diaspora-compatible social networks) welcomed me when my #Facebook account was frozen and I was (and still am) too stubborn to give in to their demand to give me back access to it.
I've been contributing to #Friendica ever since, mostly through dogfooding through my own single-user node.
Happy Birthday to us and thank you to everyone who has contributed or still is contributing to this mind-boggling common project.