@silverpill That'll do - thanks.I'm sure I saw some discussion relating specifically to collections - but maybe it wasn't in an FEP.
-
@silverpill That'll do - thanks.
I'm sure I saw some discussion relating specifically to collections - but maybe it wasn't in an FEP. -
silverpill@mitra.socialreplied to fentiger@zotum.net last edited by
-
trwnh@mastodon.socialreplied to silverpill@mitra.social last edited by
@silverpill @fentiger i think you can take the c7d3 stuff as mostly describing the basic authorization model of the existing fedi ("mastodon protocol", etc)
the one thing i'd personally like to work out is splitting out authorship information into a different property like dc:creator or schema:author, because authorship and authorization are not the same thing.
- no attributedTo implies server ownership
- some actor manages the collection
- the same id, indicating a self-managing collection -
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@silverpill @fentiger the other thing i toyed around with way back is to put the server software as the actor's `attributedTo` or possibly `generator`, but i think i'm coming around to the idea of signaling which clients are attached to any given actor. this is going to be necessary for e2ee but also very useful for determining which "client-to-client protocols" are supported