4 ms·

By different network, I meant different protocols basically that will serve the puropse of the network. I don't mean connecting some nodes together using the cu

by nwhnwh 2y ago

By different network, I meant different protocols basically that will serve the puropse of the network. I don't mean connecting some nodes together using the current internet. So imagine a new service provider, you go and subscribe, and login to the network, you can't receive anything other than text. And the domains are all available at the begining, so no google no microsoft, etc. Except if you allow internetwork domains.

solardev 2y ago
You can start a service like that and put it on the existing internet if you want. You can bypass DNS and make your own routing if you want. Onion and Freenet and blockchains and DHTs and content addressable systems work similarly. But nobody uses them because they're such a hassle. Again, what you're describing is more an application or protocol, not a network necessarily. You can build it all in software on top of the existing internet.
- nwhnwh 2y ago
  Can you recommend a book that could explain these topics especially the protocols in a good way? I hated network classes in college.
  - solardev 2y ago
    Sorry, networking isn't my specialization, and I never read a book on those topics. (I know vaguely what they are and a little about how they work, but not enough to reimplement any of them on my own.) But many of those projects are open-source, so you can see the discussions (and code) about how they were built. IMHO: I think maybe you're overthinking this a bit though...? If your end goal is just to have a place where people discuss primarily (or exclusively) over text, then all you really need is a web app that enforces that, like HN does. You can probably find some HN clone or reddit clone software and just use that, or Discourse (the forum, not Discord the chat app), and remove any multimedia functionality they might have. Or host your own IRC or Usenet server and don't allow images. I don't think this is really a technical issue to solve, but a cultural one. Such places aren't common/popular because "I never want to see an image" isn't a big priority to most people. It'll be hard to get traction on such a forum, no matter how you build it under the hood.

by nwhnwh 2y ago

solardev 2y ago

You can start a service like that and put it on the existing internet if you want. You can bypass DNS and make your own routing if you want. Onion and Freenet and blockchains and DHTs and content addressable systems work similarly. But nobody uses them because they're such a hassle. Again, what you're describing is more an application or protocol, not a network necessarily. You can build it all in software on top of the existing internet.

nwhnwh 2y ago
Can you recommend a book that could explain these topics especially the protocols in a good way? I hated network classes in college.
- solardev 2y ago
  Sorry, networking isn't my specialization, and I never read a book on those topics. (I know vaguely what they are and a little about how they work, but not enough to reimplement any of them on my own.) But many of those projects are open-source, so you can see the discussions (and code) about how they were built. IMHO: I think maybe you're overthinking this a bit though...? If your end goal is just to have a place where people discuss primarily (or exclusively) over text, then all you really need is a web app that enforces that, like HN does. You can probably find some HN clone or reddit clone software and just use that, or Discourse (the forum, not Discord the chat app), and remove any multimedia functionality they might have. Or host your own IRC or Usenet server and don't allow images. I don't think this is really a technical issue to solve, but a cultural one. Such places aren't common/popular because "I never want to see an image" isn't a big priority to most people. It'll be hard to get traction on such a forum, no matter how you build it under the hood.