These are the main ones for me:

─Session can mirror one identity across devices; Keet ties a room to a single device keypair.

─Session’s open groups or community servers provide moderation and persistence; Keet rooms vanish when all peers leave.

─Session’s design hides IPs behind onion-routed relays; Keet peers still expose IPs directly.

In short, Keet has the true p2p spirit, but Session has the usable infrastructure.

And I seek a balance between extreme privacy that is not useful, with acceptable functional privacy.

Reply to this note

Please Login to reply.

Discussion

-Keet can link one id across unlimited devices

-Keet rooms have moderation and persistence unlike any other platform. All peers leaving a room is a nonsensical argument. You can remove keet from all active devices in a room and still recover the room if a copy exists

-Keet relays most messages by default hiding ips, onion routing can be added to keet in future and you are free to use a VPN or onion routing on your network connection etc

Keets infrastructure grows with every device, it has no scaling limits or cost. The developer of Keet is extremely focused on privacy