3 ms·

> the Web that exists today rests on the assumption that users exist on someone's server: essentially as guests on someone else's property We just need better

by seydor 3y ago

> the Web that exists today rests on the assumption that users exist on someone's server: essentially as guests on someone else's property We just need better connections. It s already at the point where this comment could be served by my home network without problem , even videos et al. Servers failed us, they got extremely centralized and censorious. Decentralized platforms have the same flaws. Self-serving from self-owned hardware is the original vision of the internet , and the final solution

r3trohack3r 3y ago
> We just need better connections. This isn't quite enough. The web is built on top of the internet right now, and the internet assumes that identities are mostly static. To find you, I dial your address, and that gets routed to your computer. The problem is, in the real world, addresses for humans change frequently unless you invest heavily in keeping them stable. On the trivial side, an ISP will rotate an IP address out from under you. On the less trivial side, you'll move from your laptop to your cellphone. The internet is missing an overlay network that can stably route messages to users in the face of unstable identifiers. Right now, I'm working on solving this with the libp2p overlay network paired with a scuttlebutt style gossip tree that supports multi-device concurrent writing to an append only database. You group together one or more databases under a "user" client side to model an account for a real world person. If you can find that database, you can find the user. We locate the database by looking for every node that announces the sha256 hash of root node on a DHT. This also pushes availability requirements down past the threshold of the persistent connection most devices enjoy these days. Any number of devices can mirror the database, so even if one device loses cell coverage another device is still mirroring it. The next step is solving delegation. Once you have multiple keys that can write to a shared data structure for a user, you can issue capabilities to third party services to modify that data structure. So you can do fun things like delegate managing/backing-up blog posts to a 3rd party hosted SaaS while still retaining full control of your data. We are walking around with super computers in our pockets with a near-HA 5G cell connection. The problem is, they aren't addressable in any meaningful way for the use cases users care about. If you want to host your website, you can't do it on your personal devices without figuring out a stable identifier for them on the internet. Edit: If this stuff interests you, we have a good list of research papers inspiring what we are building listed on our open interview challenge - https://gitlab.com/webai-open/network/interview-challenge https://gitlab.com/webai-open/network/interview-challenge
- mediumsmart 3y ago
  can this be implemented without the side effect of getting my devices shutdown by the shitstorm crowd or do I have to really agree with the majority from then on?
- h0p3 3y ago
  I wish you the best of luck, `/salute`.
deleted 3y ago
[deleted]
- deleted 3y ago
  [deleted]

by seydor 3y ago

r3trohack3r 3y ago

> We just need better connections. This isn't quite enough. The web is built on top of the internet right now, and the internet assumes that identities are mostly static. To find you, I dial your address, and that gets routed to your computer. The problem is, in the real world, addresses for humans change frequently unless you invest heavily in keeping them stable. On the trivial side, an ISP will rotate an IP address out from under you. On the less trivial side, you'll move from your laptop to your cellphone. The internet is missing an overlay network that can stably route messages to users in the face of unstable identifiers. Right now, I'm working on solving this with the libp2p overlay network paired with a scuttlebutt style gossip tree that supports multi-device concurrent writing to an append only database. You group together one or more databases under a "user" client side to model an account for a real world person. If you can find that database, you can find the user. We locate the database by looking for every node that announces the sha256 hash of root node on a DHT. This also pushes availability requirements down past the threshold of the persistent connection most devices enjoy these days. Any number of devices can mirror the database, so even if one device loses cell coverage another device is still mirroring it. The next step is solving delegation. Once you have multiple keys that can write to a shared data structure for a user, you can issue capabilities to third party services to modify that data structure. So you can do fun things like delegate managing/backing-up blog posts to a 3rd party hosted SaaS while still retaining full control of your data. We are walking around with super computers in our pockets with a near-HA 5G cell connection. The problem is, they aren't addressable in any meaningful way for the use cases users care about. If you want to host your website, you can't do it on your personal devices without figuring out a stable identifier for them on the internet. Edit: If this stuff interests you, we have a good list of research papers inspiring what we are building listed on our open interview challenge - https://gitlab.com/webai-open/network/interview-challenge https://gitlab.com/webai-open/network/interview-challenge

mediumsmart 3y ago
can this be implemented without the side effect of getting my devices shutdown by the shitstorm crowd or do I have to really agree with the majority from then on?
h0p3 3y ago
I wish you the best of luck, `/salute`.

deleted 3y ago

[deleted]

deleted 3y ago
[deleted]