I know you were talking about AI. It was just a quick jab at the fact they are both slop. Not really meant to be taken that seriously.

I am surprised it took them so long. It would have been the first thing to do, block new users, stop people takeong over orphaned packages or make the whole AUR read only for a while. Any of those would have disrupted this attack and gave the devs more time to figure out a longer term solution.

Are you talking about AI or self help books?

I don't think this is the win we want. Sounds like palwprld change the game to no longer infringe on Nintendo copyright claims. So Nintendo can no longer seek an injunction. They are still seeking damages.

I really want to see the copyright claims be challenged in court so we know where we stand. Rather then the continual settling out of court because Nintendo has more money.

It doesn't sound like Nintendo are on track to win or lose this. Just Palworld changed the game to limit the impact of the lawsuit. Which is in a way a small win for Nintendo.

Because that is not an escape sequence. Not sure there is any valid escape sequence. If you put any non space character on the line it will show the ticks in the block:

-```
```\
M  ```
```♪
```     a

Though looks like you can use more ticks on the opening block and the end will need to match that number:

````
```
```
````

Still more helpful then this error I have seen before:

error: Success

Use AI as much as possible. You will be juged on your usage. No wait, not that much. This shit is expensive.

This is what you get for jumping on the bandwagon without even seeing where it is going.

Its hard to argue that 2 config files both multiple lines long is simpler then a single line in an existing file. Adding a service to cron is just simpler. But adding all the extra bit you are going to want on top increases the things you need to learn to do and configure correctly.

IMO systemd timers are simpler to get right at a little bit more of an upfront cost to learning how they work. But cron is still simpler to just get something working without caring that much. I still find that ends up biting you in the longer term though though all the missing features you need to add manually on top of that one basic line you added.

Cron jobs are nice and simple to create. Until they go wrong then they are a pain in the ass. You need to manage logging yourself. If you forget you root mail will fill up your disk and crash the system. If you forget the mailto setting. If you remember it you justlose all logs and have no clue why something is not working. You need to redirect the output to a logfile yourself. And then risk filling up the disk with logs unless you remember to also set up logrotate. And you then still don't know when something last ran or if it ran successfully.

So many traps and that is just the logging side of things.

My favourite: The code does not work. You make a change, it breaks more. You undo that mistake: it now works.

That does not stop things from stealing your data.