[Request] Fluxer & Fluxer Canary x64/arm

[Emptiest]

What software are you requesting to be packaged?
Fluxer
https://fluxer.app/
Source: https://api.fluxer.app/dl/desktop/source/latest

Fluxer Canary
https://canary.fluxer.app/
Source: https://api.canary.fluxer.app/dl/desktop/source/latest

Not sure which of the stable or canary code will be hosted here post-release (see additional context), but this is the repo: https://github.com/fluxerapp/fluxer

Describe the motivation
Fluxer is a free and open-source self-hostable Discord alternative. Packaging the desktop client would be nice for Terra users. Additionally, packaging the Canary (testing) client would be a nice convenience for those helping the project with testing.

Additional context
Some details are still in flux at the moment. The main developer has been working on updating things from the now-months-old codebase in private, and should likely be updating the repo within the week. Currently source is available through their website linked above, though it's expected source will be available through their github once these updates have been published.

I expect the github repo will host the most up-to-date code, but am not sure since it hasn't been released yet.

Both x64 and ARM clients are available.

If details change, I will update this issue. Should know how things will pan out within the week.

[Emptiest]

The GitHub repo is updated!

I asked Hampus, the developer, what the plan is for pushing updates for stable vs. canary, and this is what he said (screenshot for "proof", text for convenience)

the way I've been doing it thus far and would be convenient to keep doing, is keep everything on main, which aligns with how we build all other services too
then, if I want to do a canary build from main, I specify canary when building the desktop app
those could maybe exist as tagged releases in the future
though for now they just upload the artifacts to our own S3, which gets served through the dl API

It seems it may be preferable to use the source tarballs from the download api on the fluxer.app website. I don't know if this adds complexity to the package scripts. Thanks for your work on this!

[madonuko]

@Emptiest we will probably not use tarballs from the website for security reasons.
By the way, since upstream removed the canary branch, would it make sense to only have fluxer-nightly for now since canary releases are not trackable right now as mentioned by hampus?

[Emptiest]

@madonuko The security argument makes sense.

Nightly would be... interesting. I don't think we've had anything like that before, so I'm unsure of how functional the resulting builds would be. I'm guessing without tagged releases on GitHub there isn't any good way to automatically identify stable or canary releases? If that is the case I could definitely ask him if he can adjust his CI or something.

[madonuko]

cc @hampus-fluxer, we would like some way to track releases of fluxer (e.g. git tags, github releases, or maybe some json files on your website stating the version & the corresponding commit sha)
Otherwise I think tracking the latest commit (which is what "nightly" means in Terra) is what we want for now.