#protosocial — Public Fediverse posts

@reiver

These are all conventions, and domain-specific conventions at that in my perspective, addressed in latest (long) blog post on grassroots #ActivityPub #fediverse evolution. In other words the choice depends on the domain you are modeling, and the solution requirements.

I am musing on a #Protosocial AP protocol extension, which acts as an overlay network, that operates more according to the Actor Model. Actors can be of many types, can be created on-the-fly, be part of supervision trees, have different lifetimes, etc.

Also they are decoupled from Identity. The have ActorId of course, but a Person actor does not relate directly to the person, and might as well be operated by a bot script. How exactly I'll model that remains open, but #ActivityStreams Profile may play a role, as an Identity visitor's card to exchange, kind of.