We are a neighbor of France and it has been illegal here for at least 18 years. I still get called about twice a year by people trying to sell me solar panels, wine, stocks or elder care services,

As German-speaking people can read on https://netzpolitik.org/2025/g... it was the public prosecutor's office who asked for the home to be raided, not the vice chancelor. And they knew that the raided person also posted antisemitic stuff, which is also illegal. They just didn't mention this as the official request for the raid.

People from the US have been made fun of for being unable to drive a stick shift for decades. You can start mourning its death, when it vanishes from European streets.

Then why did the US give up paying in cash?

As someone whose job includes commenting on every f***ing CVE that is reported for the software on a customer's device, I look forward to this reducing the number of CVEs. There are lots and lots of CVEs that do not compromise the security of a system and at most are locally exploitable DoSes.

Please point me to the paragraphs that gives the works council this right.

The case you mentioned might be due to paragraph 112 BetrVG. That paragraph says that the employer and the works council have to agree on a plan (Sozialplan) for what happens with the employees affected by significant restructuring. The works council will try to prevent unfairness towards those that leave the company. Those that stay are not in focus as long as the company can continue to function without those that leave.

Works councils in Germany have no say in voluntary termination agreements (AufhebungsvertrÃge). The works council has to be given a chance to comment on involuntary terminations (which makes a difference if the terminated person sues) and it negotiates company-wide agreements (Betriebsvereinbarungen).

You can't be serious. This is one of many projects funded by Germany's Sovereign Tech Agency. They are also funding or have funded Python, PHP, Scala, R, SDCC, JUnit, GFortran, OpenJS, Haskell Cabal, and Ruby Gems. And it wasn't their idea to fund Rust Coreutils. Project have to apply to get money.

It's seemingly being used - actively - by governments (particularly, Germany) to reimplement important parts of the open source ecosystem.

Source?

The measure ran out because those lawmakers, who wanted scanning, wanted to make it mandatory and were not willing to accept a proposed compromise.

What the article forgets to mention is that almost every tech expert was against it. There were also several big petitions that tried to change the lawmaker's minds.

Scanning of online communication invades the user's privacy and implementing mandatory scanning as proposed would have enabled the government to abuse it. What these big tech companies now mourn is that they no longer have an excuse to violate their user's privacy to make money - at least not when sending messages.

What about services that access the internet on behalf of other applications? If you use systemd-resolved, like many modern distributions, all applications will connect to the local service to perform DNS lookups. On older systems you might find nscd doing the same, although the reason and method are different.

To which process does Little Snitch map these requests?

Zhaoxin continues VIA's cpu business.

DM&P (known for Vortex86 cpus) continues SiS' cpu business (SiS55x cpus). SiS previously bought Rise (known for its mP6 cpu).

How would I implement this?...
The birth date could be stored in a new field in /etc/shadow.
Then maybe a DBus service listening on the system bus that can be asked for the age bracket of a user. The existing systemd org.freedesktop.login1 service would match nicely.

It is too difficult to require the birth date to be entered on account creation. Instead allow the API to return that the information is missing.

To limit API usage to app stores, the DBus policies should be used. So this has to be configured on distro level.

The list of possible age brackets should be configurable, because not all countries/states will specify the same age brackets as Colorado.

Maybe we also need a mechanism that will ask the used if they allow an application to know something about their age that is not covered by the age brackets (e.g. "is at least 21" when the age bracket is "18 or older").

And what Cellebrite does is ok because they are selling to the US?
Or because they didn't steal from the US?

It's not about paying for the commercialization. It's about making a huge profit by selling in the US.