It’s much more complicated than this. Given that models have been shown to spit out verbatim copies of some training material, it can be argued that the weights do in fact encode the material, just in some obfuscated way. Additionally, it can be argued that the output of the model is a derivative copy of the original work regardless of whether the original work can be “found inside” the model weights, just by the nature of the process. As of now, there is no precedent that I know of on whether this constitutes redistribution of copyrighted material.

How many months should he have waited for an authoritative response?

Well, Marcan should wait as long as feels right to him. As I said previously, I’m pretty sure he was already pissed off about previous R4L issues and he didn’t quit because of this alone. I want to be clear that I’m commenting solely on the expectation of a swifter response from leadership in the original email thread and not on Marcan’s decision to step down, which I can’t be the judge of.

So, I expect people in places of power to take their time when they respond publicly to issues like this, for various reasons. Eg:

• they might try to resolve things in private first (seems to be the case)
• they might want to discuss with their peers to double check their decision making and to take collective action, this is especially true if the CoC committee gets involved
• they might want to chime in when people have calmed down and they expect to be able to have meaningful conversations with them

At the very least, I would have waited to see what happens with the patches if I were in his position. The review process, which kept going in the meantime, essentially sets a timer for a decision to be made. In the end, Hellwig’s objections would either be acknowledged as blocking or they would be ignored. In any case there would have been a clear stance from the project’s leadership. It makes sense to me to wait for this inevitable outcome before making a committal decision such as stepping down.

Cristoph Hellwig’s initial message was on 2025-01-08. Marcan’s stepping down was on 2025-02-07. So no, it’s not several months; it’s barely one month. Getting in fights in mailing lists and making social media posts is not everyone’s first reaction and it is arguably not the best reaction, especially for people in places of power. It is silly for Marcan to demand everybody’s reaction to be as loud and as quick as his own.

It was very clear that the reaction was going to be no reaction.

Well, it turns out that the reaction was pretty clear not “no reaction”. That’s the reason this thread we’re talking in exists. Marcan was objectively wrong if he assumed Hellwig’s comments and nack would be accepted. Instead, Hellwig was explicitly called out for having no say on the matter and for producing “garbage arguments”.

Marcan is not the submitter. Unless I’ve missed something, the submitter is still working on the patch.

Marcan was probably fed up and was looking for a reason leave. If that’s not the case, then it’s silly for him to just quit mid-discussion, before it’s even become apparent what the reaction to Cristoph Hellwig’s behavior would be and whether his reply would even be taken into account during the review process.

Arch doesn’t require you to “read through all changelogs”. It only requires that you check the news. News posts are rare, their text is short, and not all news posts are about you needing to do something to upgrade the system. Additionally, pacman wrappers like paru check the news automatically and print them to the terminal before upgrading the system. So it’s not like you have to even remember it and open a browser to do it.

Arch is entirely about “move fast and break stuff”.

No, it’s not. None of the things that make Arch hard for newbies have to do anything with the bleeding edge aspect of Arch. Arch does not assume your use case and will leave it up to you to do stuff like edit the default configuration and enable a service. In case of errors or potential breakage you get an error or a warning and you deal with it as you see fit. These design choices have nothing to do with “moving fast”. It’s all about simplicity and a diy approach to setting up a system.

Agreed. A few year back the devs looking for quick fixes would go over to StackOverflow and just copy answers without reading explanations. This caused the same type of problems that OP is talking about. That said, the ease of AI might be making things even worse.

Getting the entire world to switch to something better would be quite the undertaking.

But that’s probably not necessary. You could install something on your phone that does phone number lookup and then just dials the number as normal. The service doesn’t need to be built into the old phone networks this way.

The latter is I think aiming for Linux ABI compatibility.

I had never hard of Asterinas, but this sounds like a the best approach to me. I believe alternative OS’s need to act as (near) drop-in replacements if they want to be used as daily drivers. ABI-incompatible alternatives might be fine for narrower use cases, but most people wouldn’t even try out a desktop OS that doesn’t support most of the hardware and software they already use.

I’m not sure why they feel it’s Linus’ responsibility to make Rust happen in the kernel.

That’s not what’s being said here, as far as I can tell. Linus is not expected to somehow “make Rust happen”. But as a leader, he is expected to call out maintainers who block the R4L project and harass its members just because they feel like it. Christoph Hellwig’s behavior should not be allowed.

I’m not saying Marcan is necessarily correct, to be clear. It might well be that Linus chose to handle the issue in a quieter way. We can’t know whether Linus was planning on some kind of action that didn’t involve him jumping into the middle of the mailing list fight, eg contacting Christoph Hellwig privately. I’m merely pointing out that maybe you misunderstood what Marcan is saying.

