

| UID | fascho_land | schaerfe_der_einreisebestimmungen |
|---|---|---|
| 1 | USA | Over 9000 |
| 144 | Nordkorea | Frag Otto Warmbier |
| 67 | VR China | Nürnberger Christkindlmarkt, verglichen mit 1 und 144 |


| UID | fascho_land | schaerfe_der_einreisebestimmungen |
|---|---|---|
| 1 | USA | Over 9000 |
| 144 | Nordkorea | Frag Otto Warmbier |
| 67 | VR China | Nürnberger Christkindlmarkt, verglichen mit 1 und 144 |


Well, there’s no license because there is no code on their Github. They claim their P2P framework is open source. Yet, that is just the part that allows clients to connect. But I also need to check that what is transferred through that connection is truly encrypted. And if there’s no code, there’s no basis to even develop trust.


This is the second time I stumble across Keet this week. It sounds interesting, and yet it appears not to be open source. All I could find is a Github page where they publish their APKs, but no source whatsoever. Is it really closed source? Because I don’t to “trust me, bruh” crypto.


This is the correct approach, OP. Bazzite is good, but its immutability is an aspect one needs to get used to and learn to work with. Since you’re not (and I’m not saying I am ;), rather stick to something you feel comfortable supporting, because you’ll be the one they’ll come running to if they have a problem.