this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

start on day3 language

phil 6b4648ae a2b424e5

+8 -3
+8 -3
shared/challenges_markdown/three/part_one.md
··· 1 - Picking up from day 2: [records](https://atproto.com/guides/glossary#record) are kept in [repo](https://atproto.com/guides/glossary#data-repo)s on the 2 - [PDS](https://atproto.com/guides/glossary#pds-personal-data-server), and today we're looking at the repo! 1 + To recap: [records](https://atproto.com/guides/glossary#record) are kept in [repo](https://atproto.com/guides/glossary#data-repo)s on [PDS](https://atproto.com/guides/glossary#pds-personal-data-server)es. 2 + 3 + **Today we're looking at the repo!** Or at least its serialized format. 4 + 5 + The repo (repository) is a key-value store of repo-keys to records. The data structure used is called a Merkle Search Tree (MST), but we're not going to worry about that just yet. 6 + 7 + Wait, "repo keys"?? Remember [yesterday](./2) how an at-uri is made of three parts, `at://<did>/<collection>/<rkey>`? The second two parts together, `<collection>/<rkey>`, make up the actual raw keys (repo keys) inside your atproto repository. 8 + 3 9 4 - The repo (repository) is a key-value store 5 10 6 11 TODO blah blah merkle tree but not getting too distracted because this is about the CAR 7 12