Working on bringing Element Flatpak through the Fedora filter:
Mal eben schnell die neue @threemaapp Electron App geflatpakt.
Da ich selbst Threema aber nur selten benutze, möchte vielleicht jemand anders das ganze richtung #FlatHub submitten und maintainen. (Einrichtungsablauf siehe unten)
Flathub submission workflow: https://github.com/flathub/flathub/wiki/App-Submission
The Flatpak/Flathub community migrates to the Matrix side of life :)
Meet us at: #flatpak:matrix.org
I'm really looking forward to see everyone around and never have to worry about NickServ again.
Another day, another flatpak. Currently building a "Lens" flatpak.
Putting https://k8slens.dev/ into a flatpak. Once this is done and working, submitting to FlatHub :)
Currently a bit undecided about the permissions, because it contains a CLI feature, but probably less than more permissions.
Something that really drives me crazy is how everything K8s related boils down to "curl this binary from our website and run it in your full user context" 👀
This should help.
I find myself quite often in discussions about newer packaging mechanisms like flatpak or snap. It appears that a lot of people love to mixup the packaging software with the package provider/distributor. Most claims made against both technologies talk about bad maintained packages, not about the packaging system itself.
There are many good things that went into stacks like Flatpak. The packaging philosophies of some #flatpak distributions might not fit everyone's taste.
I have news:
We might don't rename the flathub repository. The Element developers pointed out that they don't plan to change the app-id, which means on our side, we just do a regular update and modify some meta-data.
What bothers me about that is that you'll use `flatpak install im.riot.Riot` to install Element… Rather strange but 🤷
Just for those who wonder: Riot was renamed to Element today: https://element.io/blog/welcome-to-element/
Flathub will provide the application under new name, I just have to talk to the right people to get the renaming/new repository done.
This weeks major contribution is done:
Started on Sunday, and here we are. A working parsec flatpak.
Might not be for everyone but those who consider cloud gaming an option, this might be a nice addition.
You can see the full development history on my GitLab instance:
Currently polishing up the parsec client that I packaged as flatpak last night.
Quite scary what this dumps into your $HOME directory.
It was a good idea to package it in a Flatpak that will take care of putting everything in the right spot.
Even weirder when their Websites states "clean uninstall", does that mean it scrapes the library packages it dumped into home directories out again? That sounds even scarier.
Hello people, please upgrade your #Riot installations if not already done :)
1.6.3 provides a security fix. Time to run: flatpak update
If you use the #flatpak version.
Enjoy your time, and if you feel bored, may checkout one of the many channels I founded:
If you didn't notice: There is a 1.6.0 release of Riot on its way to Flathub :)
Riot 1.6.0 bring the new and shiny cross-signing features. Means you get TOFU now, can cross-sign your devices and users, which allows easy to transfer trust between all your matrix sessions.
Just make sure you use RiotX on Android in order to have all devices compatible :)
Today I checked the #Firefox in #Flatpak from #Fedora. Looks usable on first sight. For most people that's a nice and easy step forward in browser security. Sadly I can't use it due to my integration with Yubikeys and other programs. But for most users who aren't using all this fancy stuff, It's a great option.
And for those worried "flatpak leads to outdated dependencies", nope, the version from registry.fedoraproject.org uses basically the same CI mechanisms as the RPM version.
I'm a professional relationship therapist for programs and their users.
This is my personal microblog. It's filled with my fun, joy and silliness.