Follow

For real though I'm so pumped about I can't shut up about it at work. I wanna set some time aside for running http services behind tunnels and to wire the front end to @agregore so I can make it easier for folks to self host services which they can access from anywhere

I seriously think this is the missing piece for those "computer in your house" startups. I worked a bit with one in the past and I really wish they figured out the how. Veilid with a web browser frontend seems great. I guess provided the speed keeps up? I hope it's faster than tor or i2p. The mobile first approach is my fave part I think.

Socket Supply is another great contender. I wish it didn't need to have each app loaded as seperate native apps instead of instantly. It makes sense why tho

@light @agregore Not actively. I'm looking for a grant to add a new protocol to it like veilid or pears. I use it daily for general web browsing though :)

@light @mauve @futo You might mean NLnet with handle @NGIZero. @nlnetlabs develops open source software, NLnet supports open source projects.

@light @futo@minds.com @nlnetlabs Sweet I'll give them a peek. I've been looking at OTF too. I'm thinking to pitch either as censorship resistance tech with decentralized publishing or double down on people being able to make new decentralkzed web apps on fully local networks. I think the p2pad demo app has a lot of potential. Ipns://agregore.mauve.moe/docs

@mauve Hmm. I'm getting an error for that URL

```
ipfs resolve -r /ipns/agregore.mauve.moe/docs/tutorials/p2pad-code-editor: no link named "p2pad-code-editor" under bafybeidsusdytja3angkcenoqwwm6db5i3bhcbed57pak2vmhipqln3nfq
```

@mauve what makes it so good compared to similar projects?

@makeworld a few things tbh.

1. Thinking about mobile first. A lot of protocols end up focusing on desktop to server or desktop to desktop and don't account for stuff like NAT or intermittant uptimes. There's also the fact that storage modules take mobile storage location needs out of the box. Socket supply's packet routing is a bit better for networking and I think the holepunch dht is better for handling churn.

@makeworld

2. Taking ip privacy more seriously while trying to keep speed and decentralization up. A lot of p2p protocols just give up rigjt away and mixnets lack p2p primitives or aren't as fast. For privacy perserving or censorship use cases this is crucial.

@makeworld

3. Key value stores are important for stuff like introducing peers or keeping small bits of shared state. It's less versatile thsn holochain or freenet but it's just enough to get the job done. Other dhts like mainline or hyperswarm don't have shared mutable state which can be annoying

@makeworld One thing it's kinda lacking is in blob storage and packet forwarding use cases but I think those can be brought in as stuff running over the kv store and tunnels. We're gonna be experimenting with using iroh over the wire for blobs and documents and using tunnels for connecting and kv for group discovery

Sign in to participate in the conversation
Mauvestodon

Escape ship from centralized social media run by Mauve.