Cloudflare’s dominance is a huge problem exactly for this reason. Having a single point of failure is a huge risk, and it’s surprising that governments don’t view this as being a matter of national security.
As a side note, and not to “well ackshully”, but Cloudflare isn’t a backbone provider. But your point still stands lol.
So he’s capable enough to add new islands and content, but not change a trigger on how to save. One button. Same logic…
Correct. The entire game state was not designed to be serialized. You can see this with how buggy multiplayer is. He could do saving mid-day, but I don’t think most players would want that over an entire new island worth of content, especially when the amount of work is comparable.
A buggy mod by someone who didn’t write it doesn’t mean it’s not possible.
I didn’t say it’s not possible. Anything’s possible when it’s your code. I said it would be hard to add now.
You can like a game and someone and still be able to be critical of a game design decision they make. Not everyone is good or bad. A hero or villain. No one is perfect.
This part, I don’t get. I maintained a mod with thousands of endorsements and over a hundred thousand unique downloads. I talked with modders even bigger than me regularly. Even the lead dev of SMAPI, who has some more insight into the codebase than anyone else in the modding community.
None of us succeeded in it.
At no point did I defend the game on its merits of being “good or bad”. I haven’t played it in years. All I did was explain that this is technically very difficult to do.
On the topic of dark patterns, many games have specific points where you can save. This is not unique to SDV. For example, some games only allow you to save at specific points to avoid save scumming and increase the difficulty.
What matters isn’t when you can save. It’s whether your inability to save at times is being exploited for their benefit.
It’s not a dark pattern. It’s a technical limitation.
Concerned Ape wrote that game with very limited programming experience. Having significantly modded the game in the past, the code is a mess, but indicative of someone who is learning to program still.
While I haven’t played SDV in a long time, there was a mod when I played that allowed you to save at any time. It was buggy as hell.
It’s an indie game made by one dude. He got some help from CF for multiplayer and porting, but that was about it.
At this rate, all indie games have dark patterns lol.
monitoring how they are used is good to identify if people are actually more productive with it
Unfortunately, many jobs skipped this step. The marketing on AI tools should be illegal.
Far too many CEOs are promised that their employees will do more with less, so of course they give their employees more to do and make them use AI, then fire employees because the remaining ones are supposed to be more productive.
Some are. Many aren’t.
Like your comparison, the issue is that it’s not the right tool for every job, nor is it the right tool for everyone. (Whether it’s the right tool for anyone is another question of course, but some people feel more productive with it at times, so I’ll just leave it at that.)
Anyway, I’m fortunate enough to be in a position where AI is only strongly encouraged, but not forced. My friend was not though. Then he used it because he had to, despite it being useless to him. Then he, a chunk of his management chain, and half his department were fired. Nobody was hired to replace them.
There are plenty of companies that track metrics on AI usage. Big names like Amazon come up of course, but even some small companies require employees to use it.
So to answer your question: a lot of people, regardless of if they want to.
And no, they can’t all quit and get a new job.
Their response seems to be arguing against a claim that AdGuard didn’t even make. AdGuard acknowledged the existence of CSAM and reported it to archive.today. What they brought into question was whether WAAD was a legitimate organization as opposed to something shady.
In their article, AdGuard published the registration address and the email of WAAD, as well as the names of the directors, and distributed confidential emails while openly defaming our actions, our structure, and the bailiff.
Publishing the public details of an organization, like its director and the email address, are not doxxing. Emails cannot be made confidential without an agreement on both sides, and French law, even if it does protect communications between French people, cannot extend beyond France.
Defamation also is a very strong claim to make here. I can’t speak for European law, nor am I a lawyer of course, but in the US, defamation usually needs to not only be harmful, but knowingly false. AdGuard doesn’t know who you are, nor have they made any false statements. The law they quoted also says “with an intent to harm” which is clearly not the case here, though they have shown reason to assume you have intent to harm archive.today.
AdGuard publicly declared that all reported URLs had been removed. Our technical checks show that part of this content is still accessible on Archive.today and its mirrors.
The fuck is a “technical check”? Maybe clear your cache? I don’t want to know what these URLs are, but I can guarantee they don’t start with https://adguard-dns.io/.
When you get a chance, might be good to take a break and process it all. The world will keep moving, and it won’t wait for you. But the world doesn’t move so fast that you can’t take a breather for a minute, then catch back up to it.
Afterwards? Well, like your mom said, it’s your posessions now. What you do with them is up to you. Whether they are nothing more than mementos, or whether you inherited billions, you get to choose how those posessions are used.
I’m no parent, but if I were, I’d want my child to use my posessions to their fullest, whether that’s making a positive change in their life, using them to achieve a dream, or even using them to further a cause they care deeply about. I’ve never met your dad, but I can’t imagine it being too different for him.
Rust currently isn’t as performant as optimized C code, and I highly doubt that even unsafe rust can beat hand optimized assembly — C can’t, anyways.
A bit tangential, but to answer this question, nothing beats the most optimized assembly code. At best, programming languages can only hope to match the most optimized assembly.
Rust does have macros for inlining assembly into your program, but it’s horribly unsafe and not super easy to work with.
Rewriting ffmpeg in Rust is not a solution here (like you’re saying).
The sheer scale of this across multiple sectors should put any fears that we’re not in a recession to rest.
Wow thanks. I feel so relieved now!
Seeing my own friends affected by both the layoffs and the shutdown (since their work is government funded), there’s no way the economy isn’t royally fucked.
Anyway, I’m no economist, so I won’t pretend like I can say what will happen, but it’s very clear something will happen, or we’re already in it (more likely).
Can’t wait to see what happens if/when AI’s hype dies too.
Also, when it comes to mounting radiators, all that matters at the end is where the air collects, and as long as a vertically mounted radiator has one end above the pump, then air will naturally collect there. Tube orientation matters, but not a whole lot. Tubes on the bottom usually means that air collects on the side of the radiator where it’s less likely to recirculate back into the pump, but mounting it the other way doesn’t usually cause issues because the air can still collect and what few bubbles make it to the pump aren’t significant enough to damage it.
TL;DR: the goal is to not run the pump dry, which should never happen as long as the pump isn’t at the top of your water loop (radiator below pump).
Eh the “radical left” is literally anyone opposed to fascism these days. “Left wing extremism” can’t be too far from that.
From what I’ve seen, the hard drive at least looks replaceable, so it should be possible to upgrade it I believe.
Wow genius response. Glad you actually addressed my comment.
ffmpeg devs can refuse the AI generated bugfixes for all we care.
This is a separate problem, but it’s still a problem. Many projects have seen a rise in slop PRs. curl is notorious for complaining about AI slop vulnerabilities and patch requests.
But I think we both agree that Google needs to be doing something more rather than putting the workload entirely on the ffmpeg devs.
Lemmy also benefits from not tracking total karma or whatever. Per-post or per-comment scores at most.
From my experience, Beehaw disabling downvotes furthers this even more. This means that people can either voice their disagreement, report the post/comment for violating the rules, or ignore it and move on. There’s no way to anonymously “punish” a post you disagree with (unless it violates the rules), and not as much incentive to stick to the echo chamber either.
Well if you categorize everything that isn’t alt-right as hard left, it’s pretty believable. I mean hell, have you seen Wikipedia? Clearly hard left.
I don’t understand how a bug is supposed to know whether it’s triggered inside or outside of a google service.
Who found the bug, and what triggered it? Does it affect all users, or does it only affect one specific service that uses it in one specific way due to a weird, obscure set of preconditions or extraordinarily uncommon environment configuration?
Most security vulnerabilities in projects this heavily used are hyper obscure.
If the bug is manifestly present in ffmpeg and it’s discovered at google, what are you saying is supposed to happen?
e) Report it with the usual 90 day disclosure rule, then fix the bug, or at least reduce the burden as much as possible on those who do need to fix it.
Google is the one with the vulnerable service. ffmpeg itself is a tool, but the vast majority of end users don’t use it directly, therefore the ffmpeg devs are not the ones directly (or possibly at all) affected by the bug.
There are a bunch of Rust zealots busily rewriting GNU Coreutils which in practice have been quite reliable and not that badly in need of rewriting. Maybe the zealots should turn their attention to ffmpeg (a bug minefield of long renown) instead.
This is weirdly offtopic, a gross misrepresentation of what they are doing, and horribly dismissive of the fact that every single person being discussed who is doing the real work is not being paid support fees by Google. Do not dictate what they should do with their time until you enter a contract with them. Until that point, what they do is none of your business.
Alternatively (or in addition), some effort should go into sandboxing ffmpeg so its bugs can be contained.
And who will do this effort?
If you’re seeing downvotes, it’s unlikely anyone on other instances can see them as well. Not sure how they federate, but Beehaw has them disabled, so they’re not on Beehaw.
Bug reports that apply only to Google’s services or which surface only because of them are bugs Google needs to fix. They can and do submit bug reports all they want. Nobody is obligated to fix them.
The other part of this is, of course, disclosure. Google’s disclosure of these bugs discredits ffmpeg developers and puts the blame on them if they fail to fix the vulnerabilities. They can acknowledge the project as being a volunteer, hobby project created by others if they want, and they can treat it like that. But if they’re doing that, they should not be putting responsibilities on them.
If Google wants to use ffmpeg, they can. But a bug in ffmpeg that affects Google’s services is a bug in Google’s service. It is not the responsibility of unpaid volunteers to maintain their services for them.
s/OpenBSD/TempleOS