Conversation

Notices

1. Christine Lemmer-Webber (cwebber@octodon.social)'s status on Sunday, 21-Jul-2019 19:03:01 UTC Christine Lemmer-Webber

   I finished adding the "Understanding Ocaps" section to OcapPub, now linking them to normal developer code flow and ordinary human social relationships. https://gitlab.com/spritely/ocappub/blob/master/README.org

   I know, this document is already long enough! The next part is How to Build It, I promise. But you should be well prepared in your mind to think like an ocap person for when I add the how-to-build-it section now.

   • Astra: Zero Luma (astraluma@cybre.space)'s status on Sunday, 21-Jul-2019 19:16:26 UTC Astra: Zero Luma

     in reply to

     @cwebber So the one thing I'm looking forward to hearing more about is a very practical question: How do we avoid every user having their own version of the fediverse collective database?

     Like, ocap'd LD objects would embed authz concerns in their identifiers (URLs), right? So each user would get their own set of URLs for all the stuff they interact with?

     This sounds bad for scaling? And also I suspect will break some things unless AP/AS/LD can deal with "object identity" vs "object handle.

     Christine Lemmer-Webber repeated this.