just got done updating an old conflict free replicated data type library:
this is a bunch of counter and set types that in a distributed system can converge to the same state from epidemic propagation... just counters and sets, i made it more tidy and its concurrent safe
i will be using the Last Write Wins set type to implement a permissions scheme that parses a custom event kind that creates a permissions hierarchy for access control to a relay, for now it will just be a simple CLI and library code for creating automated access control systems like for subscriptions
the access state messages will be private to administrators, owners and users themselves will be able to read their own record but not each other's, according to their privilege - admins can see all users levels, and read them but can only change users, owners can see everything everything but can only change admin and users
the LWW CRDT will resolve with a tight time threshold and the event kind will require very tight windows of acceptance of timestamps so there is very low chance of concurrent conflicts
actually, this might be a reason why i should use OR (observed-removed) sets since they allow this conflict to be seen and then the algorithm can make a resolution
the event database itself will be the source of this information and altering the access control list will be done by publishing an event and authenticating
eliminates the need for a separate configuration aside from specifying a list of owner keys in the main config
