You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Conversations is a strong candidate for inclusion in the Awesome Privacy due to its emphasis on privacy, open-source nature, and support for modern encryption protocols. Here are some key reasons why I think it should be considered:
Developed and maintained by a community of open-source contributors, which further enhances trust and privacy
Promotes and uses Decentralized XMPP network
Allows users to have greater control over their privacy
Free from ads, tracking, and data harvesting
Not owned by a large company with vested commercial interests in mining user data or selling advertising
- name: Conversationsurl: https://conversations.im/icon: https://conversations.im/images/conversations_logo.pngdescription: >- Conversations is a Jabber/XMPP client for Android 5.0+ smartphones that has been optimized to provide a unique mobile experience.github: https://codeberg.org/inputmice/ConversationsandroidApp: https://play.google.com/store/apps/details?id=eu.siacs.conversationsopenSource: true
Category
Communication
Listing Name
Conversations
Listing URL
https://conversations.im/
Listing Icon
https://conversations.im/images/conversations_logo.png
Listing Description
Conversations is a Jabber/XMPP client for Android 5.0+ smartphones that has been optimized to provide a unique mobile experience.
GitHub repository
https://codeberg.org/inputmice/Conversations
ToS;DR ID
No response
Is Open Source?
Security Audited?
Accepts Anon Payment?
Justification and Further Info
Conversations is a strong candidate for inclusion in the Awesome Privacy due to its emphasis on privacy, open-source nature, and support for modern encryption protocols. Here are some key reasons why I think it should be considered:
YAML Content for Addition
This ticket was submitted via awesome-privacy.xyz/submit
Final Checklist
The text was updated successfully, but these errors were encountered: