Private Lexicons

[attpslabs.com]

Hi,

I’ve read a lot about permissioned/private data, and for me it has always been about keeping the contents of a post private/shared with a pre-approved group of people.

I’m wondering if anyone has explored using lexicons in a permissioned/private manner.

How could this be achieved without severing interoperability? Has anyone given this any thought?

[zicklag.dev]

There’s definitely been a lot of thought.

Northsky sounds like maybe the closest thing to what you’re describing.

There’s lots of thoughts in this thread:

[Proposal] Shared private Data for social posting

After some experimentation with Appviews and researching the PDS reference, I’ve written up a proposal on how we at Northsky intend to handled shared private data with a PDS/Appview to create a form of community only posts. The core of it is, a lexicon mirroring app.bsky which when used stores the records/blobs separate from the public data which an appview then uses for hydrating feeds where data is exposed within configuration boundaries defined by domains witihin the lexicon. Please give the…

Also check out the permissioned data diary from the Bluesky folks that is slowly coming out with more posts:

Daniel's Leaflets

[attpslabs.com]

Ohh I missed so many posts on that leaflet, guess I will have a place to dive back in, also appreciate you pointing me to Evelyns post! Cheers!

[zicklag.dev]

Just a heads up, some stuff apparently changed with Northsky since that article was written:

[Proposal] Shared private Data for social posting

So things have changed a bit with Stratos that might help some people who are looking for a solution. Stratos at the moment is an independent service, it functions by “enrollment” which is done via Oauth to establish a long lived token so that it can write a stub record referencing a record created in stratos. The Stub is public but private is not, public record holds no metadata only a reference. The private record contains the data on which boundary domain it belongs to and can only be access…

Just in case it takes you a bit to get to the bottom of that post.

[bmann.ca]

All the proposals also use Lexicons. The Lexicons have to be “known” – the Lexicons themselves aren’t permissioned or private (although some approaches have additional records added to carry permission info).

[evelyn.northsky.team]

Yep, in each case it has to be a unique lexicon due to the permissible metadata. I was thinking idly how to handle arbitrary lexicons and I guess you could just fire it right at stratos but then it doesn’t know the permission of it so maybe adding a verifiable “addendum” to the lexicon could work rather than making lexicon devs adjust or get it verified or something.

[bmann.ca]

You can add fields to lexicons that are just ignored so yes @evelyn.northsky.team you should totally follow that pattern if you want arbitrary lexicons to work with your system.

Someone still has to build an interface to view and render them.

A private microblog post is going to be different than an event.

[bumblefudge.com]

just off the top of my head, I think it makes a lot of sense for app data to be stored in the same lexicon regardless of what kind of repo it’s in, actually; feels like the shape+authN of the data and the authZ of that data should be decoupled if possible?