Comment Re:You now what ... (Score 1) 57
The most complicated thing with hosting your own stuff now is domain registration and DNS setup. For email specifically, that can be quite confusing.
The most complicated thing with hosting your own stuff now is domain registration and DNS setup. For email specifically, that can be quite confusing.
You'd think that you'd make your healthcheck systems scale proportionately to the number of systems you've got last reporting active. That seems like a good thing to do.
Personally, I'm not sure this would result in the remaining systems getting healthchecked more often, though. How would that work?
Let's say: you've got 1m servers and (say) 24 healthcheck system. They each send out one service API probe every, oh, 15 seconds, for something on the severely high side of things, with a 3 second timeout. If you suddenly only have 500k servers due to a network partiation, this doesn't cause healthcheck to occur at 2x against the backend services. Infrastructure isn't built this way, because if it was, the healthcheck would be meaningless.
Very different than what the client would see on the service facing side. Even then, it's going to cause 2-3x load to all the systems due to 2x the traffic to each system (assuming it was an extremely homogenous system) and cause things to be slow, and you'd have seen a different failure mode.
Sure there is: it gives you several days to download it on a shitty internet link so that on the day of release you're able to play it. Some people are stuck at 50Mbit or less internet speeds, particularly in rural or financially depressed urban areas. You're going to have people tethering their phone to download it.
I'm going to bet we'll have an AI port and unlock of the game by the end of the month.
It was licensed MIT. They didn't make specific claims about mislicensing.
Other people were "stealing" their private (public) PRs before they went upstream, was the complaint I understood, and not contributing their work back - which was all perfectly acceptable with the MIT license. So they're trying to prevent that (perfectly acceptable under MIT) behavior.
They don't like it, so they're cutting off access to people using AI. Simple as.
I've gotten modded down in the past for explaining this in depth, so I'll leave it at: that isn't how LLM weights work at all, and it invalidates your argument.
"free real estate to pilfer and exploit"
Um... that is literally the purpose of Open Source. Every license allows this to one degree or another.
"exploit our permissive licensing"
Well, you picked the license.
"hijack our work"
Zir, that is what you said they could do. (The license.)
"In some extreme cases, in-development feature code was being lifted straight out of our personal forks"
So they did exactly what the license allowed, and you allowed, by making the repositories public?
"In case you did not know, Asahi Linux forbids AI generated code contribution"
Ah, so there we go, we found the reason, you're opposed to your work being "hijacked" by AI people who aren't actually writing the code, and profiting from doing so.
Let's just be honest what this is: you're making defensive efforts to avoid AI contributions. That's fine, but I have one question: when will you be changing out the Linux kernel for something else? Huge swaths of it have had AI contributions at this point.
The more I read this, the more I realize: are they really talking about Caldera Linux (fraudulent Linux copyright/ownership claims), which was entirely unrelated to the gripe he's got? I'm not sure what other events , unless they're talking about the license issues with ATT/BSD in the very early 90s? This is not alike any of that at all.
If they're misattributing or not giving license for code they've written, that's one thing - and that's a problem. It's not a problem that's going to go away by changing the license: clean room implementations are both fast, and easy. (IME, I can often produce better code overall with AI than the original).
The fact is, copyright protection has gotten very complicated with AI, and it's not going to get any easier. It's not going to go away, and to no small degree, it's made a lot of nuanced software licensing for open source irrelevant: the cost to re-implement is negligible, it's the ideas which are going to hold financial value.
If you're contributing hand-written code to an open source project, I appreciate that you'd want to do that as a hobby you enjoy. Go for it. But also don't be upset when people continue to do the same thing with newer tools.
Sadly, this largely sounds like farriers complaining about automobiles. Yes, shoeing horses is a real, valuable skill (one still needed). So is writing code. But it is no longer prestigious in and of itself, and is debatably as professionally useful as being able to solve sudoku.
Other notable people who've done the exact same thing:
- Steve Jobs
- Barack Obama
- Zuckerberg
- Albert Einstein
- Tom Wolfe
There's a reason why it was common for men to spend a lot of money on 1-2 garments that would last them a year and were the same, every year, but women had a tendency to have more variety: changing your clothes is a vain distraction.
You probably do this to some degree, too. I personally only buy plain color undershirts and wear them with black dress shirts, the same jeans are on auto-order (it only took me a decade to find a brand/model that I like consistently), and sock preferences. Black tees for when it's just whatever, and black golf shirts for slightly nicer scenarios. I've been buying the same shoes and boots for 10+ years. (Do I wear other things on occasion? Yes. I'm not a billionaire who gets to run the room, I have to conform somewhat. I've got band shirts, etc. but I don't like having to decide every day.)
These are things you do as you find something you like that works for you, so you don't have to think about it again. Who wants to spend all that time shopping for clothes?
(On that note, there's a surprisingly large amount that you can get away with socially if you're well dressed.)
It means they are postulating something that's extremely biased in its findings and they've got no way to substantiate it, and it's likely easily refuted, but they're doing it anyway because they have an agenda.
Better look at the coal-powered Chinese monies that were used to fund the article.
"Possibly" is pulling a lot of weight, here. Nay, pretty much all of it.
What would they prefer? Coal fired plants, which pollute a lot more directly? Solar or wind farms, which pollute just as much if not more due to the production pipeline to make those machines? Hydro or nuclear? Perhaps we could go back to burning down our CO2-sequestering forests to keep ourselves warm and produce power from that, like Germany is doing now (due to prohibitions on coal)?
Of course, there are workable solutions here - nuclear being one of them. But nuclear has been prohibited for a half century now due to regulations and alarmism - regulations, in many cases, which have only made the likelihood of a nuclear disaster being more likely in our older plants.
The reality is that of the available fuel sources we have today, natural gas is by far the cleanest, least ecologically disruptive to harvest, and cheapest. It's also necessary that we continue to harvest it (and the other petrocarbons it's associated with) because without doing so, the whole of modern civilized world would grind to a halt and billions would starve to death. (This is even more true, now that Hormuz is effectively blocked and Ukraine is economically destroyed: nitrogen fertilizer largely is a byproduct of natural gas).
I'm so tired of 'green' alarmists coming to the table with problems without solutions being allowed. If you want to solve the problem, don't oppose all of the workable solution.
Thank you for this sensible comment.
model weights already more or less "contain" several partial OS kernels,
No, they don't. They were trained on that data, but they are not that data. You can't extract it from weights, and I highly doubt you'd be able to reproduce it from weights, even on an exceedingly large model.
At best, it's a work inspired by the original, not even a derivative. There's no "substantial or material" replication.
Why is this modded insightful?
Is it "stolen work" to read a book and then recite it, or paraphrase it, or create a story with the same themes? No. Those are new forms of work. The actual work isn't being recreated. Is software not the same as free speech? Can I not use phrases from other speeches in my speeches, and still have them be original work?
Who owns the copyright on the Klingon translation of Mein Kampf? Does Hitler retain those copyrights? No.
This "AI is all theft" argument is as tired as the old Microsoft lie that compatibility with their shitware was the same as copyright infringement. It's a tired argument. Retire it.
Look, I get it - a lot of the anti-AI folks don't take the time to inform themselves of how AI works, and it's generally scary, because it's threatening your identity as a coder. It's unfortunate, and not that different than the stablemaster being threatened by the automobile. That's the way things work, and there's no putting this cat back in the bag. You've got to adapt or die, just like the COBOL and FORTRAN developers of yesteryear. Or you could become a Maytag repairman.
Are we really going to trust something security-oriented by a guy who conceived of systemd? Instead of creating something which improves security and isolation, he created something renowned for its architectural and management complexity, privilege boundaries (or frequent lackthereof), attack surface, and the frequent consequences of concentrating system management in a large privileged software stack.
I'm reminded of the SSH/Pulse Audio privilege escalation through systemd some years back... due to their obstinately poor security design.
The callous part of me thinks that was the intention from the start: wash out the capable engineers who were competently producing and hire ethnic cohorts who played the game.
"A complex system that works is invariably found to have evolved from a simple system that worked." -- John Gall, _Systemantics_