I tend to find myself obsessing over specific topics and projects. Hell bent on my goal.
In this case my goal was understanding AT Proto more indepth to be helpful in the private profile and ultimately data within the AT Proto and Bluesky application.
I put together a GitHub repo that served as a workspace for all the projects I felt I needed to touch to make this possible and if I could locally run the entire stack.
Adding settings to existing screens is as straight forward as adding a section to the existing profile privacy settings via Lexicon and adding to the Bluesky Api to set those new records.
The tricky part is how do I run a PDS locally where I can modify its logic to allow for assigning access to known followers. which is a part of the existing lexicons and API.
We have a few layers to consider. The AT Protocol, the Bluesky Application, and the Personal Data Server [PDS].
We want a solution ideally baked into the AT Proto, and PDS and a pattern that Bluesky and any other application will need for access control and privacy. Which as mentioned in the community discussion is separate concerns. Access control of who is able to open or receive a file is one thing. Complete privacy is another. The concept of a distributed ID [DiD] in IPFS represents a files Content ID [CID]. If we have a private gateway like Pinata does it not expose the CID at least? And if it does, will it expose personal identifiable information.
There is a balance with the Internet of privacy and access. The ole triangle of Security/Accessibility/Availability.
So far after my workspace efforts I reached out via a discussion board and was met with guidance from Erlend to read Paul's leaflets which inspired me to get into this platform and to reach out to Storacha (badass name) to get more context and see how I can get involved.
You'll be hearing from me Storacha!
Yours in code,
Stephen Traiforos
~ Triforce
PS I meant to publish this forever ago. I am writing a follow up shortly.