Anarchists don’t fight for a world with zero authority. They fight for a world that has justified authority. If you say, “well lots of things don’t require authority that people swear is necessary!” Yes, that’s why it’s an entire axiom and not a childish thought.
Learn what political ideologies even want before you attempt to insult them.
Yea OK they’re fucked. I really really doubt they’ll be able to claim the data is solely comprised of the open works saved within that database. The only way they’d be able to get away with it is if they’ve meticulously harvested the data such that they only ever retrieved the open works or public domain works.
Anything not in that list or otherwise made available solely via their nonprofit efforts is going to be ammo in the lawsuit. Ammo that will hit its target.
I think that would depend on how intentional the open port was.
If it’s something there and advertised, even if mentioned in one place in some archaic document, they’d probably be fine just for accessing it.
Though that would only absolve them of acquisition issues. If they’re using someone else’s work for profit, there is almost certainly enough room for the lawsuit.
Only a select few licenses even allow for open and unrestricted commercial use. Especially if the data itself is the licensed thing, since valuable data is far easier to convert than something like source code.
I mean… it’ll all come down to how they accessed the data. If they had a public portal and no EULA, they can push rocks. If the data wasn’t public or the ‘theives’ had to use non-standard channels, or otherwise violated an EULA, they’re likely screwed. Especially if they had to go through abnormal channels.
I know their data can be accessed publicly, but I’m pretty sure it’s under license. You cannot just use any old thing found in public… That’s the biggest reasons the AI models are technically theft: they weren’t licensed to commercially profit off of 99.99% of the things their LLMs are trained on, but the law and politicians are WAY behind the times. Commercial data they’d normally have to pay for is suddenly magically OK when laundered through an LLM…
Keep in mind data recovery vs drive size. Getting past ~16TB drives, it starts to become a question of whether the rest would be able to survive a restore of a failed drive if any are going to have remotely similar endurance. Obviously, the answer is going to be “yes” most of the time, but at a certain point, there are deminishing returns on the cost of the drives to where even a one to one price increase in the HDD per size might not be worth it all the same.
Kinda’ a moot point if you’re not going to raid them in any way for reliability, but worth a thought.
I’ve described this terribly, but Level1tech on YT talks about it sometimes in reviews.
I mean, that ‘could’ be a straight up wrong thing to do if some of the calls were expecting errors to be able to escape. Yea, it’d be super weird and I don’t know if .NET would marshall them anywhere, but in some systems, that sort of, “obvious” fix could break shit. Sure, it’d be something doing something weird and kinda’ dumb, but … don’t we see “weird and dumb” all the time??
It gets funner when it’s a value that actually is a complex number with an “imaginary” component, but gets represented by NaN because the real value doesn’t make sense by itself. In reality, imaginary components are extremely critical for some equations and are totally valid.
I wish I remembered my math well enough to have one off the top of my head, but I don’t use it often enough… IIRC, it’s even important for magnetics, let alone more complex physics, so it does come up in practice quite often. I think there’s even a fundamental part related to derivatives, but yea, don’t exercise math enough. Might be misremembering.
Wow, way to actually respond with a valid point. You are beyond pathetic.
me: “You shouldn’t trust police by default.”
you: “OH yeah?! Did these ones lie?”
me: “that’s not what I said.”
you: “you must be angry all the time.”
Projection is a terrible thing, and I’m sorry you’re too dumb or young to understand.
JS will be far more versatile if you learn it well. It’s in so many dang things.
The biggest annoyances about JS are some things that exist in Python, so you’ll already be familiar with loosely typed systems and mutatable objects (dictionaries/hashes or what ever Python calls 'em).
Other than that, it’s mostly that there are a million ways to get the same things done, even something like, “define a class with static and instance-bound functions and properties”. Older JS techniques only use scope and the prototype and look like a gross hack. Modern JS has actual class syntax.
It all stems from the constant enhancement of the language. Many, many nice features like proper class syntax and first class modules (no more third party module syntax) came in ES2015, and a sadly small number of front end devs to this day really know them well.
Many web dev tutorials use older style techniques just because they’ve been around ages. If you learn how the new features are mostly syntax sugar on old styles, you’ll be a JS pro in no time.
No they don’t automagically make every single person happier, but breaking up monotony, providing at least neutral distraction, and opening up the door to directly interesting activity all can have a huge impact on someones’ happiness. Even getting healthier with exercise does help … eventually, if you stick with it and don’t despise the activity.
Just because they’re not a silver bullet shouldn’t reflect too poorly on the general advice. Though it IS important to remember that many peoples’ sadness absolutely cannot be solved so simply, and giving basic advice for troubling problems can be down right insulting.
The point of general advice is not to make people happy, but to open the door to enjoyable experiences that can. Analyzing them as direct happiness is of course far, far too subjective. Analyzing them as direct sources of happiness kinda’… misses the entire point on why these activities are so commonly recommended.
Yup! I love TypeScript, and I love the flexibility of JavaScript. With all of the type templates and generics and other black magic TypeScript has, it’s pretty easy to even support the crazy stuff like mixins and contextual parameters (if I’m not speaking too loosely while avoiding proper terms!).
A lot of the crazy stuff won’t optimize, but at least it goes to show how it’s not really tying JavaScript’s hands even when requiring TS everywhere.
You need to remember that a lot of those best practices are to cover for the performance issues from misusing loosely typed variables.
The JavaScript engine can compile clean, type-safe code down to be almost as fast as properly compiled code. When you use various features like the loose equals or various object mutations and the like, the engine cannot optimize it, leaving your code much, much slower.
The irony of you being upvoted when reality is the exact opposite…
Model collapse IS NOT from them consuming more human-based knowledge. It is from them consuming AI-generated content it thinks is human.
This has been all over the news. How can you utterly fail to understand a basic phenominon? Because you like using the AIs?
Stop lying about reality if you want them to continue giving you any truth.
IMO, the most important parts are to document the actual intent of the code. The contract of what is being documented. Sure, it’s only so useful in perfectly written code, but NO code is perfect, and few will come through later with full context already learned.
It makes it sooo mich easier to know what is intended behavior and what is an unchecked edge case or an unexpected problem. If it’s a complicated thing with a lot of fallout, good documentation can save hours of manually lining up consequences and checking through them for sanity.
You might say, “but that’s indication of bad code!”. No. Not really. Consequences easily extend past immediate code doing things as trivial as saving data to the database without filtering, or having a publicly available service. Even perfectly coded things come up with vulnerabilities all the time due to underlying security issues. It’s always great to have an immediate confirmation of what’s supposed to happen whether it’s immediate code or some library with a new quirk in a new version.