I see, thanks, I didn’t know the details. I just had a faint recollection that they had switched from AppArmor to SELinux.

I see, I probably misunderstood what you were saying. Thanks. I’m seriously considering OpenSUSE myself, for both my workstations and home server.

I think OpenSUSE Tumbleweed has SELinux enabled now too. I’m not sure what you mean by all over the system, as I’m not that familiar with SELinux yet. I believe that Tumbleweed used to use AppArmor but recently switched to SELinux? I also believe that Leap (the stable version of OpenSUSE) still uses AppArmor.

Flathub not coming preconfigured

Huh, that’s odd. I’ve been test driving different Linux distros lately for my move away from Windows, and Tumbleweed was one of the ones I tried. KDE Discover in Tumbleweed had Flatpak options for software, and I’m pretty sure it was tied to Flathub and not a different repo like Fedora does. Maybe I’m misremembering? Or did you mean that it doesn’t have the Flathub application itself?

Added to my watchlist, thanks!

Absolutely! If you haven’t watched it yet, Dark Days is also harrowing, if not as much as The Act of Killing.

The WordPress company, as in the developers of WordPress itself.

Thanks for these. Will add them to my list.

I love documentaries. There are so many amazing ones and I regret that they don’t get as much attention as the biggest fiction films, even though I love those too.

Here are two documentaries that immediately spring to mind because they made a big impression on me:

Dark Days (2000)

The Act of Killing (2012)

If people can code better, faster, cheaper, safer (more secure) that will surely apply to open source as well.

I’m not European, but I understand that there’s an old European (German?) saying that basically goes: “If I had wheels, I’d be a trolley.” I understand that it’s been pretty well-established that AI coding tools routinely underperform compare to humans in terms of “better” and “safer”, which indirectly would also lead to it failing at “cheaper” too.

On top of that, there is another major issue with using AI for open-source code: copyright. First, you don’t know if the code that you’re adding through AI may be copying license-incompatible code verbatim. Because everyone has access to open-source code, it would be trivial for anyone to search and find copyright-infringing code to attack projects with. Second, the code that AI produces is also not-copyrightable, so that is another line of attack that this would make open-source projects vulnerable to. These could be used in combination as a one-two punch combination to knock out an open-source project.

I think that using AI-generated code in open-source projects is a uniquely ill-advised idea.

This is almost like a real-world Chewbacca defense?

Awesome, thank you @ROllerozxa@sopuli.xyz for those details and @Ephera@lemmy.ml for the tag!

That’s fair. But what they’ve said so far seems to strongly point at this being the reason.

Think about it. Anything you type into a browser is your intellectual property, you own the copyright to it, unless you’re copying someone else’s text. In order for Mozilla to pass what you type on to any website you’re visiting, they need to “copy” that text (i.e., from the keyboard to the network).

I think this is what they’re trying to address with their legalese. It’s a pity that it has to come to this, but that’s how the legal environment is these days. They can’t afford to make expensive mistakes. Perhaps they can keep improving and clarifying the language though.

That’s cool, thank you for telling the background!

Thanks!

No problem, thanks!

Thanks!

Thanks again!

No worries, I’ll check it out, thanks!