Depends on what your blender is capable of.

It means your coffee pod machine just came online and the coffee is currently spewing from the spout … probably.

In Australia:

https://reebelo.com.au/

Very cool, didn’t know this existed!

For anyone who wants more: https://en.wikipedia.org/wiki/Schumann_resonances

If it’s never happened to you, how would you know that it’s happening at all?

Skin cancer is like an iceberg, what’s under the skin is what will kill you. Go and see your doctor.

Between the clickbait, YouTube “enhancements”, exploding AI slop videos and the atrocious search facility, the platform is rapidly becoming completely unusable for finding relevant information when you’re looking for answers.

As an entertainment platform it’s forcing creators to make long form content and making viewers sit through more and more low quality content.

It’s evolving, but I’m pretty sure it’s heading towards extinction, rather than greatness.

The shoes I’ve seen look like an orthopaedic horror story.

As a fully functional adult, I’ve been eyeing off light up shoes for years. So far, all I’ve seen is gimmick shoes you wouldn’t wear for more than an hour, so I make do with fluorescent shoelaces instead.

This seems like fun, though I’m not sure if I’d be game to walk up a set of stairs on them, perhaps I’m not keen on breaking something when I’d invariably trip and fall.

Wait until you get your head around awk 😇

The commands man and apropos are your friends to get you started.

Learning how to use specific tools like grep, sed and awk is a case of getting started by using them. Most of the subsequent learning process will focus around how to create regular expressions (regex), for which there’s also a manpage.

The “typical example” for a dd command is like saying, “here’s a great way to shoot yourself in the foot”. A better way is to understand that most of these tools follow the UNIX philosophy:

1. Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new “features”.
2. Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.
3. Design and build software, even operating systems, to be tried early, ideally within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.
4. Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.

Once you “grok” that, you’ll be in a much better place.

How would you suggest I respond in the future?

We have a person, claiming that CUPS doesn’t work and they now uninstall it on every installation.

There is no context, no data, no information that suggests what the issue is, what they tried, when this occurred, on which platform, under which conditions.

In other words, the user was essentially saying “CUPS sux”.

Having used Linux as my main system for over 25 years, that sentiment did not match my own experience, does not help anyone, not me, not the user and not the OP who was trying to solve a problem, let alone anyone else reading along.

I responded accordingly.

This has not been my experience … at … all.

Perhaps it would be helpful to discover what exactly doesn’t work for you and fix that, rather than remove CUPS because one time it didn’t work for you seven years ago.

You could print to CUPS from the other devices and potentially bypass all those shenanigans.

Also, CUPS has a PDF printer which saves you from even heating up your printer at all … I haven’t had a printer in my life for over 25 years.

https://en.wikipedia.org/wiki/1989_Tiananmen_Square_protests_and_massacre

There’s 10 types of people, those who understood binary …

It uses a security feature of Linux called cgroups or control groups to limit access to resources at a kernel level.

It’s used all over the place, including as the basis of Docker.

https://en.wikipedia.org/wiki/Cgroups

Wait until you see our dropbears. .

There’s a common but persistent misconception that Docker is like running a virtual machine. This is understandable but incorrect.

A better way to think of it is as a security wrapper around an untrusted process.

If you look at your running processes whilst a container is running, you’ll see the processes inside the container running on your “host” machine - remember, it’s not a host - guest situation.

There is no relationship between the user inside the container, unless you start mapping the UID and GID.

The only exception to this is the root user which shares the UID/GID with the actual root user.

See: https://www.howtogeek.com/devops/why-processes-in-docker-containers-shouldnt-run-as-root/

Edit: I suspect, but don’t know for sure, that the root user inside the container is actually the same user as the one running the Docker process, which is typically the root user on the “host”.

1. The Docker container should change the user to an internal one (created by the build stage) and the process should run as that user.
2. The uid and gid can be specified at runtime.

See: https://www.docker.com/blog/understanding-the-docker-user-instruction/