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.

lil copy edits

phil 71982358 639f5166

+17 -14
+17 -14
shared/challenges_markdown/two/part_one.md
··· 2 2 [records](https://atproto.com/guides/glossary#record) in the 3 3 user's [repo](https://atproto.com/guides/glossary#data-repo) on the 4 4 [PDS](https://atproto.com/guides/glossary#pds-personal-data-server). These are stored as key/values in the user's repo 5 - divided by [collections](https://atproto.com/guides/glossary#collection). The API shows them as JSON via the api. Like 6 - this 7 - record of a Bluesky "like" 5 + grouped by [collections](https://atproto.com/guides/glossary#collection). 6 + 7 + You can get records from a PDS as JSON, like this Bluesky "like" record: 8 8 9 9 ```json 10 10 { ··· 21 21 posts, [tangled](https://tangled.org/) repos, 22 22 [standard.site](https://standard.site/) docs, everything like that is stored publicly on your repo as an atproto record. 23 23 24 - The records are stored in collections and have record keys. This is usually expressed by an at-uri like 25 - `at://did:plc:rnpkyqnmsw4ipey6eotbdnnf/app.bsky.feed.like/3mhbs2cnrl22r`. 24 + The records are stored in collections and have "record keys", sometimes called rkeys. By combining them with the author's identity, they can form an `at-uri` like this: 25 + 26 + ``` 27 + at://did:plc:rnpkyqnmsw4ipey6eotbdnnf/app.bsky.feed.like/3mhbs2cnrl22r 28 + ``` 26 29 27 30 This uri can be broken down into 3 parts: 28 31 29 - - `at://did:plc:rnpkyqnmsw4ipey6eotbdnnf` is the DID of the user 32 + - `at://did:plc:rnpkyqnmsw4ipey6eotbdnnf` is the `DID` of the user 30 33 - `app.bsky.feed.like` is the collection 31 34 - `3mhbs2cnrl22r` is the record key 32 35 33 - You will also notice that the record has a `$type` field, `app.bsky.feed.like` for the above record. This is 34 - the [lexicon schema](https://atproto.com/specs/lexicon) for the record. There will be more on this later, but for now 35 - it's important to know it's a [NSID](https://atproto.com/guides/glossary#nsid-namespaced-id) of the atproto app and 36 - shows how the record should look. 36 + You might also notice a `$type` field in the record, set to `app.bsky.feed.like` in the example above, matching its collection. More on [this later](https://atproto.com/specs/lexicon). 37 + 38 + For this challenge: Using what you learned from day 1 about finding the users PDS and their repo, find the following record: 39 + 40 + ``` 41 + {{at_uri}} 42 + ``` 37 43 38 - Using what you learned from day 1 about finding the users PDS and their repo, find the following record `{{at_uri}}` and 39 - enter the verification code 40 - found in the record 41 - for it below 44 + Enter the verification code found in that record below: