You are _technically_ correct, but I think you are minimizing network effects by simply calling it "easier".
These days you are pretty much required to use those same 10 sites if you want to interact with anyone, do business, or find useful information.
Those 10 sites have effectively captured the Internet.
The gp is saying the millions choosing the "easier" action is what causes the network effects.
E.g. another example that applies to tech-savvy programmers: most developers have the knowledge (or can Google a tutorial) to host their own personal git server but most choose not to. The collective millions choosing not to bother with self-hosting leads to emergence of something like Github.
Signing up for a free account on Github is easier than:
- hosting a personal repo at home on a laptop or Raspberry Pi
- buying a $10/month shared VPS server to host it
So even before Github had network effects (say less than 1000 user accounts), it was still easier to create an account on an unproven Github platform than self-host. Those early adopters leads to future strong network effects.
But that also leads to unwanted side effect of Github deleting repositories from DMCA takedowns, etc (aka "censorship").
90s: ask your ISP for a public IP, register your domain, start Apache and off you go
Nowadays: getting a public IP is iffy. All good domain names are taken. Emails from your self-hosted mail server go straight to spam/junk. Fiddling with TLS certificates is close to mandatory. The moment you start your server, you're bombarded by a flood of gratuitous requests, trying out every known vulnerability under the sun. etc. etc.
I can grab a cheap vps within minutes from DigitalOcean or OVH, with a public IP included. Both offer images with pre-configured software, and there are ample guides for setting up just about anything. Certbot/Let's Encrypt will literally setup add the generated TLS cert to your nginx config if you ask it to.