mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #4562] [FR] Request for Peer-to-Peer and End-to End Encrypted Sync Feature on Local Networks. #2048
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#2048
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @nikunjkumarnakum on GitHub (Jan 31, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4562
Description
I am proposing the inclusion of a robust Peer-to-Peer (P2P) synchronization feature enhanced with End-to-End Encryption for our application. This feature aims to empower users to seamlessly sync data between devices on the same local network while ensuring the highest level of security and privacy.
Impact
Collaborative Teams:
Small Businesses:
Privacy-Conscious Users:
Remote Areas or Limited Connectivity Environments:
Families and Home Networks:
Additional Context
Redundancy:
In a P2P environment, redundancy is improved, as data can be distributed across multiple devices. This enhances data resilience and availability, reducing the risk of data loss in case of device failures.
Offline Collaboration:
The feature emphasizes the ability to synchronize data even when devices are temporarily offline. This is particularly beneficial in scenarios where a stable internet connection cannot be guaranteed, ensuring uninterrupted collaboration and data access.
Cross-Platform Compatibility:
To maximize usability, the feature should aim for cross-platform compatibility, supporting various operating systems and devices commonly found in local network environments. This inclusivity ensures a broader reach and adoption across diverse user scenarios.
Enhanced Security and Confidentiality:
The integration of End-to-End Encryption ensures that all synchronized data is encrypted on the sender's device and can only be decrypted on the recipient's device. This level of security guarantees that even if the data is intercepted during transmission, it remains confidential and inaccessible to unauthorized entities.
Minimizing Server Dependency:
By focusing on local network synchronization, the feature aims to reduce dependency on external servers. This not only addresses privacy concerns but also mitigates potential issues related to server downtime or maintenance, providing a more robust and self-sufficient solution.
Mitigation of Third-Party Risks:
Reduced Dependence on External Servers: Minimizing reliance on external servers not only enhances privacy but also reduces the risks associated with third-party service providers. Users can have greater confidence in the security of their data, knowing that the synchronization process occurs directly between trusted devices on the local network.
Scalability in Large Local Networks:
Scalable Performance: The P2P architecture inherently scales with the number of connected devices. This scalability is crucial, particularly in large local networks where numerous devices may need to synchronize data simultaneously. The feature ensures optimal performance even in such environments.
@ieuze commented on GitHub (Apr 10, 2024):
What is the benefits of E2E if all traffic are aimed to "seamlessly sync data between devices on the same local network"? Are there untrusted devices on the chain in local? A general P2P implementation with basic encryption will suffice.
Meanwhile it is much easier and likely to implement if these processes are handled by a different project not limited to a specific pkm program, like syncthing.
@trymeouteh commented on GitHub (Jul 10, 2024):
I would like this feature and it would be great to see it done in two ways.
https://forum.appflowy.io/t/p2p-syncing-syncing-data-between-devices/931
@nikunjkumarnakum commented on GitHub (Sep 12, 2024):
@yuuz233 Thanks for your input! Here’s why E2E encryption and P2P sync are both important.
For E2E Encryption I would say.
Security: Even on a local network, E2E encryption ensures data is protected from unauthorized access and internal threats, maintaining privacy and user trust.
Future-Proofing: It safeguards against potential future security issues and prepares us for scenarios where devices might be compromised.
and about P2P sync
Efficiency: Enables real-time data sharing and collaboration directly between devices without relying on external servers.
Offline Use: Works even without internet access, which is ideal for remote or low-connectivity environments.
Cost-Effective: Reduces the need for server infrastructure, saving costs and simplifying setup.
Combining both: Integrating E2E with P2P sync offers robust security while leveraging the benefits of local synchronization.
Regarding Syncthing Using an external tool could limit our ability to tailor the sync process to our specific needs and might introduce additional dependencies or integration challenges. While Syncthing is effective, it may not seamlessly integrate with our app’s existing features and workflows
@nathfavour commented on GitHub (Oct 25, 2024):
good point
@tomByrer commented on GitHub (Dec 12, 2024):
Hi, what is the status on this?
@trymeouteh commented on GitHub (Jun 6, 2025):
https://forum.appflowy.io/t/p2p-syncing-syncing-data-between-devices/931
https://github.com/AppFlowy-IO/AppFlowy/issues/8036
Would like to see E2EE for sure and having P2P syncing would be nice to have.