He’s just saying that Keet isn’t open source yet, which that particular app isn’t. But everything it’s built on is.👇🏻

nostr:nevent1qqsqyhqgtu3p8jsp0dsdkexwd7l77592d87krgwekk3zcqy3zmmcwlqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgswaehxw309ahx7um5wgh8w6twv5qs6amnwvaz7tmwdaejumr0dsq3samnwvaz7tmjv4kxz7fwd4hk6mmnw3ezuurfde4sz255q0

Their collection of foss (pear i think they call it) is cool. Keet the app is the issue

lol, they are planning on having a protocol spec soon, they have been making too many breaking changes so far though. Apparently they spent a ton of time making one a couple years ago and then made a huge change which threw more than half a years of work in the trash. So they said they weren’t doing that again until they felt it was completely solid 😆

Nothing in the connection layer does this. It runs on Pear Runtime which is entirely open source. The connection is P2P and you can see everything in the code related to that. If something in the UI on top that is not yet open source has malicious connections in it , then sure that’s possible. There’s no APK yet (I do have one for some troubleshooting stuff I was helping with but it’s not publicly available yet and I’m not gonna audit it myself because ain’t nobody got time for dat 😆)

But as has been discussed, Keet is planned to be entirely open source after it’s out of beta. Just don’t use it if you are concerned with this for some reason or don’t trust them. But literally everything in Pears (and the networking runtime) is open sourced.