Show Navigation
Notices by Lynn Foster (lynn@lynn.mikorizal.org)
-
Hi, we just released a new version of ValueFlows (v.3) at https://valueflo.ws/.
"Value Flows is a set of common vocabularies to describe flows of economic resources of all kinds within distributed economic ecosystems."
"Purpose: to enable internetworking among many different software projects for resource planning and accounting within fractal networks of people and groups. The vocabulary will work for any kind of economic activity, but the focus is to facilitate groups experimenting with solidarity / cooperative / collaborative / small business ecosystem / commons based peer production / any transitional economies."
@bhaugen @bhaugen @yaaps @mayel @ivan
-
@mayel
Love most of what you posted Mayel!
It is a challenge to use AP and still move to agent-centric communications in the fediverse. But I think it is important to do a minimum straight-up AP graphql api for the #commonspub C2S interface, so I'd like to try to get it to all mesh happily.
>"- Users can have several Actors. Actors can have relationships (and capabilities /permission) with each other. "
This is the one that I find possibly problematic. I think the goal should be for each person to have one Person actor for themselves, period. A Person can have many User (credentials) over time and for different methods of credentialing.
At the same time, people like to segregate the parts of their lives - so we would need a way to do that without creating more Persons. Adding something like Profile or Persona could solve that. Also, as Groups become supported and Persons can join Groups, that will become another way to scope conversations.
Here is a quick sketch of something that might work without changing AP, just extending it. Profile is a new actor type. A Person can have many Users. A Person can have many Profiles. Feedback welcome!
@bhaugen
@ivan
@alexcastano
@cwebber
@AceNovo
@Gargron
Lynn Foster
All Jonkman Microblog content and data are available under the