1116
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Aug 2025
1116 points (100.0% liked)
Technology
74247 readers
3820 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
IP is the most robust and best protocol humanity ever invented. No other protocol survived the test of time this well. How would you even go about replacing it with decentralization? Something needs to route the PC to the server
I don't want client-server model. I want sharing model. Like with Briar.
The only kind of "servers" might be relays, like in NOSTR, or machines running 24/7 like Briar mailbox.
IP. How would I go about replacing it? I don't know, I think Yggdrasil authors have written something about their routing model, but 1) it's represented as ipv6, so IP, 2) it's far over my head, 3) read the previous, I don't really want to replace it as much as not to make it the main common layer.
Guess what
Briar itself, and every pure P2P decentralized network where all nodes are identical... are built on Internet Sockets which inherently require one party ("server") to start listening on a port, and another party ("client") to start the conversation.
Briar uses TCP/IP, but it uses Tor routing, which is IMO a smart thing to do
I'm talking about Briar used over BT.
Even
AF_BLUETOOTHsockets are.... sockets, where one machine ("server') opens to listen, and the other ("client") initiates the streamSockets are an operating system abstraction and have nothing to do with this conversation.