Nice idea!

In addition, we could have an allowlist for honest bots (like search crawlers).

I wish there was something more interesting to do there.

You are not expected to remember a v6 address - or even v4 for that matter. They are designed for machines. DNS is designed for humans.

What do you do on the yggdrasil network?

We need three four things:

1. A way to poison the data that will throw off the training without causing perceptible difference to humans. As I remember it, many image AIs were sensitive to a peculiar noise that was imperceptible to humans.
2. A skiplist of AI data stealers, so that their IPs/domains can be blocked in bulk.
3. Eventually, the above technique will become useless as AI data stealers will start using dynamic IPs and botnets to bypass the skiplists. We'll need to throttle or block data to visitors based on pattern recognition. For example, if the visitor requests linked pages in rapid succession. Or if the request interval is uniform or pseudo random, instead of genuinely random.
4. If the pattern recognition above is triggered, we could even feed the bots with data from AI models, instead of blocking or throttling. Let the AI eat its own s**t.

Oh! I misunderstood. Sorry! Glad to meet a fellow Gentoo here!

I use Gentoo with OpenRC. So my position in this matter should be clear. Anyway, check the last paragraph again to see what I think about systemd's modularity.

Python decided to use a single convention (semantic whitespace) instead of two separate ones for machine decodeable scoping and manual/visual scoping. That's part of Python's design principle. The program should behave exactly like what people expect it to (without strenuous reasoning exercises).

But some people treat it as the original sin. Not surprised though. I've seen developers and engineers nurture weird irrational hatred towards all sorts of conventions. It's like a phobia.

Similar views about yaml. It may not be the most elegant - it had to be the superset of JSON, after all. But Yaml is a semi-configuration language while JSON is a pure serialization language. Try writing a kubernetes manifest or a compose file in pure JSON without whitespace alignment or comments (which pure JSON doesn't support anyway). Let's see how pleasant you find it.

The kernel isn't a place to play politics. You can't just yank a component out like that on short notice, even if it has such a horrible story attached to it.

Back then, ReiserFS was mildly popular and its use would have been widespread (that includes me). The users of ReiserFS and probably even the other kernel devs had no idea that Hans Reiser was capable of such a crime. Infact, he was known as a computer prodigy back then.

There are plenty of users who don't have the luxury of migrating data on a short notice to a different filesystem. Disabling the filesystem would have left them high and dry. That's why the devs gave it a long deprecation period.

I thought IBM was still stuck with Watson. Have they moved on?

The licenses alone are enough to ensure that the opposite happens.

The OP can make the same argument after replacing sudo with doas or su.

There are other applications that use suid (like newuidmap). And there are programs that use capabilities (like ping). I'm pretty sure that this logic will be used to justify assimilating those applications too. But I'm sure that the crowd will cheer them on as if they did something revolutionary.

That's rich, coming from a company that sued a child whose website domain name was mikerowesoft.com. (His name was Mike Rowe, and the site was about the software he made).

Systemd is too egotistic to even mention Linux. They will simply name it systemd-defenderd.

Don't believe me? See this!

The vast majority of Linux users consider systemd as a good thing because it apparently makes system administration easier. They also don't agree that systemd is monolithic, because it's actually designed modular.

But of course there are detractors. The only thing I like about systemd is its declarative service definition and parallel service startup. But if I wanted to run an OS with bloated and inscrutable software (even with the source code), my choice wouldn't be Linux or Systemd.

I also routinely switch parts of my OS. This is harder with systemd. Although it is modular, the modules are so tightly coupled that it will prevent the replacement of modular components with alternatives. Frankly, I think systemd is killing the innovation in system component development.

You can uninstall the sudo application and add sudo as an alias for run0 in your shell initialization script. That's better than them renaming run0 to sudo, because that will prevent people from running the real sudo if they want it.

I think assembly was easier back then. Some architectures still are. But many architectures like x86 got incredibly complicated.

The problem is that all of those interdependent parts and software that are dependent on it become entrenched. There is no freedom to replace individual parts with an alternative because something else will break. That's what I call 'Modular in theory, monolithic in practice'.

So you hate flatpaks and not flathub in specific?