In this scenario, alcohol is less bad than soda

If by “scenario” you mean you only want to observe single parameter, then fine, but that’s not really useful.

Alcohol is much worse than soda.

the risk of data loss at that point is high. you will miss things

that’s what makes it exciting 😓 😓 😓

I used to love Sailfish OS.

I guess I still do, but the problem is that while they recently expanded amount of devices they support, for some of them the “support” is just not what you think. Eg. I got Xperia 10 V just for the SFOS, but even though on their main list the device is listed as supported, turns out that camera, Android support and fingerprint sensor, these don’t work. To be fair, this info was possible to find on their forums, and I did not have to pay for SFOS (they offer 6 month trial), so they have nothing to gain from communicating so badly, but it is what it is.

So in case you want to try it, just really make sure you know to what extent your device is supported.

OpenTTD player

It’s nice when people guess which AI i used to generate my avatar.

…well, technically, yes.

If you are well-versed in the guts of the distro (grub, /etc/fstab, /etc/crypttab…), and have extra space, you could spend part of your weekend shifting partitions around and moving everything to the encrypted side, and eventually re-configuring your install and removing the old part. (Oh and don’t forget to chown your /home data if you have multiple users.) I’ve been there, it’s not fun. It’s fun[tm]. It’s just far easier and less error prone to re-install if you can.

(Yeah, I’m stretching the definition of “enabling it” reeealy thin here… 🙃 )

https://xkcd.com/538/

It’s much worse: They can re-use the same wrench.

(Disgusting, I know… 😝 )

Great point.

I provided reasons why I encrypted my drives but this one is even better.

(Another one could be if you need to get your computer to a repair shop, and for some reason you can’t just remove the drive.)

TBH even the way you phrased your question kind of proves it’s orthogonal. Yes, you can have the full matrix:

encrypted | backed up
----------|----------
       no |        no
       no |       yes
      yes |        no
      yes |       yes

In each case, you have a different set of problems.

• Encrypting a particular medium only means that it’s going to be harder to gain access to the data on that medium (harder for everyone, but trillions of less harder for someone who knows the password.
  • That’s regardless of whether you also have a backup.
• Backing up just means that a copy of the data exists somewhere else.
  • That’s regardless of whether this or the other copy is encrypted.

Sure, eventually, the nature of your data’s safety will be affected by both.

Disclaimer: I’m by no means a security expert, don’t take what I write here as advice!

Eg. I encrypt my disks. When I do, I basically encrypt everything, ie. all partitions (except /boot). Then on those partitions, most of the data is not worth backing up since it’s either temporary or can be easily obtained anyway (system files). Well, some of the data is backed up, and some of that even ends up on disks that are not encrypted (scary, I know!) :)

To be fair, just encrypting the disks does not solve all. If someone broke to my house, they would with almost 100% chance find my computer on, which means that the disks are not encrypted (technically still are, just that LUKS provides unencrypted versions as well…) So the barrier they would have to face would be basically just the desktop lock.

For that reason I don’t encrypt hard drives on my remote server, since the server is always running in a virtual environment so by definition anyone who’s maintaining the hardware can already open files from the unencrypted drives, ie. I think it would be pointless.

mary beach rodeo

thank you for sharing your password 😜

Don’t you mean LUKS with LVM on top? (That’s what I use, I’m not sure LVM alone even supports encryption…)

LUKS (I was assuming that’s kind of implied, I don’t think I ever thought of another way…)

but if somebody is eager and skilled enough to break in my home to get my disks, honestly they “deserve” the content.

The problem with “my disks” is there’s always some other’s people on it, in one way or another.

But of course, it’s your call. We all have gaps in our “walls” and it’s not like I’d be pretending that LUKS is all that matters.

I do, laptops and workstations.

It’s just too easy not to, and there’s almost no downsides to it. (I only need to reboot, once a month or two.)

Well, unless you consider the possibility of forgetting the password a downside, so for that reason I keep the password in a password manager.

In case my laptop was stolen, there would quite a couple fewer things to worry about. Especially things like client’s data which could be under NDA’s, etc…

Don’t take it the wrong way, It’s not a strong opinion at all.

The inclusion of the word “cloud” meant that I wanted to know precisely how other people’s computers are involved. My thinking was, since it got to the first paragraph on the site, (which I assumed was intended for the users), I thought it must be more than just the obvious, well, someone has to provide the hardware.

All I did was Google it, and the definition I found was not telling me much.

In fact, I’m already learning more; eg. I listened to some of the podcast with j0rge that someone linked here… So no need to fire this user yet.

Thank you for the post, especially the interview links; I’ll check them out.

I’m sorry, but it is a software engineering term. Maybe not from the area you are familiar with, but cloud native was the raging buzzword…about 10 years ago

I guess my point would be the same, but conclusion is the opposite. Yes, I’ve heard “cloud native” tons of times, but that is the problem with buzzwords: because they are overused (and often used a lot by people who don’t really know what they are talking about), for many people like me, they lose meaning in that period. It’s like “AI” nowadays, or “NFT” few years ago. The term loses its specificity (if it ever had one), and collects all the “bad smell” from people overusing – not just the term but sometimes also the methodology behind.

Honestly, for me rpm-ostree and Flatpak would be excellent terms to convey the architecture of Bazzite. I did have to go to here and to Wikipedia to learn that.

The suspicious part is that the “good folks making good shit” are defending it, and even doubling down because it makes people question the whole identity and of the project. (But I guess out that turned out after your post.)

(I recognize that it’s by no means all of the Bazzite’s good folks.)

I got to buzzword and then I gave up reading.

No and I stated it clearly in the OP.

I even looked up “cloud native”.

Cloud native computing is an approach in software development that utilizes cloud computing to its fullest due to its use of an open source software stack to deploy applications as microservices. Typically, cloud native applications are built as a set of microservices that run in Docker containers, orchestrated in Kubernetes and managed and deployed using DevOps and Git Ops workflows.

That term is extremely vague at best.

And guess what: If I just looked up the definition and ran with it, I would just shrug and toss the whole thing out. “Do I want to run my games as microservices in Kubernetes? I guess some niche group of people want…”

The whole reason we have this thread – and where I’ve learned what Bazzite is about (mostly from its users) – is because i did not fully trust the buzzword, and I already knew something about Bazzite in the first place.

That’s how “accurate” it is.

No it just means that the goal of the founder (or someone who’s posing as founder here) is to stick it up to us “luddites”.

Probably a wounded ego or something.

Founder here, the more I see this whining the more I want to keep it on the website.

OK, so now we know how the founder is treating their potential users.