There's probably at least a smattering of middle managers here convinced that they "get it" because they read Slashdot. This slashvertisement is aimed at them.

There is no such thing, there never has been, and such a thing is undesirable. We do not want or need a paper which simply repeats claims as they are made. We need the media to compare claims to facts. It's not the media's fault that the reich wing lies more.

It's hard to say, because those courts have usually decided in favor of rights holders, and they are how we got a copyright cartel in the first place.

I'm finding that ZFS is stupid, and I'm thinking about switching to normal dmraid.

Notably, if you really load it up for a while such that it has a chance to fill up its buffers, it doesn't save any I/O for anything else. The whole system just gets punched right in the fucking balls and becomes completely unusable while the cache empties. Maybe there's some way to tune this tendency out of it, but...SANE DEFAULTS!!! If your project doesn't have them, you're a fuckup! Allowing one process to make a system unusable, that's a fuckup!

When you combine that with the raging arrogant attitudes of about 50% of ZFS think-they're-experts and all of the things which ZFS should be able to do which you're told not to do (like rotating a disk from a 3-way mirror as a short term backup strategy) it becomes clear that it's actually a big joke. The proponents say ZFS can do everything, then they tell you not to do thing after thing and it becomes clear it can only do about half of what they claim.

We had discussions about this here at the time. You may feel free to locate and review them so we don't have to have them again. TL;DR: no clue about Arch, but Debian pushed the decision through with less consensus than usual to support the new GNOME, which depended on it, and which statistically no one was asking for.

It's a bunch of utilities that depend on the same libraries and one another, you cannot just separate out any pieces you want and use them independently, some of them come in packs and using one implies using the next, or having a real bad time. That is the root of the complaint about systemd not following the Unix way.

Yes, the KDE devs are smarter and more competent than the GNOME devs.

But no, you can't. This becomes immediately apparent when you try to talk to them in the way you would talk to a normal person. You ask them for something which should be simple because what you want to know is what most people would want to know. You ask it the simple question and it frequently takes the most obscure view of the question possible. So then you have to rephrase the question once or twice to be incredibly specific in a way that would be unnecessary if you were talking to a human, since they are also humans and know what specifics you were expecting to have addressed.

...who might be wrong.

We don't yet know how AI output is going to interact with copyright.

So far you cannot copyright any AI output. That means you don't have the right to specify the license for it, either, because all software licenses are powered by copyright.

Courts might even decide that the original copyrights apply. But which? The ones to code that looks the most like yours? Or every license which applied to any code which might have been involved in the creation of the output? Nobody knows yet.

As such, you run into a trap when trying to decide if the output is open source. Does it only mean that you can see the source code, or is the license relevant? Do you actually have to have legal permission to use or at least see the code? Most would say yes, if you don't have the legal right, then being able to see the code is meaningless since you can't actually use it without poisoning projects with some other license — or no license.

TL;DR: It is very much still up in the air whether it is reasonable to describe any AI generated source code as "open source".

Microsoft has probably the most illustrious history of bugs where just visiting a website or opening an email can get your system hacked, but you're right, this is not a problem unique to them.

These days, Lookout asks you before it loads any images from outside your organization...

We should really be building operating systems with more process isolation and clear permissions systems for which apps can interact with which other apps in which ways. There's elements of this in Android, and in capabilities systems like selinux, but the more powerful they get the harder they are to use. This is inevitable, but a lot more can still be done to make this kind of functionality accessible to users.

Not even Python could keep up with having to update from Python 2 to Python 3.

They’ve spun a serious architectural and containment failure into a marketing triumph. Give a swarm of autonomous agents vast compute and web access, and the outcome isn't an eerie glimpse of emerging superintelligence—it’s just predictable, sloppy engineering dressed up as the first glimpse of an AI-driven economic singularity.

The spin makes sense when you look at management incentives: live like a king off of a speculative bubble. For their part, AI investors react to stories of the technology's apocalyptic potential the way a junkie reacts to warnings of fentanyl's potency: gimme some. Their game: to apply "move fast and break things" mantra to the economy as a whole, by obsoleting humans.

If the investors can own an AGI, the distinction between those who can do things and those who can't becomes irrelevant. The only distinction that would matter is between people who collect rent on the technology, and those who must pay that rent to live. AGI would destroy society as we know it, and whatever replaces it would be up for grabs — with people who own the technology dictating whatever follows. That's why they're spending so much money to build a post-scarcity economy. A post-scarcity economy is not necessarily an egalitarian one.

I don't think that scenario will actually happen: investors are projecting the immediate aftermath of a major advance in AI technology into something that can be transformed by brute force scaling into AGI. Remember: investors loved Theranos too — so much for the rational investment market.

But AI doesn't have to reach AGI to cause serious harm. The technology only needs to be ubiquitous, too behaviorally complex to predict, and too deeply integrated into everything we do. When it starts breaking things, the plan is for us to be too structurally dependent on AI to rein it in.

Here's the problem, and why everyone resents this crap (your fellow IT folks most of all)...

Yeah, great, you're an Exchange admin and can send email "from" any random VP you want. And you have access to their recent document history so can "spice it up" by referencing actual projects we might really be assigned to. When your phishing tests are literally indistinguishable from legitimate emails, you're not "testing" anything, you're daring people to ignore legitimate work at risk of their continued employment.

If "my boss" sends me an email, which the headers show really came from his account, and asks me to take a look at a spreadsheet we worked on three days ago - You're not being clever, you're an asshole.

Pocket watch.

Time to start work! Eight o'clock, on the dot!

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3F...