all interactions on atproto are stored in your PDS (repo). Different modalities (microblogging/linkaggregators) use different 'Lexicons', a way to determine the format of the interaction, basically. Different lexicons are not mutually legible, but a platform can decide to support multiple lexicons if they want to. You can actually see the content of your PDS here: https://atproto-browser.vercel.app/at/wake.st You can see all the app.bsky stuff, thats all your interactions on bluesky, as well as the fyi.frontpage.unravel.comment. thats where this comment lives
thanks! getting closer to having an view of the dynamics of this place. So if someone wanted to make a feed of all your activity they would need to parse everything in all the different specific lexicons attached to each PDS that they saw.
Yeah, this is an unfortunate side effect of atproto not using a json-ld like thing. In ActivityPub everything extends from a base type that can show up in a feed, no such "extension" (or dare I say, trait) system exists in atproto lexicons right now.
so my last comment is rendered here: https://atproto-browser.vercel.app/at/did:plc:4vembyxavyiuv7zsajfaslnq/fyi.unravel.frontpage.comment/3l6nub6xxor2i so I guess this could be pulled in in a client app pretty easily
Thanks for this explanation. Sounds like they fyi needs a “save” lexicon so I can save this!
