@linux Sharing a 'small' inconvenience I had to fix with #opensuse#slowroll (I suspect #tumbleweed is the same) - I couldn't launch snaps (spotify, bitwarden) after update - error was: cannot determine seccomp compiler version in generateSystemKey fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory
The fix (I first tried re-installing, didn't work) was to:
a. locate snap-seccomp - was in /usr/libexec/snapd
b. symlink: ln -s /usr/libexec/snapd /usr/lib/snapd
@pastermil@linux the attack surface for something that isn't officially maintained by the developers, and that doesn't have more vetting (e.g. distribution packages) opens up room for malicious actors.
e.g. #arch / #aur recommends verifying scripts manually before installing, and malicious scripts have been found and removed.
There are actors like #jiatan out there. An unofficial #flatpak needs manual verification before install - that's why I just go with #snap if the flatpak isn't official
Channeling Jerry Seinfeld. What's the deal with the lack of flatpak server/services software?
On Ubuntu Server a ton of command line tools and services are snap packaged. Why isn't this happening with flatpak? Is there some fundamental difference that prevents flatpak from being used like snaps are on the server?
‘#Meta’s ad tools are formidable, for everyone from your neighbourhood takeaway to multinational giants, and it’s a mammoth effort to stop the gap from widening further. It’s too soon to say whether #Snap’s efforts to close it will be successful – but it’s the things hidden from the normal users, as much as anything they can see on their phones, that will decide the next decade for the company.’ #Facebook#Snapchathttps://www.theguardian.com/technology/article/2024/may/07/techscape-newsletter-snapchat