Or fork it and make a Rust Linux with blackjack and hookers, and boy, will everyone left behind feel silly that they didn’t jump on the bandwagon.

That’s what they’re doing. But if you read the entire post carefully, he explains why maintaining a fork without eventually upstreaming it is problematic. And it’s not like they’re forcing their dream on the linux project, because the discussions have already been had and rust has officially been accepted into the kernel. So in the wider context, this is about individual maintainers causing friction against an agreed-upon project they don’t like.

As far as I know, the apps are not intercepting the text messages for passcodes. The messages have a specific format and a hash to indicate which app they are targeting. It is up to the messages app to read the message and to forward the code. This design should not need to give the apps any access to your messages.

EDIT: Basically the immunity system doesn’t work like a muscle.

I think the immune system can be likened to a muscle if someone really wants to go with that metaphor, but only if you consider vaccines to be the gym and getting sick is uncontrollable and dangerous physical exertion. So, wanting to develop natural immunity is like wanting to get into street fights to build arm strength. It might kinda work, but you’ll also be in a lot of unnecessary danger.

Your encryption key can be stored encrypted in the cloud. This isn’t a fundamentally bad thing, but they should allow better protection than the short pins they allowed last time I checked.

Do you have access to Signal servers to verify your claims by any chance?

That’s not how it works. The signal protocol is designed in a way that the server can’t have access to your message contents if the client encrypts them properly. You’re supposed to assume the server might be compromised at any time. The parts you actually need to verify for safe communication are:

• the code running on your device
• the public key of your intended recipient

Yeah, that section is bad.

For one, it’s has classic vibe “if you want to keep the nazis out, you’re the one who’s exclusionary”.

But also, how is refusing to engage on a platform “shutting out a significant portion of [the] community”? That sounds backwards to me. Blocking people from engaging with Debian on its own platforms would be shutting them out. The implication in the article is that Debian is obligated to be unconditionally present on every social platform its users might be on.

Vaxrys literally arguing that Hitler should be welcome in communities as long as pushes his goal of gassing of people outside the discord server, but “SJWs” are the real bigots ruining communities

Comparing pregnant women who drink to men in prison as equally violent individuals?

Straight up adding pregnant women who smoke to pregnant women who drink alcohol to women who get late stage abortions with no concern that an individual might belong to more than one group?

Removing fathers who drank before conception from the equation entirely with the justification that an article called it less harmful, but clearly not harmless, which is the opposite of what he did when he put number of drinkers and convicted criminals in the same equation.

Go there & argue with guy if you are capable of showing a more accurate math

I’m not going to argue with that dipshit because it’s total waste of time. And so is arguing with you. I only commented for the benefit of other users who might scroll by without noticing the absolutely ridiculous evidence you cited, and get trapped into taking your position at face value.

Bro, no way you’re not a troll. I clicked on the 2nd link to see what the source is. It’s a guy using copilot to calculate percentage of women smoking and drinking during pregnancy, as well as late abortions, then does completely arbitrary math to conclude that women are more violent. If I wrote a parody of a person abusing stats to prove stupid points I would never have managed to make it as ridiculous as this.

Most of Proton code is Wine. So basically if you have Wine in your system, library dependencies are not an issue anymore, apart from DLLs that some games require

If I have wine on my system and try to run steam-managed proton without any sort of runtime or container, then I’m running proton on different versions of libraries than the ones it was compiled for and tested on. Proton also has additional components which might mean additional dependencies, so your statement is false to begin with.

Why are they doing a fork instead of contributing?

The fork is open source. As far as I know, some contributions do get merged into wine. Valve is also funding work from Collabora which is contributed directly into wine. They cannot contribute the entirety of proton to wine because wine does not want all their contributions. This is a very common situation to arise when someone wants to use an open source project but their goals don’t align.

But I expect it will be easier to push back on using containerization in Proton, than making Valve allow us such control

Valve is never going to rip out a solution that is working great for them and risk causing issues for customers for no good reason. Thinking that Valve are more likely to remove containerization than they are to allow you to modify the container is, frankly, delusional. It’s also completely irrelevant, as I’ve already said. If Valve wants to “fuck us up” then they’re going to do it. Steam is a proprietary piece of software that supports DRM for all your (also proprietary) games, which are stored on the cloud. You have no control over your games, but containers have nothing to do with it. And if they did, and Valve really wanted to pull a trick on us, asking them to remove the containers would make even less sense…

The issue is that even if you choose a hosting service outside the US, they might choose to block your content anyway in order to comply with US regulations and avoid legal trouble.