Keet has usernames. I don't see the difference between giving someone a phone number or a username as both are convenient
Stop using phone numbers with a messenger and use keet
Atproto has more in common with Keet than nostr, but neither atproto nor nostr solve the social media bigtech dilemma as the basis of that is using servers and only keet has solved not using servers
It won't disappoint. It's basically just about ready to replace Signal , WhatsApp etc and more, they have livestreaming in public testing now too and heaps of features coming
Keet 3 years ago didn't support mobile and had a group chat limit of about 50 people. It now supports mobile and has no group limits with one group already with 13000 people, it has a heap of new features including things like livestreaming
Keets way more advanced than nostr
Forget signal
Forget AWS
Use keet.io
Or use another decentralized solution... One that needs no centralization on top
Something better than lightning is coming. Something like what was built with Keet can't not have implications for transacting value
Nostr never solved the actual problem which is servers, Holepunch with Keet did
Bluesky's protocol is more in line with what Keet is doing. Tbh you will either have to reverse engineer what keet is doing or wait till it's more public to know more exactly but I doubt the social bit is anything exciting, it's the P2P bits they have already opened which would be
Very few use it currently but its UX is nearly good enough to replace WhatsApp and in some ways already better. The fundamental difference Keet has from Signal, Simplex, Nostr etc is Keet can already scale with no cost to bigger than WhatsApp
Holepunch has been quietly working on a tech stack that's going to completely change the tech sector
P2P is better suited for everything. Every peer in a P2P platform can be a relay. When you relay a message your IP is not directly associated. Even then things like onion routing in a P2P platform are totally possible with the added benefit of more nodes. Infact the lack of fixed static nodes makes network attacks ie logging ips at the routers or servers much harder
No offense but have you considered the viability of keychat? Playforms like signal, matrix and more hit scaling and funding issues, even telegram would have this problem. What technology stack can scale to whatsapps 3billion users tomorrow with no costs or service interruptions? What tech stack is unaffected if AWS or any data center goes down?
You should know the answer P2P
I love nostr but it hasn't solved servers so I see something like keet as much more hopeful
I just tried bitchat again and this time obviously after many updates it works. It's disturbing it requires location access tho, so I removed it
The basic issue with servers is someone needs to run them and in lieu of some giant corp paying people to do that it just never happens at scale even then funding it is difficult and compromises ux. P2P circumvents that problem by integrating the server software into ever app and making it run automatically
Something like nostr could certainly run P2P which is basically what keet is doing but unlike nostr the social protocol in keet is still hidden but all the P2P stuff isn't
You can verify it you put the effort. From the ethos of the people building it tho I would trust it especially way more than telegram or whatsapp
How did you find them? I love Keet but bitchat didn't work for me when I tried it and Keychat still uses server so won't succeed
They are my speculations, tbh P2P solves so many problems it's worth trying. They never fully open source anything yet, they plan to next year
The early versions of keet on desktop had all the source available in the install location which they later obfuscated but is still available
The app and tech is extremely promising and looks near 100% will replace all current tech. You need to realise any problem centralised tech and data centres etc solve P2P can solve and actually solve better but it just needs different thinking
Because some of keet remains closed its not fully certain what the issues are, which is probably the biggest issue, but from having used it here is some ideas and speculationsI have
Direct IP connections exposing your IP. These do not happen all the time tho
Main id, username and screen name exposed to every room
Seems like no forward secrecy on the P2P distributed room data
Seems the room data can be freely distributed to anyone that knows it exists but there is obviously an issue identifying it given peers also encrypt connections to each other
Notifications on mobile in some part (said to be encrypted obviously) go via Google and apples servers
Each room message is identifiable to each device
Screenshot message data might be matchable to room hash data
Might be possible to forge results with their username system then maybe mitm is possible etc
Keet.io already way out performs matrix and with no censorship
Try Keet, while it doesn't have local meshing currently it is quite capable and plans to have it
I believe they have published enough source that it's quite possible to make an app that could interact with keet, I have seen others do such things since a long time ago
Your "contacts" in keet are the rooms you are a member to, so what ever keys that allow that plus your own local hypercores. The function to make a copy of these "contacts" is to link another device which will then replicate them all on that device which is technically just another instance of keet whether it's on another device is not actually important. And the action of linking the "device" is actually a new identity joining each room with one overall identity linking each of your devices/identities in the room. Interesting point your identity per room is unique opening the possibility to have a different screen name etc per room but this has yet to be implemented, it's just the foundation has been built for it
If you wanted to get into somantics it would be possible with keet to store the info necessary to join any room in text and then store that in keet or any app
As to rugability, it's built on a completely open source and P2P foundation meaning there is no servers to maintain ie it can't be shutdown, yes parts of the app are not currently open but there is certainly enough open to build chat apps and you should be able to make them keet compatible, if you have the keet install files which are publically available you can keep installing and using keet even if holepunch the parent company went bankrupt and stopped, which you can not say for things like signal, WhatsApp or telegram and most other apps