Thanks, I didn’t know any of this.

I just started a hobby project with Bun, it’s my first time trying it. I would like to know what you are referring to when you say “what Bun did”. Can you share more information?

This might not be your issue, but it might be useful to know: if you connect two disks with the same GPT UUID, they might start misbehaving. Perhaps GRUB might not care, but Linux does. Did you ever clone a disk or partition without changing the UUID?

Assuming you are not in a CGNAT, which is common for mobile networks: DNS with low TTL such as FreeDNS, pointing to your IP. And ofc, if you have a router in between, port-forwarding.

Otherwise, a VPN such as Tailscale. But you would need to install it on all your devices.

Otherwise, for HTTP(S) web services, a reverse-proxy such as CloudFlare.

(Personal opinion not based on scientific evidence.)

I would say that’s not possible for a hobbyist. The main issues with this kind of DIY phones are performance, compatibility with existing software, and most importantly battery life.

The Raspberry Pi was never designed to be used with a small battery while still staying connected to the internet to receive notifications all the time, like a smartphone. If you want to build a usable smartphone you will need an efficient co-processor to do these tasks. This could get complicated fast unless you use a CPU designed for this job.

There has been some interesting progress with desktop environments and small touch screens. Still nothing as good as Android, but nice UI is no longer the main issue imho.

As for compatibility, good luck running Signal, Matrix and Thunderbird in the background without draining the battery.

That being said, if you are just doing it as an excercise without expecting to build a device that will replace your main phone, you can definitely give it a try. Have fun and learn much!

Ah! Sorry for the textdump, and thanks for the feedback. I’ll keep it in mind in the future.

Sorry, not an answer to your exact question… Dockge might be the answer if you need a web UI to manage Docker containers.

If you need something more specific, like a button dashboard to run custom commands, perhaps you could build your own with Vite (Node.js). You will need to understand basic HTML, CSS and JavaScript. (EDIT: OliveTin makes more sense.)

As for authentication, you could configure a basic authentication on your favourite reverse proxy (such as Nginx), or look for something more advanced such as OIDC/OAuth2 through Keycloak.

Link for opting out: https://github.com/settings/copilot/features

In the “Privacy” section, set “Allow GitHub to use my data for AI model training” to “Disabled”.

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.

I have a feeling that this human step might be at the end of a chain of automated filters.

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.

No, only the local FS. But they have recommendations in their README for integrating with S3 with the help of other tools.

You are invited to join the CopyParty! This has a web UI accessible from the browser, also from mobile, files are stored directly on the filesystem (not encrypted or on a database) and you can mount it as a network drive on Windows and Linux. But it doesn’t let you sync files for offline use, at least not without the help of some auxiliary tools.

You won’t find anything simpler to install and configure than this.

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».