I don’t use such terms, but I’ll try a possible explanation: There is indeed a certain tendency. Articles are mostly written by speakers of that language. For example English articles by English-spreading editors tend to be influenced by western ideology. If you’d look at, I dunno, Russian Wikipedia, I’d assume it’s a similar situation.

It’s known that there are indeed paid government agents editing Wikipedia. But even those that are not are influenced by the Zeitgeist, which itself is informed by state propaganda. So we don’t need to assume intentional malice.

Ideally, people complaining about Wikipedia would have the time and skill to improve it. But that’s easier said than done.

the post already links to a summary, but tl;dr

the state seeks to charge Meta for supporting grooming of minors, because adding chat encryption obstructed law enforcement. Criminalizing the design decision to add encryption might deter all companies.

Some of the most damaging evidence in both trials came from internal company documents where employees raised concerns about safety risks and discussed tradeoffs. […] the rational corporate response is to stop putting anything in writing. Stop doing risk assessments. Stop asking hard questions internally. […] That makes everyone less safe.

That’s pretty wild 😉

It’s not always about the leength, but how you use it.

At work I use kubernetes and quite like that (upgrading containers without downtime FTE), but I didn’t bother trying to set up the infrastructure myself. Some argue, it’s not with the efford for self hosting, I dunno.

What I do like to use is Dockge, to keep docker but also keep your sanity. It even offers a single button for “docker compose pull”, which is great of you don’t have to many compose files / stacks. Combine with a simple shell script to batch pull/build all stacks in one go, plus some backup solution, and it’s actually nice to use and does all that I need. I love CLIs, but I’ve had situations where the GUI came in very handy.

#! /bin/bash
# note: this will update and START all dockge stacks, even if you stopped them before
shopt -s nullglob
for proj in /opt/dockge /opt/stacks/*/; do
  echo "> $proj"
  docker compose -f "$proj/compose.yaml" up --pull always --build --detach
  echo ""
done

Gotta copy that, thank you!

It’s great until you unmute it

This happened to me yesterday. Turned out that the site had a password length limit on the reset-password-form, but not on the login page.

As a new user, I’ll just say thank you

Sadly, I don’t see anything in the article (or those linked from it) regarding why they should avoid Signal specifically. The issues mentioned apply to other messengers as well. This move might just lead to worse alternatives without solving any problem.