rentar42

You know that you too are writing in a script, right?

It doesn’t exist.

Wait. Again?

I was answering under the assumption/the context of of “Amazon wants to release an Android-based OS that doesn’t contact any of Googles services”.

So, when I said “easy enough to remove” that was relative to releasing any commercial OS based on AOSP, as in: this will be one of the smallest tasks involved in this whole venture.

They will need an (at least semi-automated) way to keep up with changes from upstream and still apply their own code-changes on top of that anyway and once that is set up, a small set of 10-ish 3-line patches is not a lot of effort. For an individual getting started and trying to keep that all up to do date individually it’s a bit more of an effort, granted.

The list you linked is very interesting, but I suspect that much of that isn’t in AOSP, my suspicion is that at most the things up to and excluding the Updater even exist in AOSP.

A cop out or a coping mechanism. Employers steal so much from employees: time, wages, sense of purpose, sometimes even health. And most of us don’t have good ways to stop them (because socienty). So stealing a bit back might actually help feeling less hopeless.

Yes, but those minor traces are easy enough to remove, especially if you don’t care about being “ceritified” by Google (i.e. are not planning to run the Google services).

Not to diminish what Valve has achieved there (it’s an amazing PC/console hybrid, love mine).

But a smooth experience without any hitches is much easier to achieve when your hardware variation basically boils down to “how big is the SSD”. The fact that all Steamdecks run the same hardware helps keep things simple.

I guess that’s also the reason why they are not (yet?) pushing the new SteamOS as a general-purpose distribution for everyone to use. Doing that would/will require much more manpower.

Not OP, but as someone using Ubuntu LTS releases on several systems, I can answer my reason: Having the latest & greatest release of all software available is neat, but sometimes the stability of knowing “nothing on my system changes in any significant way until I ask it to upgrade to the next LTS” is just more valuable.

My primary example is my work laptop: I use a fairly fixed set of tools and for the few places where I need up-to-date ones I can install them manually (they are often proprietary and/or not-quite established tools that aren’t available in most distros anyway).

A similar situation exists on my primary homelab server: it’s running Debian because all the “services” are running in docker containers anyway, so the primary job of the OS is to do its job and stay out of my way. Upgrading various system components at essentially random times runs counter to that goal.

I’m almost entirely with you on this.

But the only thing causing mind on my doubt is how excessively impulsive and not-in-control-of-himself Enlo often seems. That’s the only thing that makes “this is just a serious of very stupid decisions made in the heat of the moment” even somewhat plausible.

It’s a product that Atlassian is selling: https://www.atlassian.com/software/statuspage

Not to be confused with their statuspage for their services: https://status.atlassian.com/

Or the status page for their status page system (which apparently has an ongoing incident): https://metastatuspage.com/

An important first step that you can do before any “real” selfhosting is to get your own domain that you control. That way you can more easily switch providers (or start selfhosting) later on without having to distribute the knowledge of your changed email address to all relevant contacts and services.

I’m still using Gmail (lazy and it works), but I’ve switched fully to using only email addresses on domains that I own.

Oh, but at the same time every single line of business logic logs nothing of value at all!

I really like it and it clearly passed the code review without any issues. But I find the diagnostic messages a bit lacking, it can be hard to debug.

I fully appreciate the desire for more civil discussion.

But please be aware that tone policing has been used as an offensive weapon against many marginalized groups: “We get that you want to fight for your rights, but could you please do that in the form of civil discourse?” That phrase is almost always heard when years of civil discourse lead nowhere.

That only works when you’re willing/allowed/able to configure each users private device. I probably could, but I’d prefer not to.

Yup, the ad results in Google had to be whitelisted to increase the SO-acceptance-factor. But once that’s done it’s really not much of a hassle at all, but whitelisting is easy if you just check the recently blocked domains.

I know at least one FAANG company that had (has? don’t know) a policy of not using any hardware that was ever used in travel to China. If you had to go there on a business trip, you got a loaner laptop (and got your account severely restricted) and when you got back they wiped and discarded the laptop.

The usual primary talking point is that it was developed “too fast”, which is of course ignoring a bunch of very important “details”. But explaining why that is wrong takes multiple sentences, but shouting out the misrepresentation that pulls people in can be done in a second.

Fundamentally there’s no need for the user/account that saves the backup somewhere to be able to read let alone change/delete it.

So ideally you have “write-only” credentials that can only append/add new files.

How exactly that is implemented depends on the tech. S3 and S3 compatible systems can often be configured that data straight up can’t be deleted from a bucket at all.

Just a little addition: the majority of things that people associate with Linux as per your first item are actually shared by many/most Unix-like OS and are defined via the various POSIX standards.

That’s not to say that Linux doesn’t have it’s own peculiarities, but they are fewer than many people think.