requilence
Premise: treat it as certain that the server will eventually be compromised, subpoenaed, or misconfigured. So the server must hold nothing that can be decrypted or linked to a specific user's content. Users hold their own encryption keys, the server stores ciphertext, and there is no UUID→identity mapping at the sync layer. Sync runs over any-sync, which is peer-to-peer-capable; intermediate nodes see ciphertext.
On your four problems:
1. O(x*y) joins - pushed to the client, because the server can't decrypt enough to do them.
2. Offline members - eventual-consistency sync and CRDT.
3. Client-side theft - if an attacker has the user's keys, they have the data. Intentional: no server-side gate to break means no server-side gate to exfiltrate at scale. We're considering optional 2FA at the infrastructure layer as an additional barrier to data retrieval.
4. Unwanted modifications - content is signed with user keys and validated on read.
Real cost is on the product side: no server-side AI over your notes, no server-side full-text search, slower cold-start, and harder to build product analytics (no access to user data). Granular ACLs are also harder — permissions are enforced by key possession, so revoking access often requires key rotation rather than a permission-flag change.
But the exact bug this post is about (a server endpoint that maps a public UUID to an email) is structurally impossible in this model, because there's no such mapping on our servers to misuse.
any-sync and our data format (any-block) are MIT, if you want to poke at how it works: https://github.com/anyproto
Anytype runs locally and exchanges data directly in a peer-to-peer way without exposing it to intermediaries even when users work across devices and with each other. Because of this, Anytype is free without storage and upload limits. We plan to open-source it with the public release.
This is our early demo and I’d like to get feedback on what we are building, so we can incorporate it into Anytype. Also, if you have any questions, I’d love to answer them.
2. In case the data is shared with someone(e.g. teammate or family) you always be able to restore it with the seed phrase. In case of private-only data, our plan is to encourage users to have multiple devices(mobile+desktop) to have a data backup
3. We plan to implemet per-device private key(like the keybase does) and use it to decrypt files' private keys. In case the device's private key was stolen you can remove this device from the list and it will not be able to receive new changes
- so it may be more private than dropbox, because cloud provider shouldn't be able to read your files on their servers
- you still need to pay this cloud service provider to store your data
Anytype is much more than file synchronisation tool.
- it gives users an ability to create their own apps without coding using simple building blocks
- allows to share those apps with your family, friends or teammates and collaborate together
- fully free when using your own disk space or self-hosted server
- It is P2P. This means that you can sync data in the same network much faster, even if you don't have an internet connection
But the whole idea is that most of the users can create their own apps without code (airtable way) using existing building blocks(no need for APIs). And a small amount of users who code can create new building blocks
Peers who are interested in the content pin it.
- E.g. your teammates share the same files
- Your family have a shared photo album
- Your devices(mobile+desktop) share your private files
- Anytype provides nodes that store a small amount of encrypted data for free. Later we will provide an option to buy more backup space on our nodes to pin your encrypted data
- You also will be able to set up your self-hosted anytype node to pin your data
> Who pins the files when my laptop is offline? Who pays for this?
Currently, Anytype provides a small cache on our public nodes to store the last encrypted versions to mitigate offline/online problems.
You also will be able to set up your self-hosted anytype node.
> What keeps my files online in the event of high node churn?
- Peers who are interested in the content actually store it
- Anytype nodes
> What happens if malicious nodes join the IPFS swarm and censor key/value lookups
- First, you will do the local-network lookup. E.g. if you are working with your team in the same network you will be able to discover local-network nodes via broadcast msgs
- Anytype provide nodes that index the encrypted content. That nodes expose additional API that can be used to speed up P2P content discovery in that cases while being fully secure (because it is content-addressable)
BTW, I totally agree about transparency. We will opensource Anytype before the public release so anyone can inspect and build from sources
4. Definitely yes
5. Again depends on the available disk space you have. If you have enough disk space - you can store your data
Integram open-source platform – best services meets Telegram on a new level
Addictive slideshow for events (beards included)
Integram – collaborating with Telegram (FREE)
Just like Slack but on Telegram and totally free