

It can’t. But somehow the dev hasn’t noticed I guess?


It can’t. But somehow the dev hasn’t noticed I guess?


Whatever you pick, do not install everything just onto “the server”. Pick some form of abstraction (VM, lxc, docker, kubernetes, …) to isolate and manage your services.
Important: do not host your own email, ever. Let alone as a beginner project. You can host it behind a forwarder that acts as the destination for the other mail providers, but don’t have a public facing, DNS registered mail server (neither at home, nor as a vps or something). It will cause nothing but problems. You will regret it. Quickly.


Give it time…


Generally not possible either. Unlocking the bootloader always wipes the phone. So unless it’s already unlocked, or it can be unlocked with some sort of exploit instead of using fastboot, it’ll be worse than a (bad) normal backup.


I like the use of color. Only where needed. Good emphasis.


You are severely missing what YouTube is for. The vast majority of people, probably significantly more than 99%, just go there to watch stuff. Very few ever make videos.
So yes, for almost everyone, content just magically appears there. Because of how many people use the site, that still means a very large (absolute) number of people make very diverse content. YouTube is excellent in figuring out what I want to see. Think of it like TV with the ability to comment, and having more variety and being on-demand and custom-tailored to my personal taste and interest. If there’s nothing I like on tv, I turn off the tv. I don’t start a broadcasting company.
In other words: me making content I want to watch doesn’t solve me wanting to watch something, and if I made it I already know it and it isn’t for me.
What makes YouTube worth visiting isn’t the site itself or how it was coded. But for the people that are on it. That makes it so hard if not impossible for alternatives to ever appear and be viable. You need the people for the site to be good, but people don’t come unless the site is good. The is no likely solution to this, not now, not soon, maybe not ever.


If there’s a description what the video is about, then the video.
Otherwise an article, but that I open any link and not just read the comments is pretty rare. Articles also very frequently have a summary directly in the post, as is more technical to copy it from an article compared to a video.
I will use it until it stops being viable. This used to mean “until the battery dies”, but I’ve also swapped batteries in phones not designed for it, and still had to get a new one as the batteries available weren’t OEM and so bad they basically didn’t work despite being new. Like phone always just turns off at like 40% charge. That isn’t “viable” in my eyes.
Now I’ve got a Fairphone 5. It’s only been a few years, but I’m planning on 10+ years if I can make it happen. In theory some new feature could get me to buy one sooner, but I highly doubt it. Hasn’t happened in the past either.


Being European, I’m assuming slimbooks aren’t really it easily available? Repairable, Linux-first. Very happy with mine.


In times of pre-optimized repos (like CachyOS) it seems rather redundant from a performance perspective. Other reasons remain valid though (learning or specialized optimizations or requirements).
Alternatively, it can also be considered wasteful (electricity/compute) when everyone compiles their whole system instead of doing it once in a central server.


Not moving to, but adding them as I understand it.


This is such a weird stance given the actual change that was made. No actual age verification, no external communication of any kind. All that got added is a number field. The ability to store a number labeled “age” for user accounts. That’s it.
There already is a field for first name and last name. You can leave them blank as well (most probably do). If any software requires a number to be there, just enter 99 or whatever. Unless this gets severely worse this is such a nothing-burger.
I’m not happy about any step into that direction either, but pick your battles (or hill I guess). This certainly is a weird one.


Mailbox.org is another candidate worth looking into.


Yes, but most people don’t even have one of those 3, let alone all 3.


Do we know what the real embargo date was supposed to be? Like was the upload off by hours, days, weeks?


Or another TV of the same manufacturer that has Internet access.


Doesn’t always help. There was a controversy a few years back that some TVs that are not connected to the Internet will use other TVs of the same manufacturer they find in WiFi range as a relay to offload their telemetry to the manufacturer anyway. I can’t remember how or if that was ever resolved. Or if it’s even illegal (anywhere).


Also sick of hearing about it. Not because I want to play it, but because I don’t care about it, at all.
Congratulations, you added to that kind of noise. For no reason, too.


Stable vs Unstable does not mean anything to do with bugginess or prone to breakage
It would be great if that’s how the words were actually used, but in most discussions I’ve seen it is certainly not the case. Also, when talking to new users, they are supposed to magically understand and know the word is used in a niche way in this context? It certainly won’t be what they take from it when hearing or reading it.
Unstable means packages update frequently including major versions
That’s what we have rolling or bleeding edge for. Sure, unstable can mean that when used within the same project/context. So having different releases be stable and unstable for the same thing, but across projects/distros that’s just confusing, especially for new people. Yes I’m aware of the historic reasons and the roots in software development, but I’d argue it isn’t helpful to convey the practical reality of the differences.
December 2026*