Working out an input syntax and set of UI patterns for @spritelyproject's Fantasary textural virtual worlds (graphical also planned, textual comes first) that's also "safe". https://groups.google.com/d/msg/cap-talk/Wa6VR-k3bLo/NXAugow8AgAJ
Most ocap security patterns have actually already been "solved". UIs are the big frontier. Trying to make some headway, a step at a time.
See also:
https://github.com/cwebber/rebooting-the-web-of-trust-spring2018/blob/petnames/draft-documents/petnames.md
https://github.com/cwebber/rwot9-prague/blob/secure-uis/draft-documents/secure-user-interfaces.md
@cwebber @spritelyproject
Very interesting, although is it possible a medium other than Google is available? I'm very uncomfortable using it.
If you want an ActivityPub solution for groups, check out https://groups.qoto.org - you could create an equivalent @spritely@groups.qoto.org group.
@jfred @torresjrjr @spritelyproject I'm also iffy on Google Groups, but cap-talk is where the community of experts who are best fit to review my proposals hang out. I could move these writeups to some org-mode documents kept in git after they settle a bit though, and I think that would help maybe?
@cwebber @jfred @spritelyproject I see. No worries. It's not really my place to demand so much. I should understand #OCap first and become familiar with the discussion anyway.
@torresjrjr @cwebber @spritelyproject cap-talk is a group that has been around for a long time and, while Spritely is related to it, it's not about Spritely itself. (It's also not Chris's group to move.)
I'm similarly iffy on Google, but I subscribe via email and it basically acts like a mailing list so 🤷♂️