Just European governments committing actual terrorism. Nothing to see here, move along please. (This is just the shit we learn about and I wished everyone who ever participates in any such scheme died an agonizing immediate death before they can execute it)

I am “slightly” worried that there’s only a single option left. That’s only 1 organization’s corruption removed from total loss of control over browsing privacy :/

Absolutely agreed.

Keep yourself cool to worsen the problem? sounds like a great plan! /s

AC users anywhere in the world where temperatures / humidity are in a range that humans can adapt to are morons.

Rather: only buy phones with explicit vendor guarantee that the bootloader can be unlocked / comes unlocked.

1. if each of those contributors to wrecking our planet points to the other causes as a justification to not limit their own damage, we’re fucked
2. it’s not AI. It’s large language models. Glorified statistical text prediction without any originality. It just appears to some naive humans as original because it regurgitates ideas to them that other people have had but they just hadn’t heard before
3. despite the misnaming, I agree that there’s a real concern that it makes the majority of users even more stupid than mankind on average already is :/

that’s gonna be mighty useful when we’ve destroyed the planet. Also, you are not working with AI. You are working with a LLM.

For the keys - do you mean something like

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 00000000 where 00000000 is replaced with the fingerprint of the key you want to fetch?

I do agree - the apt-key command is kinda dangerous because it imports keys that will be generally trusted, IIRC. So a similar command to fetch a key by fingerprint for it to be available to choose as signing keys for repositories that we configure for a single application (suite) would be nice.

I always disliked that signing keys are available for download from the same websites that have the repository. What’s the point in that? If someone can inject malicious code in the repository, they sure as hell can generate a matching signing key & sign the code with that.

Hence I always verify signing keys / fingerprints against somewhat trustworthy third parties.

What we really need though is a crowdsourced, reputation-based code review system. Where open source code is stored in git-like versioning history, and has clear documentations for each function what it should and should not do. And a reviewer can pick as little as an individual function and review the code to confirm (or refute) that the function

1. does exactly what the interface documentation claims it does
2. does nothing else
3. performs input validation (range checks etc)
4. is well-written (in terms of performance)

Then, your reputation score would increase according to other users concurring with your assessment (or decrease if people disagree), and your reputation can be used as a weighting factor in contributing to the “review thoroughness” of a code module that you reviewed. E.g.: a user with a reputation of 0.5 confirms that a module does exactly what it claims to do: Module gets review count +1, module gets new total score of +0.5, new total weight of ( combined previous weights + 0.5 ) and the average review score is “reviews total score” / “total weight”.

Something like that. And if you have a reputation of “0.9”, the review count goes +1, total score +0.9, total weight +0.9 (so the average score stays between 0 and 1).

Independent of the user reputation, the user’s review conclusion is stored as “1” (= performs as claimed) or “0” (= does not perform as claimed) for this module.

Reputation of reviewers could be calculated as the sum of all their individual review scores (at the time the reputation is needed), where the score they get is 1 minus the absolute difference between the average review score of a reviewed module and their own review conclusion.

E.g. User A concludes: module does what it claims to do: User A assessment is 1 (score for the module) User B concludes: module does NOT what it claims to do: User B assessment is 0 (score)

Module score is 0.8 (most reviewers agreed that it does what it claims to do)

User A reputation gained from their review of this module is 1 - abs( 1 - 0.8 ) = 0.8 User B reputation gained from their review of this module is 1 - abs( 0 - 0.8 ) = 0.2

If both users have previously gained a reputation of 1.0 from 10 reviews (where everyone agreed on the same assessment, thus full scores):

User A new reputation: ( 1 * 10 + 0.8 ) / 11 = 0.982 User B new reputation: ( 1 * 10 + 0.2 ) / 11 = 0.927

The basic idea being that all modules in the decentralized review database would have a review count which everyone could filter by, and find the least-reviewed modules (presumably weakest links) to focus their attention on.

If technically feasible, a decentralized database should prevent any given entity (secret services, botfarms) to falsify the overall review picture too much. I am not sure this can be accomplished - especially with the sophistication of the climate-destroying large language model technology. :/

Removed by mod

word. from the very first time I ever saw a pic of that mug, that fucker gives me the absolute creeps.

Am Meisten erstaunt mich, dass so eine Aussage von jemand aus der CSU kommt…

Aber hey, eine Nachricht zum Weiterleiten an all die AfD-Nachplapperer

Makefiles/automake isn’t a reasonable expectation these days, with a plethora of languages and build toolchains, but good, clear instructions are definitely something to include.

As for the Makefiles, I meant that for whatever build toolchain the project uses - because the rules to build a project are an essential part of the project, linking the source code into a working library or executable. Whether it is cmake, or gnu make, or whatever else there is - that’s not so important as long as those build toolchains are available cross platforms.

I think what is really missing in the open source world is a distribution-agnostic standard how to describe application dependencies so that package maintainers can auto-generate distro-packages with the distribution-specific dependencies based on that “dependencies” file.

Similar to debian dependencies Depends: libstdc++6 (>= 10.2.1) but in a way that identifies code modules, not packages, so that distributions that package software together differently will still be able to identy findPackageFor( dependency )

I would really like to add this kind of info to my projects and have a tool that can auto-build a repo-package from those.

I’m sad about the direction of windows, but it generally works pretty well for how it’s designed

That is a bold claim. And absolutely wrong for many configurations.

Edit didn’t mean to imply Linux is easier than Windows to learn in general.

It is though. People just neglect that in today’s world, no one “learns” Windows from scratch.

Learning to do anything from scratch is easier on most Linux distros than on Windows. The tools are better and the documentation is light years ahead. Windows is a steaming pile of horseshit in comparison. But once you’ve made yourself a cozy nest in the middle of said pile, getting to the comfy whirlpool hot tub that is linux requires you to scale over the walls of horseshit surrounding your nest. And that is what makes people claim “but Linux hard, muh duh!”

kate editor would like to have a word… They did my lady kate dirty with the latest updates :( The top level File menu was so much better and now I don’t know where to find the configuration to get that back, and have on my work computer a stupid single button in the top right corner which opens the “menu bar”, except vertically…

Now Debian insists we add the GPG keys manually. Like cavemen.)

Erm. Would you rather have debian auto-trust a bunch of third party people? It’s up to the user to decide whose keys they want on their system and whose packages they would accept if signed by what key.

While I agree that developers (like myself) are not necessarily experts at packaging stuff, to conclude that it’s fine that a developer provides a flatpak is promoting shitty software. Whether a software should run in a jail, or within user space is a decision that - for most use cases - should be made by the user.

There is absolutely no reason not to provide software as a tar.gz source code archive with a proper makefile & documentation of dependencies - or automake configuration if that’s preferred.

From that kind of delivery, any package maintainer can easily build a distro-package.

You had some valid points as well - I enjoy a good constructive exchange, thank you! :)

came to point out the Hitler likeness…

I suppose there are problems in many teams, yes - the majority of humanity is just not mature enough to treat each other professionally :/

Still - 4 out of the 5 founding companies being pure evil does not fill me with confidence :/