I stopped trusting keet when I saw there and FBI cooperation
Discussion
I'm glad I never used Keet. I was waiting until they open sourced it but then I read their privacy policy and decided I wouldent touch it with a 40ft pole.
What's wrong with the privacy policy?
Sorry I used the wrong phrase its their tos. tldr despite being built on open tech (hole punch) they will sue you if you reverse engineer it and try to figure out how it works. They say they dont collect data but with a "balck box" we dont know for sure and I could be misremembering but I thought they talked about open sourcing keet. So I wanted to wait to use it until then but after reading the tos I doubted that it was likely and decided to stay away from it.
But pear is open now & that is what uses holepunch & hypercore. Keet apk is coming with the next major release.
I really dont care about keet. Having an apk wont change that its not open source. If pear is actualy open source then cool. ๐
Pear is licensed under Apache V2
https://github.com/holepunchto/pear?tab=Apache-2.0-1-ov-file#readme
What FBI cooperation is there?
Well, i guess you can say whatever you want if they aren't open source. The burden of proof is on keet.
Pear runtime is now open, Keet apk is coming, supposedly with the next major update. It's pretty clear from the way it operates that it's truly p2p tho. If I'm not online things don't propagate. I have to leave an instance running at home to seed my rooms. And everything tends to work better when there are more peers. But blind forwarding is also on the way, so media should propagate more reliably when that hits.
I am jacks complete lack of surprise
So what would you do if your centralized service was targeted by the govt?
Personally, I'd start building ways to decentralize everything else so that targeting me would ultimately do them no good ๐คทโโ