vortexsurfer

Had a similar thing at work not long ago.

A newly deployed version of a component in our system was only partially working, and the failures seemed to be random. It's a distributed system, so the error could be in many places. After reading the logs for a while I realized that only some messages were coming through (via a message queue) to this component, which made no sense. The old version (on a different server) had been stopped, I had verified it myself days earlier.

Turns out that the server with the old version had been rebooted in the meantime, therefore the old component had started running again, and was listening to the same message queue! So it was fairly random which one actually received each message in the queue 😂

Problem solved by stopping the old container again and removing it completely so it wouldn't start again at the next boot.

What an amazing businessman!

I'm a Norwegian Linux enthusiast and have never heard anything about the government using Ubuntu or Linux. Seems unlikely, from what I know. I know that within healthcare Windows is still widely used, even on the server side...

On the other hand, a lot of software for official services is being developed as open source now, so that's at least a good step in the right direction. Example: https://github.com/navikt

I literally have an account there dedicated to porn. Have had it for years. I stopped using Twitter after the muskocalypse, except I still check my porn account every once in a while.

You have to actively go looking for porn there, but once you do it's a neverending rabbit hole. Especially if you're into some niche/fetish stuff. There's some unique stuff to be found there...

It actually wouldn't surprise me if this turned out to be true

You can self-host Bitwarden, and sync your vault to your phone. Maybe not an option for everyone since it requires some technical skills, but very doable.

Oh yeah, I was there for that! Good times! 😂

You can google "women in computing" for more details, or check out https://en.wikipedia.org/wiki/Women_in_computing - it's amazing how much women contributed to this field and how little known that appears to be. (I only learned about it a few years ago myself.)

But the gist is:

Early on (i.e. the 1940s and 50s), men thought the prestige and honor was in building the giant machines (which back then could fill a classroom or more). Actually programming them was considered easier, "just like following a recipe", so women got jobs as "computers" who did this part. To quote that wikipedia article: Designing the hardware was "men's work" and programming the software was "women's work."

Fast forward to the 1970s and people had started realizing that programming was actually hard, and so it was promoted as a field boys should get educated in, while girls were encouraged to instead become nurses and teachers and such.

If you want to make your playbooks/roles more universal, there's a generic package module which will figure out what package manager to use based on the detected OS.

Or, if that doesn't fit your needs, you can add conditions to tasks (or blocks of tasks), like

when: ansible_os_family == "Debian"

and use that for tasks specific to a given Linux distro/family.

Ansible will detect a lot of info about each host and make it available as facts. See for example https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_vars_facts.html

I believe it was more like: a guy was accused of cheating (against Magnus Carlsen), and anarchychess on reddit came up with the buttplug theory. Now everyone thinks it actually happened.

There are many ways in. Sometimes no one has to click on or do anything, instead the attacker finds a security vulnerability in e.g. a web application, which gives them access to the server the app is running on. From there the attacker can look for other vulnerabilities to penetrate further into the network. Or if the system/network admin hasn't properly configured/secured the network, then the attacker can easily move into other parts of the network.

No, you give the AIO container access to your docker daemon and it will create / handle / supervise all the other containers nextcloud needs.