Post

public broadcast and permission spaces deserve different sync mechanisms (and probably URI schemes). public into a global shared heap is sort of a special-case audience/scope. but it is important and different enough that the MST+firehose are worth it. all the other affordances+tooling is reused!

curious why it's called permissioned spaces rather than permissioned data?

I have a feeling that the framing of permissioned spaces is leading us down the route of a different URI scheme and the space as an authority, where as permissioned data acknowledges this is all the same scheme and records can consensually travels between many potential spaces.

𝕮@chrisshank.com

Let's take a look at long-form writing, an essay might flow though many permissioned spaces: - initial draft (size: 1) - feedback from close friends (size: 5) - newsletter for paid subscribers (size: 100s-1000s) - public distribution (size: millions)

bryan newbold

@bnewbold.net

I think I understand the vision you are advocating for, and see that others have been writing about it. but i'm not really convinced that data should be referenced+synced the same way across a lifecycle like that. I think having a common schema/representation is the main win.

17/8/26, 10:36 pm0 reposts4 likes

Totally onboard that sync is different but i have a feeling that a different addressing scheme breaks object permanence and there might be repercussions to that. Will start a thread of the forum to discuss this more!

bryan newbold

@bnewbold.net

there has been enough discussion that a longer form response is warranted (aka, I don't want to get in to the details here in this reply thread)