Post #1404627

conversations around this have been super generative, thank you everyone for your feedback 🙏 I think a compromise position that serves people who want to make their own non-browser frontends but preserves the underlying semantics this thing needs without requiring people to get automerge to work in their environments could be: expose the automerge update API over http. so the endpoint I would use in JavaScript would look like PUT /issue/:id where bytes is the automerge blob that comes out of automerge.save, everything managed in the browser. but I'm suggesting exposing another endpoint like POST /issue/:id.json "[{type: put_object, ...}], [{type: splice_text. ...}], ... (HTTP verbs and paths speculative of course) where you can upload a sequence of automerge document mutation operations. I feel like that could let non-browser users participate fully without burdening them with extra integration work if they don't want to do that.