Post

I like that you made it so when official spaces spec is made it's just a data migration thing because I too am lazy heh

tbsky.appflo-bit (@flo-bit.dev)ive decided to just do a thread about the why's and how's of permissioned data in contrail instead of a blog post, cause i'm lazy, so here it goes: 1/9

unrolled thread:

dholms.leaflet.pubPermissioned Data Diary 4: The Big Picture - Daniel's LeafletsA special edition of the data diary that sketches out the rough shape of where we're heading.

main idea: - do permissioned data like you usually would (in your own database), but copy the structure (as close as possible) 1-1 from @dholms.at blogposts with the eventual goal of moving everything over seamlessly once permissioned data actually lands

- that means there's a simple ACL with read/write access for everyone in a space & people can create, list, delete etc spaces using xrpc endpoints - similarly record CRUD is as close to the normal putRecord, deleteRecord, listRecords, getRecords, etc xrpcs as possible (just with an extra space uri)

- auth works using service auth tokens (like bluesky dms) and contrail instances publish a permission set with all the xrpc calls for convenience, so other apps can access the permissioned data a user has access to too