@adamwiggins I'm running Fedora on a Dell XPS 13 and everything's pretty much plug-and-play.

Hearing good things about Slimbook laptops as well.

@casraf not quite drop-in as the API is different and you have to deploy your own backend.

I've been thinking of hosting a public backend for crdt_sync but it runs into the same issues as above 🙂

@casraf creator of Firedart here: I give them instructions to create their own.

No way I'll risk my Google account or spend my time monitoring what people are doing with it.

I still remember how often I had to clean up dongs when I first published https://draw.cachapa.net

Couldn't let this go last night, and ended up redoing the version generation.

The new version reads both the pubspec, and the latest release.

If the latest release is higher, the patch is incremented, otherwise it just uses the pubspec as-is.

@filiph for apps I create GitHub releases and the build system uses the release name as version name. The version code is simply the CI build number.

I still have to type the release name manually but the rest is automated. Ex: https://github.com/cachapa/tudo

An improvement could be specifying major and minor in the pubspec and having patch be the CI build number, e.g. pubspec says 2.5.0 and it's build 241 so you'd get v2.5.241.

That way you can just push to auto-release.