{"package_name":"com.bwt.threadscooponionchatcom","name":"ThreatScoopOnionChat","summary":"A Forked Version focused on privacy from SESSION","category":"Internet","icon_url":null,"latest_version_code":3915,"latest_version_name":"1.20.9","apk_url":"/api/apk/com.bwt.threadscooponionchatcom","apk_size":138131828,"apk_sha256":"b98c0a97c3be88f02db40461d67b1f559ed4b57da1721b1fd4adf641cf8255b4","source_kind":"fdroid-repo","repo_slug":"fdroid-main","last_updated":1779371402,"release_timestamp":1741745144,"description":"# ThreadScoopOnionChat\n\nThis version is a fork from \" https://github.com/session-foundation/session-android \", enfocado en la privacidad.\n\n## How Did ThreadScoopOnionChat Come About?\n\nI have always been a fan of privacy and security in communications, and I am constantly researching potential security breaches in messaging applications.\nThreadScoopOnionChat emerged after the analysis of this blog \"https://soatok.blog/2025/01/14/dont-use-session-signal-fork/\", in which several aspects are described as to why using Session is not recommended, and I wondered how it is possible that a foundation focused on privacy—with the grants and support it receives—has not been able to improve this protocol.\nI still do not understand the answer, since my resources are much smaller than those of a foundation compared to that of a person who is simply a fan of privacy and security.\nIn this blog, certain problems were described:\n\n1> \"https://soatok.blog/2025/01/14/dont-use-session-signal-fork/#insufficient-entropy-ed25519\"\n2> \"https://soatok.blog/2025/01/14/dont-use-session-signal-fork/#in-band-negotiation\"\n3> \"https://soatok.blog/2025/01/14/dont-use-session-signal-fork/#public-keys-aes-gcm\"\n\n\nThis is a forked version privacy focussed from Session.\nGo Github to check all features implemented.\n","categories":["Internet","Messaging","Phone & SMS","Voice & Video Chat"]}