Maybe try a different bed temperature? And I got some improvement after cleaning the bed with alcohol.

Uh yeah. That is more information… Sorry, I’m not that familiar with Snaps. It looks to my untrained eye a bit like the report on the Snap itself, maybe it advertises to support running in strict confinement. Which it could… but doesn’t do. (Alike the other channels, which you could install, but didn’t… It’s kind of buried with that kind of information.)

It’s confusing at least. And the user definitely wouldn’t expect it from that wording. So I’d view it as a separate bug as well. And dropping confinement without notice would be the third thing, I’d consider a bug.)

No need. It’s already reported. And known since Dec 2019. 👀

#947325

Yeah. And I’d say with the SELinux problems and with what OP wrote, the security model including things like a failure mode to fall open, …silently… There’s more things to be wary of, than what they wrote in those 4 sentences.

It may not be wise to use a Snap without first understanding the reputation/limitations of Snap.

seems the Debian Wiki has pretty much your take on it 😅

If I had to guess, this isn’t a bigger issue because Snap is mostly pushed by Canonical. And in a bit of a weird way (proprietary backend, exclusive apps) so… reception in the rest of the Linux community is …mixed. To put it charitably. It’s probably not that relevant for most people outside of the Ubuntu ecosystem. And probably also not a priority for Canonical or the proprietary software vendors.

Sure. I should have phrased it a bit differently. My point was more or less, why is the curl developer’s review of the performance in a hypothetical scenario a decisive factor here… That feels like super random information. Same with the other two people. I’m fairly sure this is true and all… There’s just no context given, nor is there a connection being made between the statements and the rest of the content of the article.

Lmao. Just add a big RELEVANCE? I mean why do they cite 3 random people’s opinion on random aspects of the entire concept? It’s supposed to be an encyclopedia, not a blog post…

Thanks for the link! But I’m afraid it doesn’t tell me much. a) FreeBSD isn’t even on the list, so I don’t know the numbers to compare it to. and b) there’s things like survivorship bias. Looking at numbers like this is literally the textbook example of how to do it the wrong way. You have to do statistics the proper way around. For all we know by those numbers, Linux could be the best battle-tested OS in the world. I mean they fixed 3 times as many vulnerabilities as Microsoft did for any of their products?!

Sometimes I wish people would back up their factual claims with numbers and studies.

Also: FreeBSD phone, when??

I dislike it. Usually I’d use packages from my Linux distribution. Or package it myself and maybe upstream the effort if my distro has a user repository. Now (this way) it’s down to everybody download random files from the internet and execute them. Specifically what every Linux tutorial instructs you not to do. Plus there’s no updates, no security, no version control or transparency. It’s not licensed in any free way, so I can’t fix it or adapt it to my liking, I can’t help you write better Python code…

But it’s your software project. You’re perfectly fine to do whatever you want with it. And it’s certainly commendable to write software, whether you do it for yourself, or put it out there in some way.

To give some perspective: BitTorrent was released in 2001. So in the 90s, you’d be looking at some precursor to that. And the first CD recorder to cost less than $1000 was sold in 1995. Before that, they’d cost something like a car.

We definitely shared and copied a lot of floppy disks back then. And music on tapes.

Shouldn’t the upgrade also update the bootloader’s default entry to a new kernel? The way I’ve been doing it was apt update && apt dist-upgrade. And then reboot once every 1 to 2 years if I feel like it, am bored, or there’s all these news articles about a severe bug in the kernel.

Syncthing or Nextcloud. There’s a bunch of Linux sync software: https://awesome-selfhosted.net/tags/file-transfer--synchronization.html

Traditionally, you’d just put it on a NFS volume and be done with it. Or make it a boring plain old independent laptop with nightly backups configured, if your users always work from the same machine and don’t like… switch to a different computer in the middle of a task.

The entire page is an advertisement for an AI tool that helped uncover it. Guess that’s the demonstration on how it augments a report.

Mint is based on Ubuntu. It’s not strictly tied to any Debian release channel?! There’s LMDE as well. That’s based on stable.

Sounds reasonable. Yeah, good luck. I’m sure you’ll figure it out. Unfortunately it’s always a bit difficult to diagnose problems over the internet, without typing in the commands and seeing the exact output. But there should be a way to make it work, F2FS is designed for something like this.

Did you read the Wiki? You need to either pass the compress_extension option when mounting it. The Arch Wiki lists how to enable compression on all text files. And I gave you the version with a ‘*’, which enables compression for all files. Or you do a chattr -R +c ... on specific files or directories to compress them. Maybe you missed that and that’s why it doesn’t compress?!

There’s probably also a way to debug it and somehow figure out what it does and how many files/sectors got compressed on the filesystem. Linux usually buries that kind of information somewhere in /sys or /proc, or there’s special commands to figure it out. But I’m not really an expert on it.

And there’s also files which just can not be compressed any further because they’re already compressed. Most images, for example. Or music or ZIP archives. If you try to compress those, they’ll usually stay the same size.

I haven’t tried it. But looks to me you need to add “compression” when formatting it. And then later when mounting, you’d add options like compress_algorithm=zstd,compress_extension=*

Remember to enable compression. Usually the Arch Wiki is a great resource to learn stuff: https://wiki.archlinux.org/title/F2FS

And don’t forget to back up your data if you’re messing around with your computer. One typo with the device names is enough to accidentally delete your harddrive.