Interesting! My PSS prototype is built as a sync server for automerge documents, so the storage is managed by github.com/automerge/au.... I just define where to store those repos, and I do it according to a specified lexicon NSID, storing data along that path

8/ Second: local-first software applications can provide multiple AppViews for private data that _never gets published._ By using shared lexicons and data, independent local-first applications can smoothly interoperate, easily understand data sets, and modify them correctly.

7/ atproto lexicons + local-first software enables AppViews over local-first data, enabling 2 useful models.

First: local-first software can provide AppViews of private data and be connected via a lexicon to public AppViews that display data that was published to the AT Protocol

6/ To explore the idea of local-first AppViews connected to public lexicons, I made a local-first markdown editor for the @whtwnd.com blog using Automerge + @inkandswitch.com's "tiny essay editor". You can use it to draft your writing in private before publishing to atproto.

2/ First, check out the flexibility of AppViews on the AT Protocol. Here are 2 different views of the data from my Groundmist Library collection, one on the Groundmist Library site and the other on my website. They both use the same underlying data from my atproto data repo.