streamdeck-ui VS flathub

Unfortunately, the StreamDeck doesn't emulate a standard USB HID device, so it needs a driver running in the background to detect button presses and do things like generate keystrokes or call Keyboard Maestro macros.

There's streamdeck-ui (https://timothycrosley.github.io/streamdeck-ui/), which is an open-source alternative, but it at first glance it seems to be only for Linux).

There are a bunch of other macro/launcher pads like the StreamDeck that DO act as standard USB HID keyboards, though, and those should work fine with Keyboard Maestro using keyboard shortcut triggers.

Found that one which seems to work with older models. https://github.com/timothycrosley/streamdeck-ui or https://flathub.org/apps/com.feaneron.Boatswain

what OS do you have on ur pi? from what i know stream deck is only compatible with Windows and MacOS, you’d have to do a special setup to use it with Linux

Not sure if that keyboard has open source editing software, but Elgato Stream Deck certainly does.

tbh I didn’t have a problem with the official Windows app so I can’t say anything about that much

But under Linux I used this

https://timothycrosley.github.io/streamdeck-ui/

Works pretty well by my experience under Debian. There are some edge cases like Wayland (see the issues) though.

The only tip I'd have would be for Wayland users who suffer from not having global shortcuts work with OBS: obs-cli with obs-websocket have you covered. Set a keyboard shortcut or Stream Deck button (using streamdeck-ui) to execute an obs-cli command and you're done.

Anyone have any experience with the ElGato Keylights on Linux? I use Ubuntu 22.04. I have stream deck that I use with Streamdeck-ui and I wanted to know if anyone uses these lights with a cli program that would allow me to control them? On, Off, brightness, etc?

Thanks for the info, I wasn't aware of the Stream Deck. It is also supported on Linux by Open Source library and app. Very tempting.

https://github.com/timothycrosley/streamdeck-ui/

> Nobody ever even audits the binary contents of flatpaks on flathub (were they actually built from the source? the author attests so!).

IME/IIRC There aren't (or shouldn't be) any binary contents on Flathub that are submitted by the author, at least for projects with source available? You're supposed to submit a short, plain-text recipe instead, which then gets automatically built from source outside the control of the author.

> The Flathub service then uses the manifest from your repository to continuously build and distribute your application on every commit.

https://docs.flathub.org/docs/for-app-authors/submission/#ho...

Usually the recipes should just list the appropriate URLs to get the source code, or, for proprietary applications, the official .DEBs. Kinda like AUR, but JSON/YAML. Easy to audit if you want:

https://github.com/orgs/flathub/repositories

I also don't believe third parties maintainers packaging software on flathub is a big issue but I'm also not familiar with how other distro repos trust their maintainers. Hopefully more developers maintain their flatpak themselves (or someone they trust) and get their apps verified. If most apps are verified, warning users of unverified apps might be a good idea.

There's ongoing discussion about splitting open source and proprietary apps in to seperate repos [1]. Additionally having seperate repos for verified and unverified apps might make it more obvious where an app comes from in the cli.

But I don't know how seamlessly an app could transition between being in the third party repo and being in the official repo. Having the user quietly stop receiving updates seems like a bad idea, but automatically migrating might not be desirable either.

I also think flatpaks cli interface needs some work. It is functional but far from distro package managers.

Being verified is especially important for critical apps. Recently someone added malicious versions of apps to the snap store [3]. This lead to people getting their cryptocurrency stolen.

[1] https://github.com/flathub/flathub/issues/691

[2] https://docs.flathub.org/docs/for-app-authors/requirements

[3] https://forum.snapcraft.io/t/temporary-suspension-of-automat...

That means Linux users can now install Bforartists on any Linux distro easily, regardless of glibc version! https://github.com/flathub/flathub/pull/4295

Still having some problems with the flathub build, see https://github.com/flathub/flathub/pull/4082 for the current status.

Here is the flathub draft pull request: https://github.com/flathub/flathub/pull/4082

i assume you dont know how flathub works , theirs little or no QC , done flathub is just get told theirs an update for the package , if yo go look at the github repo pes https://github.com/flathub/flathub/pull/4164 for example , only updates the link to the girt repo , theirs 0 code checked

It all should be written in pages for contributors, read the docs for fusion, and the docs for flathub.

These are criticisms of the flatpak ecosystem as it stands today. Currently, the Firefox ESR package on flathub seems to be caught in limbo or maybe dead. Mozilla publishes both a snap and a flatpak of Firefox latest, but only a snap of the ESR version. This raises the question of why. Have Mozilla chosen to invest more in snaps than in flatpaks? If so, what's their reasoning? (More users on snaps, making it similar to why they put more investment into Windows than Linux? Something else?) If they haven't invested more into snaps than flatpaks, is this a sign that it's harder to maintain flatpaks (or at least on flathub) than snaps? If that's true, I would hope that flatpak/flathub would be soliciting feedback from Mozilla about it.

Because that may be very hard to sandbox: https://github.com/flathub/flathub/issues/3366