willdot.net / at-advent
forked from pds.dad/at-advent
this repo has no description
0
fork

Configure Feed

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

not actual words but an outline of stuff to write

phil 9782c4c6 b582bee2

+28 -3
+28 -3
shared/challenges_markdown/three/part_one.md
··· 1 - This will be explaing the car format and will have a download link to a car file we create that they can download. 2 - We can create a new web handler like. /day/3/{did} and it downloads the car file. 3 - Inside the car export is just one record with the verficiation code 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! 3 + 4 + The repo (repository) is a key-value store 5 + 6 + TODO blah blah merkle tree but not getting too distracted because this is about the CAR 7 + 8 + where do CARs come in? 9 + 10 + - nice neat serialization format 11 + - what you get when you export your repo 12 + - what apps get when they sync your repo 13 + - what PDSs send as proof for sync.getRecord 14 + - what gets sent over the firehose 15 + 16 + - header with root cid 17 + - blocks (cid, block) 18 + 19 + - block content is dag-cbor (already covered a bit from day 2) 20 + - there are also MST blocks (also dag-cbor, you can ignore them if you want) 21 + 22 + OH YEAH terminology note: dag-cbor is out, i think we're all drisl now? drisl-cbor? 23 + 24 + - CIDs (ignorable) 25 + 26 + ### Your CAR is ready 27 + 28 + Click the button below for your very own CAR export of an atproto repository. Search the CAR for your verification code and submit it below. 4 29 5 30 <a id="download-car" href="" class="btn btn-primary btn-disabled">Loading (JS required) &hellip;</a> 6 31