Add a warning that Jami is partially centralized #1727
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1727
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Although it is described as a P2P client, Jami uses 5 different central servers to provide some functionalities, as described here and here. Hence, without self-hosting, these servers are points of failure where meta-data can leak (see also #1357).
This by the way goes counter to the cited advantage of P2P clients: "There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models."
I suggest a warning is added about the possibility to disable/self-host these servers.
I think small note is would be a proper solution to this. this issue is one of the grey areas which are always difficult to define. Do you wnna make a quick PR for this @lrq3000 ?
@blacklight447-ptio yes I'll do it :-)