Agreed. I'll add that my main issue with Patchwork is that from what I can tell it's pretty much impossible to develop for it without using Node.js. I really th

Agreed. I'll add that my main issue with Patchwork is that from what I can tell it's pretty much impossible to develop for it without using Node.js. I really think that for this to take off, it needs to focus on 'developer happiness' right now. There's a solid client, a relatively vibrant and activist community, but too little in the way of (relatively) inexperienced devs like myself to build apps on top of. this is especially problematic because the Patchwork client, while impressive, is not something I enjoy using. I'm just itching to build my own alternative clients, as well as apps that run on the SSB protocol, but I can't unless I force myself to get back into the Node ecosystem. Another crucial issue, I find, is the inability to have multiple devices linked (by whatever means) to the same user. The impression I get is that the community is split on either fixing that, or adding more tools to deal with community management. I find that worrying because I've had multiple experiences with communities where ~50% was overly focused on 'preserving what is', and none of those experiences ended up in any kind of success. For the time being I'm still excited about Patchwork, and looking for ways to positively contribute (contrary to this post), but I get too much of a 'sixties imploding commune' vibe to feel comfortable wasting my energy, for now. EDIT: all this sounds somewhat negative, and my apologies for that. But I got and am really excited about the core proposition of the whole thing and just worry a lot about its viability. I'd really love to hear where I'm wrong, or how I could contribute without having to deal with the community kerfuffles that I am not too interested in. It's like CouchSurfing in reverse.