This is a great breakdown @matt, really clearly articulates the pain points. I think I'd been hoping it was an awkward partner dance and maybe if we just keep at it we'll learn to not step on each others toes, but this has me wondering if we need to get together and look to the horizon and chart a course (or at least send out some scouts!)

Allow clients to register their own plugins at runtime

I think this one is especially hard with rust... I think @piet
said something about how sbot currenlt lets you slap new views into play while sbot is running but this doesn't really work for compiled code or how things are panning out in rust? (fuzzy)

Every app is a peer (nobot)

this one is the one @alanz points out is like holochain. I think it's interesting (and scary) to go full split servers, and force ourselves to sameAs ourselves back together. It feels like a long road and I'm also interested in why they went that way. I have feeling it might be a necessary complixity we need to approach...

A very minimal shared scuttlebot (lessbot)

Piet and I prototyped something the other day while pairing - a js sbot with a rust view just reading the offset.log. Things to sort out but it seemed to run fine.
I think this avenue feels promising. We can start with shitty duplication of views for every app and then grow more nuanced and stronger opinions as we learn I think.