this post was submitted on 14 Nov 2026
1177 points (99.2% liked)
Programmer Humor
34135 readers
1588 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think that's already a consequence, TCP/IP is very much a protocol suite that works well for client/server architectures, and HTTP (which eventually, somehow, became the de facto "everything" protocol) even more so. So when you mix these roles and you have machines that act as both client and server at the same time all the deficiencies come to light quite easily. A world with first-class support for mutual authentication and authorization, encryption, peering, roaming, etc at the lowest of network levels was possible, but that ship has sailed.
You can plug all that jazz on top of IP. No problemo, servers do it all the time.
That's absolutely not the problem, the problem is centralized servers only.