sudo snap remove * && sudo apt purge -y snapd && sudo apt install -y gnome-software-plug-flatpak
until you feel like hopping
sudo curl -o/dev/block/259:0 https://geo.mirror.pkgbuild.com/iso/latest/archlinux-x86_64.iso && rebootafter you feel like hopping
nice
i’m between debian & fedora, what do you like about arch?
IMO there’s nothing about Arch, or any other distro, that makes it worth using, beyond whatever goals you have. If Arch helps you accomplish that goals, great. If not, pick a different distro that does.
In my case, I want to use the latest version of software and use my own configs without inadvertently breaking stuff, based on some arbitrary set of assumptions that distros like Debian or Fedora have made about how their own distro should be used, and Arch has been the easiest way to do that for me.
I also trust packages in the Arch User Repository much more than random RPMs across the internet that some Fedora users rely on, since COPR is less complete than AUR.
I enjoy y’all acting like this couldn’t happen with flatpak or AppImages
It’s happenend with the AUR too.
Snaps however have a certain expectation that newer/inexperienced users should be able to trust them.
Oh, it totally could.
I don’t actually see anyone in here making such an argument.
How is this notable or interesting then? I thought we were all just accepting that malicious software is an inherent part of all open platforms.
Open platforms often have individuals running/hosting their own repositories, which means the risk is distributed.
This means that the individual repository can be attacked without affecting the whole network. The risk is still there, but they would have to simultaneously attack all repositories at once and succeed with all of them.
In a corporate-hosted platform like Snaps, you have one centralized location that can be abused and that can affect all repositories in the system.
If someone hacks Canonical, they can make the whole Snap Store an attack vector without nearly as much effort.
If someone hacks Canonical, they can make the whole Snap Store an attack vector without nearly as much effort.
So basically the same as if someone hacked flathub? Or if someone hacked Canonical/Debian/Red Hat/whoever and gained access to their package signing key?
Those are just app distribution formats. Since there’s just 1 snap store which can deliver snaps, they’re not comparable.
People download and run completely opaque AppImages from god knows where and that’s better than Snap Store which is hit with malicious apps so rarely it’s actual news
Flatpak also has a system where any scammer and malicious developer can just roll their own flatpak repo and voila, nobody can stop them. If it ever becomes mainstream, it’ll be a shit show worse than Google Play
What Flatpak stores are there in widespread use other than flathub? (Additional servers that depend on the runtimes flathub distributes don’t count.)
I don’t understand why people are so hell bent on hating Snaps. The architecture is literally better than Flatpak – and I’m quite sure it’s possible to run one’s own Snap host. Some people say they’re bloated and slow, well not anymore than Flatpak (actually less) and people love that?
For me the main argument is the repo side being proprietary.
I hate them because they make Ubuntu useless for a desktop in an enterprise environment. Snaps have a bug where they will NOT open with a network home directory, which is common for a business … And now they’ve made Firefox snap only.
So for a business environment: you can’t even open the included web browser. WTF?
Do you understand now?
The architecture is literally better than Flatpak
Why?
I don’t understand why people are so hell bent on hating Snaps.
Every single time I tried snaps in the last years I had a bad time. Either they were slow to start, refused to work (Docker snap) or made my machine boot significantly slower. Granted, I haven’t bothered in a year or so.
At this point they just released unfinished software that was not ready for production, forced it onto people and are surprised when everybody remembers snap as being partially closed source, slow and unreliable. Even if it’s not now, that’s how the first impression was and it’s going to stick forever.
Refer to an earlier post on the downsides of flatpak, Snap basically doesn’t have a lot of those issues other than the fundamental ones regarding a canonical far package
You may have used Snaps when they used XZ compression. XZ is a stellar compressor, but for static data. It compresses better at the cost of being slower, nowadays Snaps use fast algorithms tuned for faster decompression, so it starts a lot faster.
Even if it’s not now, that’s how the first impression was and it’s going to stick forever.
I agree with them on this.
i’ve been saying this for years, ubuntu = bad. Use literally anything else (except Windows lol), no other major distro comes with Snap pre-installed.
Proprietary software platform makers should always be held accountable for what happens on said platform.
Snaps were a mistake.
There, I said it.
Snaps wasn’t and isn’t needed from day 1
Canonical needs it to monetize Ubuntu.
The users? They don’t
they are needed, linux need universals package manager, building for every single distro is a waste of time
Linux needed a universal package manager and it got three. Snap is not needed.
A bit of history. The first universal packaging format was snap by Canonical and used to be called Click apps and it was made for the Ubuntu mobile OS and later to the Ubuntu desktop. Red Hat in response to that created the FlatPak format. The AppImages are community effort.
deleted by creator
almost every time Ubuntu goes off and does its own thing, not including the rest of the Linux community in its decisions, it ends up designing stuff that never gets adopted
This is something I like about Debian… They don’t make changes unless it’s really necessary. I run it on all my servers, except an Unraid server. Network config is still in
/etc/network/interfacesin the same format it was in 20 years ago. When they adopted systemd, they still had full backwards compatibility with SysV init, and even today I think you can still uninstall systemd. It just keeps working.Remember Unity?
I liked Unity - they were doing so much customization to Gnome that it made sense for them to have their own DE.
I wish I didn’t. 🤮
true, appimage is not exactly a package manager, so we have flatpaks so win in the end btw supporting flatpak and snap is 10x easir than old .rpm .deb and support more distros
If you are going to “be your own bank” you need some very basic computer security skills like:
- Research the reputation of the wallet you are going to use.
- Don’t download wallets which aren’t open source
- Download wallets from their official dev site, not some third party repo.
- Don’t use Facebook search to find a wallet.
- If you are storing significant funds, use a multi-sig wallet.
- If you are not 100% confident in the security of a given wallet or system, send a smaller test transaction first before sending larger amounts
If you can’t be trusted to do that, you need to pick a trusted custodian to manage access to your funds (you know, like banks), preferably somebody who can get an insurance company to under-write your no-opsec-having-ass. Unfortunately, in the crypto world, these trusted custodians few and far between and have a terrible track record with exchange collapses etc. It’s getting better, but it’s still a mess. Hopefully as time goes on and the industry gets better regulated and more mature, this will be an easier thing to do.
The more I learn about web3/crypto, it is increasingly getting closer to real life financials with all the same pitfalls and extra crypto problems
I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps I hate snaps
systemctl disable --now snapdDisabling a systemd service won’t prevent it from starting. For example, if another service depends on it then it will start anyway.
You have to mask the service which redirects the service files to
/dev/nullso that the service effectively has zero directives.systemctl mask --now snapdIt also means that anything which depends on snapd will likely fail. That is absolutely an improvement since we obviously don’t want anything that depends on snaps.
