I think it’s applicable in general to any non-foundational software too, because why not, “never ever crash” look like great guiding principle regardless

I guess X just encourage one to don’t reply until they read all the replies. This is rather a good thing, so they don’t repeat whatever is already replied by the others. But yeah, X forces engagement, which doesn’t look ethical

This project seems quite interesting! Could you possibly share the design documentation while we await the github.com/inkandswitch... repository to be open? 🙂

Woah, that’s good to know! I somehow missed this at the website.

Yeah, I just rss-subscribed to your blog so I read it right after the note has been added 🤷

I am interested in the UCAN. It’s funny, I been thinking on implementing something like this, not using JSON/JWT but RON, before I discovered UCAN.

Very keen to see the impl :) And thanks for sharing!