In context, I interpreted it as a furry costume.

That example isn't a random wifi network, it's the Xfinity network.

But also, you think tv manufacturers are sane? They have proven that they don't deserve the benefit of the doubt, in my opinion.

Cory Doctorow's book Enshittification introduced me to the term Technofeudalism. Wikipedia describes it as "a modern economic system where big technology companies have power similar to feudal lords in the past. Instead of land, these companies control digital platforms, data, and online markets. People and smaller businesses rely on these platforms, just like peasants once relied on feudal lords for land and protection." Yanis Varoufakis wrote a book on it, Technofeudalism: What Killed Capitalism.

Seitan is a pretty common food among plant-based eaters.

Sarcasm?

haha, yes, sorry.

you needed more exclamation marks :)

The gentleman's /s tag.

Or say "That's unpossible!" so we know for sure.

I mean, 55k commits in 3 years, that's about 55 a day, 7 days workweek. It's reasonably implied no one can be looking at all them thoroughly.

This incident is unrelated to what was committed to the repository. More info: https://docs.litellm.ai/blog/security-incident-oct-21-2026

What is the word for this type of troll that feigns lack of understanding?

sea lions

From this Wondermark comic [1].

[1] https://wondermark.com/c/1062/

Gaslighting

"Both" requires allocating limited die capacity to products that have over an order of magnitude less margin.

These days, most things that I run that aren't from my distro's repos get their own bubblewrap. On top of this, I use opensnitch. Even if I trust the application (uncommon), I never trust npm, pypi, etc. any longer. It's tedious to set this up and OSes should be helping make this easy.

Agreed. Programs like Zoom, Steam, and other closed source "apps" should always run either in a separate user account or in a bubblewrap.

I agree. But sometimes I struggle with finding the right files under /dev or /sys so that the necessary hardware is accessible to the program. Is there some documentation that gives a good overview over the different device and system files? For example, if a program wants to use my web cam, how would I figure out which files to mount?

You may need a general knowledge in device and device drivers in Linux (the BSDs behave the same but follows a simpler approach). Basically the naming scheme is based on the driver name with numbers and letters appended for device ordering. So sda1 means scsi disk (sd driver), a for the first one, and 1 for the first partition. Linux added a few folders and scheming for better interactivity.

/sys is powered by sysfs, which is actually a database as file and folders. OpenBSD doesn’t have it (and /proc too), so if you need to interact with kernel objects, you need to use C and the system library. But on Linux, you can do a lot with basic read and write on files.

An LLM can be useful to help you figure out stuff like that.

Never make the mistake of anthropomorphizing David Ellison.

It would make more sense to compare with Qwen Image 2, since that was the last open weights Qwen model.

Edit: This is wrong.

Wait... is that true? I don't think the original Queen Image 2.0 was ever released beyond an API. At least, I don't remember a public weights release.

I promise I searched on my phone before posting that, but it looks like I misinterpreted an hf search result that was actually Qwen-Image-2512 but the url was truncated to Qwen-Image-2 due to my screen width (ugh). For some reason I was thinking Qwen Image 2.1 was the one that had been available for a while but not released, but you're right that was 2.0.