Post #2291985

@mauve@mastodon.mauve.moe access control is similar to what I've been experimenting with in SAWA which effectively bottoms out in a kind of namespacing, in this case the remotes are the namespaces. locally you can track whatever remotes you want, some of which may be your own, some of which may be collaborators. the issue branch referring to the crdt file lives on every remote. git fetch will pull them all in but we don't have to proactively merge and update your local state. just having access to everyone's file is enough the present a merged view in the local web UI. if you take action like editing or commenting on the issue then you'll build on that merged view and you can commit that locally and push it out to your remotes. no signaling planned but I think periodic git fetch might be enough? and yeah if people want to build something more elaborate and p2p they can, it's not foreclosed on, just orthogonal