mirror of
https://github.com/anyproto/docs.git
synced 2025-06-08 05:47:05 +09:00
use for example instead of e.g. according to Google developer documentation style guide
This commit is contained in:
parent
f1f0cfffd1
commit
a5bb316246
3 changed files with 6 additions and 6 deletions
|
@ -26,7 +26,7 @@ There are some technical details on encryption and data storage:
|
|||
|
||||
* Anytype stores changes for each object you’ve created
|
||||
* Every object’s change has 2 encryption layers with different keys. 
|
||||
* the First layer is used to connect changes within an object (e.g. all this encrypted data belongs to the object with id \<abc>)
|
||||
* The First layer is used to connect changes within an object (for example, all this encrypted data belongs to the object with id \<abc>)
|
||||
* Second layer is used to encrypt the actual data. We using AES with stream **encryption** with CFB mode
|
||||
* When you create a new change for an object, we periodically send it to our backup node(with only the first-layer key). More info about sync [here](syncing-and-p2p.md).
|
||||
* Anytype backup nodes have access to the first layer key, so it can group changes for the object and send them in one pack when you want to restore your data
|
||||
|
|
|
@ -4,15 +4,15 @@
|
|||
|
||||
Anytype is Offline first; hence, all data you create will be stored locally first. After that, the data is synced to the backup node and your devices for redundancy.
|
||||
|
||||
We use a private IPFS network and [ThreadDB](https://docs.textile.io/threads/) to handle storage. It is a Peer-To-Peer file system that facilitates decentralized data storage across devices. Furthermore, we use the deduplication feature to reduce storage. E.g. If the same picture is uploaded three times, there is only one image copy stored to reduce storage consumption.
|
||||
We use a private IPFS network and [ThreadDB](https://docs.textile.io/threads/) to handle storage. It is a Peer-To-Peer file system that facilitates decentralized data storage across devices. Furthermore, we use the deduplication feature to reduce storage. For example, if the same picture is uploaded three times, there is only one image copy stored to reduce storage consumption.
|
||||
|
||||
{% hint style="info" %}
|
||||
You can read more about IPFS here: [we-are-using-ipfs.-what-is-that.md](../faqs/we-are-using-ipfs.-what-is-that.md "mention")
|
||||
You can read more about IPFS here: [we-are-using-ipfs.-what-is-that.md](../faqs/we-are-using-ipfs.-what-is-that.md "mention").
|
||||
{% endhint %}
|
||||
|
||||
### Media
|
||||
|
||||
Media files are not directly downloaded in overall syncing to save bandwidth. Instead, when that file is requested, it is streamed to your device from the backup node or your devices on the network. E.g. If you have a 4k Video, it will be streamed from the backup node or P2P devices to your device.
|
||||
Media files are not directly downloaded in overall syncing to save bandwidth. Instead, when that file is requested, it is streamed to your device from the backup node or your devices on the network. For example, if you have a 4K Video, it will be streamed from the backup node or P2P devices to your device.
|
||||
|
||||
So when you open an object with an image, it downloads. When you press play on video & audio, it begins to download. After that, this file will be stored in the application cache.
|
||||
|
||||
|
@ -43,5 +43,5 @@ The Anytype Root Folder is a variable based on the OS where all your local data
|
|||
Anytype does not have a way to reference files from the OS files system. So all the files are getting copied when you drop media and files inside Anytype. We will introduce this feature later.
|
||||
|
||||
{% hint style="success" %}
|
||||
By the way, you can check our roadmap in the [Community Forum](https://community.anytype.io/t/release-plan-a-general-roadmap/1283)
|
||||
By the way, you can check our roadmap in the [Community Forum](https://community.anytype.io/t/release-plan-a-general-roadmap/1283).
|
||||
{% endhint %}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue