OutNet VS hardlinep2p

I have been thinking about this for about 6 years. Here is some more info: https://github.com/rand3289/OutNet

There is no information about how it works only what it does... see my project for example of what I would like to know: https://github.com/rand3289/OutNet

I started working on decentralization a few years ago but saw zero interest and never got to the hard part of detecting attacks. I got a simple test system going that takes care of basic connectivity and peer discovery if you are interested: https://github.com/rand3289/OutNet

They definitely need to see my framework. :) https://github.com/rand3289/OutNet

Yes, avoiding DNS should be a main goal! I do that in my project: https://github.com/rand3289/OutNet

This is what I got to say about that: https://github.com/rand3289/OutNet

Hey, can I participate? I wrote OutNet for decentralizing services: https://github.com/rand3289/OutNet

Compare it to my OutNet where I clearly explain how things should work: https://github.com/rand3289/OutNet

My OutNet runs as a distributed service (backend) and applications connect to it to find peers. https://github.com/rand3289/OutNet

Who uses UDP these days? You can configure router port forwarding for TCP ports easy! Use UPnP protocol. I had to do it for my OutNet project: https://github.com/rand3289/OutNet

I really wish there was something like Tor hidden services, but without the hidden part, just the ability to access something in a performant p2p way with a crypto url. That would make self hosting a bit easier (Although I still wouldn't even think about doing my own email server!).

I had a proof of concept working( https://github.com/EternityForest/hardlinep2p/blob/main/hard...) but it used kivy for the mobile app and I decided I wanted fewer one-person-projects in my life.

I started an attempt(https://github.com/EternityForest/hardlinep2p), but I wasn't using BEP, instead I had a custom protocol that's like

Yes, it is 100% time fot that.

Mozilla FlyWeb was close, but didn't handle remote access. It could have been extended to, but they dropped it.

I wrote a proposal here for how this could be done with Bluetooth-like pairing, using URLs that embed a certificate hash, a random sequence as an extra security layer, and a lookup URL that one can ask where to find the host for a service, for access over the WAN.

By using a URL instead of normal non-HTTP DNS, the lookup URL can be another web service self hosted using the same TLD, or a Data URI if one is hosting from a static IP.

No part of the URL besides the key is used to determine the origin for CORS and local storage, so you can change discovery methods and the random string freely.

Initial connection is by directly sending a link, or by LAN discovery.

Unless discovery is enabled and you are on the same network, it should be impossible to connect without already knowing the URL, so even if your home automation hub is very badly coded, they can't even start hacking it till they find your URL, which can't be found just by sniffing(Because of that random string).

Clients track the "last seen" address of servers, so even if lookup goes down, access still works until your home IP changes.

When nodes connect over LAN, the server sends it's "Find me on the WAN at" IP. So even with no discovery server at all and no static IP, it creates a very convincing illusion of "just working" 99% of the time.

Which means that if you buy a device that uses a cloud lookup service, and they drop that service, your device will still be remote accessible, most of the time. Which might be good enough, or at least good enough to get by until you can find a more permanent solution.

Proposal:

https://github.com/WICG/proposals/issues/43

And a partial implementation of a very close version(Lookups always use OpenDHT in this), plus a notetaking app based on it.

https://github.com/EternityForest/hardlinep2p

I really think this is one of those critical missing technologies that would really enable a lot of amazing things.

Github is here, still has some Python version compatibility work to do: https://github.com/EternityForest/hardlinep2p