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
3786 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
I've personally played with Gemini a few months ago, and now want a new Internet as opposed to a new Web.
Replace IP protocols with something better. With some kind of relative addressing, and delay-tolerant synchronization being preferred to real-time connections between two computers. So that there were no permanent global addresses at all, and no centralized DNS.
With the main "Web" over that being just replicated posts with tags hyperlinked by IDs, with IDs determined by content. Structured, like semantic web, so that a program could easily use such a post as directory of other posts or a source of text or retrieve binary content.
With user identities being a kind of post content, and post authorship being too a kind of post content or maybe tag content, cryptographically signed.
Except that would require to resolve post dependencies and retrieve them too with some depth limit, not just the post one currently opens, because, if it'd be like with bittorrent, half the hyperlinks in found posts would soon become dead, and also user identities would possibly soon become dead, making authorship check impossible.
And posts (suppose even sites of that flatweb) being found by tags, maybe by author tag, maybe by some "channel" tag, maybe by "name" tag, one can imagine plenty of things.
The main thing is to replace "clients connecting to a service" with "persons operating on messages replicated on the network", with networked computers sharing data like echo or ripples on the water. In what would be the general application layer for such a system.
OK, this is very complex to do and probably stupid.
It's also not exactly the same level as IP protocols, so this can work over the Internet, just like the Internet worked just fine, for some people, over packet radio and UUCP or FTN email gates and copper landlines. Just for the Internet to be the main layer in terms of which we find services, on the IP protocols, TCP, UDP, ICMP, all that, and various ones and DNS on application layer, - that I consider wrong, it's too hierarchical. So it's not a "replacement".
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_BLUETOOTH
sockets 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.