JRepin

cross-posted from: https://lemmy.world/post/21367513

Johannesburg, South Africa – While South African legal researchers were in an undisclosed location last week, racing against time to finalise hundreds of pages of evidence proving Israel’s intent to commit genocide in Gaza, in Israel, leaders gathering near the Gaza border were calling for the besieged and bombarded Strip to be emptied of Palestinians.

During the “preparing to settle Gaza” conference, held at a restricted military zone in Be’eri last Monday, Israeli Security Minister Itamar Ben-Gvir was recorded calling for the “migration” of Gaza’s current inhabitants, and the possibility of future Israeli settlement expansion there – something considered illegal under international law.

“[We will] tell them, ‘we are giving you the chance, leave from here to other countries’,” Ben-Gvir said, while Israeli forces continued their more than yearlong bombardment of Gaza. “The Land of Israel is ours.”

South African diplomats assert that statements like these offer undeniable evidence of Israel’s genocidal intent – something they must prove before the International Court of Justice (ICJ) in an ongoing case.

“The problem we have is that we have too much evidence,” Ambassador Vusimuzi Madonsela, South Africa’s representative to The Hague, explained to Al Jazeera.

cross-posted from: https://lemmy.ca/post/31843906

Oxfam's research found that the world's fifty richest billionaires produce on average more carbon emissions in under three hours than the average British person does in their entire lifetime. On average, they take 184 private jet flights in a single year, spending 425 hours in the air. This produced as much carbon as the average person in the world would in 300 years. Their luxury yachts emitted as much carbon as the average person would in 860 years.

cross-posted from: https://lemmy.ml/post/21873892

The Open Source Initiative (OSI) released the RC1 (“Release Candidate 1” meaning: This thing is basically done and will be released as such unless something catastrophic happens) of the “Open Source AI Definition“.

Some people might wonder why that matters. Some people come up with a bit of writing on AI, what else is new? That’s basically LinkedIn’s whole existence currently. But the OSI has a very special role in the Open Source software ecosystem. Because Open Source isn’t just based on the fact whether you can see code but also about the License that code is covered under: You might get code that you can see but that you are not allowed to touch (think of the recent WinAmp release debate). The OSI basically took on the role of defining which of the different licenses that were being used all over the place actually are “Open Source” and which come with restrictions that undermine the idea.

This is very important: Picking a license is a political act with strong consequences. It can allow or forbid different modes of interaction with an object or might put certain requirements to the use.

The Open Source Initiative (OSI) released the RC1 (“Release Candidate 1” meaning: This thing is basically done and will be released as such unless something catastrophic happens) of the “Open Source AI Definition“.

Some people might wonder why that matters. Some people come up with a bit of writing on AI, what else is new? That’s basically LinkedIn’s whole existence currently. But the OSI has a very special role in the Open Source software ecosystem. Because Open Source isn’t just based on the fact whether you can see code but also about the License that code is covered under: You might get code that you can see but that you are not allowed to touch (think of the recent WinAmp release debate). The OSI basically took on the role of defining which of the different licenses that were being used all over the place actually are “Open Source” and which come with restrictions that undermine the idea.

This is very important: Picking a license is a political act with strong consequences. It can allow or forbid different modes of interaction with an object or might put certain requirements to the use.

Welcome to a new issue of "This Week in KDE Apps"! Every week we cover as much as possible of what's happening in the world of KDE apps.

This week's changes and improvements cover a wide range of applications, from audio apps (including the classic Amarok, which is making a comeback) to Kate getting improvements to its integrated Git features.

In between, you have everything from new functionalities for note-taking utilities and media players, to upgrades in financial software and mobile apps.

cross-posted from: https://lemmy.kde.social/post/2184126

cross-posted from: https://floss.social/users/akademy/statuses/113344786509327188

Do you want to host Akademy 2025? Help organize an unforgettable event with the KDE Community and plan #Akademy2025!

Gather your team of Free Software enthusiasts and make it happen. Learn more at https://akademy.kde.org/news/2024-10_akademy-2025-call-for-hosts/

@[email protected]

Safety Profiles were introduced in 2015 with the promise to detect all lifetime safety defects in existing C++ code. It was a bold claim. But after a decade of effort, Profiles failed to produce a specification, reliable implementation or any tangible benefit for C++ safety. The cause of this failure involves a number of mistaken premises at the core of its design:

1. “Zero annotation is required by default, because existing C++ source code already contains sufficient information”
2. “We should not require a safe function annotation”
3. “Do not add a feature that requires viral annotation”
4. “Do not add a feature that requires heavy annotation”

The parameters of the problem make success impossible. This paper examines the contradictions in these premises, explains why the design didn’t improve safety in the past and why it won’t improve safety in the future.

KDE developers continued fixing bugs and making UI improvements this week. You’ll notice a good many of them are about screens somehow! Ah, screens, the magical windows to our computers. They are amazing… and they suck. So many graphics driver bugs and hardware quirks to work around, so many edge cases to handle… and so that was a large part of what KDE developers spent doing for you, dear reader! Because getting all this screen stuff right has a massive impact on quality. And of course there was a lot of other work too!

Does the C++ design follow the zero-overhead principle? Should it? I think it should, even if that principle isn’t trivial to define precisely. Some of you (for some definition of “you”) seem not to. We– WG21 as an organization – haven’t taken it seriously enough to make it a requirement for acceptance of new features. I think that is a serious problem, but one that we (WG21) should be able to handle. This paper offers some examples.

The Steam Deck has revolutionized the gaming handheld market. With the Linux-based immutable SteamOS, Valve has fostered an active community developing mods and alternative systems for this platform. Other manufacturers distribute Windows-based mobile consoles. However, time and time again it has been shown that they lag behind Linux in terms of software support.

But how easy is it to bring a Linux distribution, say openSUSE, to the Steam Deck?

In this talk, a prototype based on openSUSE's open technologies and infrastructure will be presented, which is already (almost) fully functional on the Steam Deck and many other devices.