Fission Fragments Weekly Links for May 27th

Fission Fragments is our weekly links roundup, that has been on hiatus … for a while. We’re going to get back to weekly, usually Wednesdays, and will be posting here in the forum. You can also subscribe by email.

Weekly Links

Alcro, an Electron competitor that uses Chrome devtools and websockets

Via @bascule, we found out about Alcro:


Tauri Studio - An Electron competitor that uses webview

Found via the bascule Alcro Twitter discussion, Tauri is another project to build native desktop apps with web technologies. It features a Node based CLI and a Rust backend, although the project aims to be polyglot:

Today, Tauri uses Rust for the backend - but in the not too distant future, other backends like Go, Nim, Python, Csharp etc. will be possible. This is because we are maintaining the offical Rust bindings to the webview organisation and plan to let you switch out the backend for your needs. Since our API can be implemented in any language with C interop, full compliance is only a PR away.


Git LFS with IPFS Support

As part of some ongoing research, @ellttBen found an implementation of Git Large File Storage (LFS) integration with IPFS, sameer/git-lfs-ipfs.

This has given us some good ideas of how to integrate a git-based development workflow with IPFS and Fission.

Binary files of all kinds can be stored with your git repo, but then transparently stored in IPFS, rather than checked in and bloating the size of your repo. This could be particularly interesting for large photos, videos, and in general media files and assets.


Slack vs Discord vs Discourse: the best tool for your community, Orbit Blog

Our friends at Orbit (you know, makers of the Orbit Model of Developer Engagement, also in our forum) wrote up a giant community platforms blog post that’s a really good summary of pros and cons to help you decide Slack vs Discord vs Discourse.

We’re on Discord and Discourse, and also use it for our private / internal company spaces, too, which isn’t really covered in the Orbit post. We’ll get around to writing up our story at some point :slight_smile:


Anil Dash, CEO of Glitch, says we need “Yes Code” rather than “No Code”

At the beginning of May, Anil posted No Code is great, but here’s why we need Yes Code to LinkedIn.

We believe in a lot of these same concepts at Fission, along with additional step of making it so that users can own their own data, which should make it even easer to hack and remix apps and websites.


I want to own the database that my apps use, Grant Orndorff

Speaking of things we believe in and owning user data, Grant’s post about how he envisions users owning the data of apps they use is very similar to what we’re building at Fission. He covers SOLID and Urbit and how they’re not quite what he has in mind.


Fission Updates

Brooke explains her design of UCAN, a user authorization method that doesn’t need a backend, that we’re implementing at Fission:

User Controlled Authorization Networks (UCANs) are a way of doing authorization where users are fully in control. OAuth is designed for a centralized world, UCAN is the distributed user controlled version.

This week’s video chat is with Qri, an open source version control and sharing system for datasets, built on IPFS – join us Thursday, May 28, 2020 4:00 PM.

1 Like