flatpak-external-data-checker VS wormhole-gui

> Maybe. The CI rules should be made public in that case, though, surely? Maybe they are?

Agreed, but thankfully they are. The PRs link to <https://github.com/flathub/flatpak-external-data-checker>. That said, it'd be clearer if the flathubbot 'user' profile also linked to that URL.

> The enormous amount of value the distros bring [...] is audit of packages (and packaging).

Yes, auditing against supply chain attacks is good! But there's also a risk in running outdated software. I don't have easy answers. But if automation leaves more time for the hard part, great.

Flathub provides an excellent tool to keep your dependencies up to date, so it's just a matter of adding it to the manifests. Besides, who says 'dependencies not being updated enough' is a valid metric to determine the quality of a package? LOL.

According to Github issue/PR #126 new builds are failing because of a bug in flatpak-external-data-checker or some incompatibility between the two projects at least.

I'm surprised the documentation says that since Flathub itself runs its CLI scripts via Flatpak: https://github.com/flathub/flatpak-external-data-checker

Another thing you could add would be to tag your releases on GitHub, add a tag field next to the commit one, and add an x-checker-data section to the manifest so the Flathub bot will automatically open PRs to update the Flatpak release when you update your repository.

See f-e-d-c, and if you're not planing to submit to Flathub, then look at the GitHub workflow example there. Be aware that auto-merging is not acceptable for anything other than extra-data sources.

Unfortunately the maintainership of the Zoom Flatpak on Flathub has been a bit slow, but you can still install it since the Flathub bot do automatic builds whenever there's an update, thanks to the provided flatpak-external-data-checker service.

There is https://github.com/flathub/flatpak-external-data-checker which automatizes the update pull requests including dependencies. Flatpak has other downsides, but security or not getting the latest and greatest is not one of them.

I’d say wormhole-gui (https://github.com/Jacalz/wormhole-gui), but I might be a bit biased :)

> No, seriously. It’s so simple I thought I missed something. But no. After you run that binary, you have a fully operational node of Syncthing. It’s ready to sync with any other Syncthing node, no other setup necessary. There’s no installers, no package management (but there are packages if you want to), no registration, no email, no logins, no password creation, no 2FA, no consents, no user agreements.

The most similar experience I had to this in recent years was using a program called wormhole for peer to peer file transfer: https://github.com/Jacalz/wormhole-gui

It was refreshing in a similar way; I download and open up the program, a friend does the same, and we can send files to each other, with a code genereated from the program. None of all this accounts stuff.

(For what it's worth, file sending has a similar issue as backup/sync that the author described -- most modern services are some centralized/cloud form, as opposed to the old days of ICQ/AIM/etc. where you could actually establish a direct connection to a friend and send files.)

Any reason for not just using the go mod vendor support? That was what I have planned to use in the future. Actually managed to get a working Flatpak. Could do with some tweaking, but it is generally working now :) https://github.com/Jacalz/wormhole-gui/issues/23

TLDR at the bottom.

It seems the answer is Brian Warner's magic-wormhole. You're gonna see lots of file transfer sites with wormhole in their name, but if you want security you should use the original one, which is BW's m-w.

It is implemented in Python [1], so it's hard to install.

So someone made a Go version of it [2] that has binaries for windows, Mac, Linux, BSD etc. But it's command line so maybe not suitable for lay people.

So another person made a GUI for it that also has binaries for all OS [3].

Also there is an android app [4]. Someone needs to implement an iOS one.

[1] https://github.com/magic-wormhole/magic-wormhole/

[2] https://github.com/psanford/wormhole-william/

[3] https://github.com/Jacalz/wormhole-gui/

[4] https://github.com/psanford/wormhole-william-mobile/

TLDR: ask them to install [5] and [6].

[5] https://github.com/Jacalz/wormhole-gui/releases/

(click on 'Assets' under 'Latest release' and download the zip or tar.gz for your OS)

[6] https://play.google.com/store/apps/details?id=io.sanford.wor...

Try it, it's usage is cute and really feels like magic.

It seems like there’s already a GUI version. If you still want to make your own, go for it, but I figured I’d mention this in case you hadn’t seen it.