heapwolf / is on Nostr

Founder & engineer at Socket Supply Co. — Turning #RFC.s and #P2P papers into code people can use — Turn on, tune in, sign out. #indieweb #dweb #foss

Last Notes

2023-08-28 08:28:39

- reply

@npub179l…lf56 @npub1grd…52zz sounds like you’re an anon account for someone who works there “sum guy”

2023-08-28 08:23:45

- reply

@npub179l…lf56 @npub1grd…52zz “grown massively”, “I’d be surprised it it wasn’t open sourced soon”, it seems completely broken still

2023-08-28 07:47:54

- reply

@npub1grd…52zz @npub179l…lf56 it’s impossible to know if it’s really secure because there is no spec and only some of the code is open sourced. From what I understand they privately modified the open source that they use heavily. Cryptographic systems that can’t be scrutinized and openly peer reviewed are not secure systems, they are marketing.

2023-08-13 09:44:01

- reply

@npub14d7…dm4s happy to make you a contributor if you want, and help you learn how it works — we also have a discord-like app that is P2P, we are adding preple to the GitHub for it every week as the UI becomes more stable, it’s a bit more appropriate for discussing this kind of thing if you’re interested.

2023-08-13 09:33:23

- reply

@npub14d7…dm4s this is the problem we solved, it took many years and many people to get it working correctly. Our docs explain how it works, and they might help you avoid a lot of dead end rabbit holes.

2023-08-13 09:22:28

- reply

@npub14d7…dm4s the thing you’ll find after that is, NAT traversal is only a small part of a *much* larger problem. Let’s imagine you successfully sort out all NAT traversal rules and codify them, get it all tested; you can connect some devices, not all of them, because that’s not how it works… what next? The next move I’ve seen everyone else do is to say, fuck it, spin up a relay server. Now you have an asymmetrical network design, and that introduces a non-trivial vulnerabilities.

2023-08-13 09:16:35

- reply

@npub14d7…dm4s you need to create a simulator that models the network — there are a finite number of well-known NAT types and behaviors. Doing it physically is a huge pain. Model it first with software. after you spend a year or two fucking around with this, you can try to get it deployed to an environment where it’s useful ;)

2023-08-12 12:06:08

- reply

@npub14d7…dm4s I’m curious why Veilid instead of socket?

2023-08-06 02:01:56

“Never build your house on someone else's land.” — Someone wise who obviously wasn’t talking about software.

2023-08-05 12:56:47

#AWS: Free if you have no customers.
#P2P: Free forever.

2023-08-02 12:02:02

- reply

@npub14d7…dm4s hit me up if you need any help :)

2023-08-02 11:33:46

- reply

@npub14d7…dm4s sounds like Socket Runtime :)