Pantherina @ Pantherina @feddit.de

Posts

120

Comments

3,420

Joined

3 yr. ago

Ah so Nekogram connected to Google?

I learned quite some things from this talk

https://youtube.com/watch?v=4WuYGcs0t6I&t=456

Appimages are damn broken

Dont spam please

Yes SELinux confined users or apparmor could allow sandboxing apps the same way as flatpaks.

On 2GB of RAM systems that would make a lot of sense.

Chromium cant use its native sandbox, Firefox supposedly can.

But Librewolf and more should be used as Flatpak, unless you need multiple apps to chat between (native messaging) which doesnt work yet, its way more stable.

Yeah for sure the not-badness-enumeration approach would be to not use the GPU and set a defined screen size and pixel density.

ungoogled chromium is likely less secure, no 1 is to have regular updates. With CI/CD those patches should be applied automatically. Would be a cool project but not for me, I prefer Firefox.

Good points.

Agree. But support by distros would make them acceptable. Only if they tick the basic security requirements of a repo, actual maintenance and download verification, this should be done.

Icons on Wayland are not possible, because of security. Apps could spawn a window that looks like Chromium and ask for a password, for example.

Do they need desktop entries, DEs should absolutely not create them for those apps.

Yes I think I touched the library issue a bit, but this is really bad. There is no updating system that could tell you what apps are affected too.

What do you want to achive with archiving, because of a potential takedown by Nintendo?

Just for your purpose you could just keep it installed and probably block it from getting updated. I am sure you could also backup the .flatpak file somehow, and all the dependencies would still be accessible.

flatpak runtimes are pretty bloated, when you use different versions etc. And its bad that you cant only use Flatpak, currently. But locally they use deduplication, so GNOME, KDE and Freedesktop.org will share at least some libraries.

But for sure, it may not be the best library management there is.

Its not evangelism, there are developers that thinl Appimage is an acceptable format and only support that. I dont know but guess some licenses prohibit user repackaging as Flatpak, so you have to stick with that pain.

I mean, snap could also be not. Just somebody needs to write a wrapper that allows to download, verify etc. .snap packages from other repos.

Shitty move of Canonical for sure.

You also dont use the Terminal for Appimages, its all shitty GUI patterns taken from Windows UX.

The linux people and their repositories...

This would tick a lot of issues but please dont do that. People will get used to it and suddenly malware is possible again.

youtube.com/watch?v=4WuYGcs0t6I&t=456

For all the Grayjay/Newpipe/Freetube users

Very good video with additional points, will add them

Yeah I avoid installing stuff to my system but I looked into RPM .spec files and that should be possible too. Flatpak would be the way to go though.

Thanks, yes fully agree. There are a ton if shitty distribution ways.

When I publish stuff on Github (its never big, always small tools) I never let people git clone, just download the needed parts.

Releases are meant for that, but still, putting software on repos may be annoying but its the correct way to do.

If you add an "!" Before the image link it is displayed in line!

I tried making a KDE theme too and it either looks like that, or random parts are colored differently.

But everything blue... haha no thanks

Thats a very constructive point!

Explained in a other comment how a pain it is to verify such a signature.

Is that stored in the appimage file?

I find it funny how flatpak neglectors always spell it wrong

Hahaha, SimpleX on Android is fine, the Desktop client is kinda incompatible with anything (no flatpak, the ubuntu version is kinda broken, no repo, their sync requires a random firewall port to be open)