iiinova — where your digital self keeps evolving

Replies

MasterR3C0RD @record.epqu.ca · 06/12/2024

5/8 For example, an atBB community might have administrators that edit forums, subforums, etc, or allow for moderating subforums, but also may have someone or something that would make posts to Bsky. Former would have create/modify/delete on `space.atbb.*` collections. Latter, C/U/D on `app.bsky.*`

110

MasterR3C0RD @record.epqu.ca · 06/12/2024

6/8 A sysop that owns the account would still have the password and would bypass permissions, allowing for low-level tasks like migrating the account, updating the DID document, etc. No lock-in for the gateway; it's all available over the protocol. And of course, it'd be very flexible.

110

MasterR3C0RD @record.epqu.ca · 06/12/2024

7/8 This could solve use cases where allowing multiple users to manage a single Bsky account is preferable; instead of sharing a password, larger social media accounts could delegate to multiple social media coordinators. Revoking is as easy as deleting their delegation record.

120