That closing the last tab closes the window instead of leaving you with a blank tab. And that there is not even an option in the UI to change this, and you have to go to about:config -> browser.tabs.closeWindowWithLastTab.

Nothing in the Qualys report nor the Ubuntu page for the CVE indicate that there is something to be fixed in systemd, only that you can create systemd-tmpfiles rules that will expose the vulnerability in snapd.

What do you think systemd-tmpfiles needs to do differently?

Yet another critical vulnerability in systemd

This is a critical vulnerability in snapd, not systemd. It sounds like it could also be exploited if something other than systemd deleted the files in /tmp/. Or if /tmp/ was not mounted.

No LLM use is benign. The effects on the environment, the internet, and society are real, and that cannot be ignored.

You can make the argument that in some cases it is justified, e.g.: for scientific research.

Linux-specific: as of version 147, Firefox respects the XDG base dir specifications, so you should be able to set $XDG_CACHE_HOME.

No.

If your home IP does not change often, you can use a dynamic DNS service. But your services will be unavailable from the time that your IP changes and the time the DNS record is updated and the cached responses expire.

I do not think the leaders believe that AI is going to replace most jobs. They definitely believe that they can use the threat of AI taking most jobs to further exploit the working class.

Servers are all Debian. Family member’s laptops are all Debian. I used Debian on my laptops for 20 years, but when Steam Deck switched to Arch, I switched my laptop to Arch to force me to learn it. I have a file with notes of differences between Debian and Arch. Next time I buy a new laptop, I will probably go back to Debian.

private property

Do you even cycle?

There are several reasons to do this:

• Most of the sensors that make the lights change will not sense bicycles, so the light will never change.
• In many places, getting a jump on the car traffic between the light and the next is much safer, because you are getting passed mid-block instead of at the intersection, where you are much more likely to be hit by a turning car.
• Jumping the light usually means being noticed by drivers while you are moving and they are not, which is great because drivers are notoriously bad at noticing at noticing anything smaller than a 7-11 when they are moving. I have been hit 4 times while stopped at stop signs and red lights, three of which while IN MY CAR, because drivers simply cannot be trusted to pay attention.
• Usually waiting at the light with the cars means the car in front of you is belching exhaust right into your face.

I now live in a city with very good cycling infrastructure, and a vast majority of people wait for the light, because when the infrastructure is designed well, it is safer to do so.

Cyclists act like a cyclist when it is convenient and like a pedestrian when it is convenient.

Cyclists act like a car when it is the only way to avoid getting killed in car-centric hellscapes.

Agreed, very suspicious. I would feel safe assuming that I can use the code under AGPL, but I would hesitate to use it for anything other than personal hobby because it would not surprise me if they closed their github account and never released any more code.

IANAL. I originally interpreted the license.txt as: all of the source code is AGPL (see lines 234-235), some of the source is also Apache 2.0, and the binaries are MIT; plus a trademark notice and contact info for getting a commercial license. After rereading it, my only conclusion is that this is a dumpster fire of a license.txt, and can be reasonably read several different ways.

At the copyright owner, they are within their rights to release the source code under the AGPL, and also sell it under other licenses. Anyone is free to use the code under the AGPL. Nobody who releases code under an open-source license is obligated to provide binaries.

As the copyright owner, they are free to use the code along with other non-open-source code (e.g.: SSO integrations) to build a non-free product.

Mattermost is licensed under the AGPL. How are they enforcing a 250 user limit?

Edit: the commercial version with additional features (e.g.: SSO) is limited. Obviously the open-source version is unlimited.

9

There were probably also people who voted for “yes AI” who would have voted for “a little bit of ai when I explicitly ask for it” if they had the option.

Stable. If you really want to use bleeding edge, I would use sid over testing. It breaks marginally more often, but gets fixed quicker.

Vive la France!