As far as I understand, audio cards hold a buffer of the audio that should be played at any time. If the CPU can’t keep up producing new audio, it will loop to the beginning of the buffer. My guess is that when you suspend, the CPU stops producing new data before the audio card stops consuming it. And that’s why you hear the last part for a short instant.

It also happens on my devices, and it’s always happened on all my previous devices as far as I can remember.

Disclaimer: this is based on my understanding + a lot of suppositions. It might not be accurate.

Sure, that’s what I thought. And Ecosia doesn’t do the same?

I do have an opinion about Ecosia, but it’s just based on feelings, so it doesn’t even make sense to share it. Apologies for not answering your question.

Instead I would like to focus on this point:

Ecosia isn’t very private, since it sends data to Bing

Also DuckDuckGo does this, but they aggregate and anonymize that data before forwarding it to Bing. That’s probably the best they can do without building their own first-party infrastructure. I would imagine Ecosia does the same.

The gamescope micro compositor does make games run better. You can obviously run that on others distros as well, but on SteamOS it’s out-of-the-box.

Is SteamOS immutable though? I thought that was just Bazzite.

Personally I tried Bazzite because it was the recommended distro for a gaming device, and I liked it so much that it quickly became my main.

Bazzite may present a bit more friction if you want to do something “advanced” that would otherwise be trivial on other distros perhaps with just a couple terminal commands, but it makes all the “simple” things super-duper easy, and the system is almost impossible to break.

I would say this model makes sense for “ordinary” users that just need a computer to read email, view cat videos, open office documents, and in the specific case of Bazzite also gaming. In my specific case I also needed to write code (I use VSCode + Godot), besides the initial friction of learning to work with containers and SELinux, Bazzite seems to be fit for coding.

Thus, I hope immutable distros will stay and thrive. I hope that one day someone will make a distro that you can just set and forget on your grandma’s laptop, and I think this distro should be immutable, like Bazzite.

Thanks for sharing your opinion and expanding.

In the past I used to think the same. Or rather, probably naïvely, I considered the GPL to be a bit of a nuisance, and preferred LGPL or MIT software.

Now I’ve changed my mind and started preferring AGPL for all my code. If a big company likes your MIT or LGPL code, they can legally steal it. If it’s GPL at least you get some safeguards, but they can still take it and put it on a server without the need to release the source code. That’s why I started to believe AGPL is the only “safe” license approved by the OSI, at least at the moment.

Of course I agree that MIT and GPL or LGPL make sense in some cases, but I would say in general they don’t protect users’ freedom anymore in today’s cloud-first world.

I would say AGPL is the “safest” license still approved by the OSI. Could you share your opinion?

Well… I assume that might be illegal. Or maybe these rules would only apply to public software? For sure it wouldn’t be enforceable, and it would still allow criminals to use it to communicate privately between each other, but it would make it harder to exploit mainstream public apps (e.g.: WhatsApp) to scam or exploit weaker individuals.

I am not OP, but that would be the ideal solution for me. Unfortunately, KPXC does not support communication with the GPG agent and the team is not interested in adding this feature due to it being «[…] far more complicated than ssh-key management. There are already excellent tools for this, Kleopatra being the best».

You will have to transfer your containers before you can see them.

From Docker to Podman: full migration to rootless

Perhaps a bit unconventional, but CloudFlare R2 gives 10GB of free storage accessible as S3 with rclone.

Ah I see… I keep container configs in a specific directory, which contains one directory per-service, which contain all the config files + a compose.yml file to place them in the correct path in the container. I could commit everything to Git if I wanted to.

Regarding network and firewall, you could make a symlink to a versioned file and keep your config with the containers. Same for firewall rules.

I’m not sure what you mean by file sharing permissions. With containers you could give a different user to each service.

If you are worried about memory and disk usage, another option I’ve been exploring recently is using OverlayFS, which, among other things, allows you to inject a directory at a specific path. Again, this would let you keep all your configs where you fancy the best. I use it through Bubblewrap.

Anyways I realize that what I just described is far from standard… hopefully other users will suggest something less custom.

If your goal is to host services, I would recommend looking into Docker, and eventually Podman. Containerization lets you keep the configuration wherever you want, personally I use a dedicated a directory for each service.

Also, please note that a container is not a VM. It’s just a way to keep everything in one place.

Not FOSS, but OneShot: World Machine Edition is a great game based on this idea.

You might want to look into Island/Insular. https://f-droid.org/packages/com.oasisfeng.island.fdroid

Depending on your level of commitment to privacy, this might be a suitable solution for you.

Then what’s even is the point of this license? There will always be a third party distributing unofficial binaries.

And if this license forbade third parties to redistribute binaries, then it would no longer really be FOSS.

Fair enough, but then it’s the same thing as open-sourcing the code but not providing support nor binaries.

I mean, personally I also prefer it to FUTO’s proprietary license, that’s for sure. But I’m one of the few privileged users who can build from source.

If this license doesn’t impose any extra restrictions on the code (and as you say, anyone can fork and provide prebuilt binaries), then this would just increase the risk of spreading malware, with no real benefits for the original developers.

In my opinion, if you want to monetize your software without going proprietary, all you have to do is provide the users a convenient way to get it. There are some paid FOSS apps on Google Play, as well as some paid FOSS games on Steam. You don’t want to distribute binaries? Fine, okay, that’s alright and I respect your choice. You don’t want to provide support to non-paying users? Fine, that’s very reasonable in my opinion. But…

…do you want to impose extra restrictions on your code? Fine to me, but then you are no longer doing open source, don’t try to pretend you are. And if you are not imposing any restrictions on the code then you are imho just going to hurt small users. We shouldn’t fight small users imho, we should fight the big corporations exploiting FOSS code for their proprietary businesses. But if there are no extra restrictions on the code, then big corporations wouldn’t care.

That’s my opinion.

I’m not a lawyer, but this doesn’t seem to be compatible with (A)GPL licenses.

I would say this is going to harm small users more than big corporations. As a small user I might be unable to build from sources myself, so I would have to pay. But as a big corporation building from source would be something I can certainly do trivially, then I wouldn’t be subject to the restrictions imposed by this license.

Imho, if someone wants to force their users to pay, then they are not doing open source. Please let’s not try to pretend we are by adopting a OSI-approved license and slapping extra restrictions on top of it.

Just go AGPL for datacenter-oriented softwares, or GPL for drivers and embeddable code, or a proprietary license such as FUTO’s for end-user software.

All repositories related to emulation and Nintendo, some of which I backed up on a self-hosted Forgejo instance.

Also, everything that you use and doesn’t have more than 2 or 3 maintainers.

For me it was the same drive. I remember I had to generate a special file to convince VirtualBox to use the physical partition as if it was part of a different drive. I don’t remember the details. Quite hacky perhaps, but it worked.