Have any #p2p people used #Keet ? Built on on #Hypercore. Looking for a good hole punching implementation and i was told this was a good one. I just tried it out between my laptop (behind university firewall/NAT) and cell phone (on mobile network), and I had one issue connecting, but after an update was able to connect in both directions no problem. No login, no account, no phone number, and allegedly e2e without needing a public server to coordinate the holepunch. need to check out how that's implemented. if this checks out i'm like damn this might be better than Signal (which i love)
edit: link to app page https://keet.io/ and (minimal) docs https://docs.holepunch.to/apps/keet.io
@jonny Yeah it's pretty cool. Sucks they haven't opened their source though.
@jonny FWIW the networking part has been open for ages. I personally don't even care about the client itself being opened. The thing that's frustrating is that they haven't published any open source stuff for how to get their stack working on mobile.
At least one project ran out of funding trying to figure it out on their own so it's one of those things where it's very obviously hurting the ecosystem and adoption of the core tech. 🤷
@jonny Yeah... check out socketsupply if you haven't yet. Also the Berty chat folks have some mesh adjacent networking working on mobile which is neat.
@mauve yes yes on my reading list. maybe i should work through that before i get excited about any project in particular lol
@alm
@mauve
sure! extremely WIP (stuff may be wrong, most of it is incomplete, all of it is disorganized) but reading list to make comparison is here: https://piracy.solutions/docs/comparison/
and reading list that's just part of my general notes is here: https://wiki.jon-e.net/P2P_Linked_Data/Reading_List
my goal at this point isn't necessarily to make an index of p2p projects, but it might turn out that way. but to get a basic understanding of a bunch that seem related to elements of what I want to do to learn from them and be able to articulate how to understand the thing in relation to something they might already know. eventually the goal for the docs is to make a sort of class structure so you can see "for this given problem in p2p space, here are the different ways that different projects approach it"
@mauve
right, that's the part I was interested in, how to holepunch on mobile. if that part isn't open/isn't replicable then it's pretty useless to me as far as implementation inspo.