I'm not a particular fan of XML, even if it's functional enough to get the job done.

Of course you have to find a dictator that is ready to invest all the time and energy to care for a project over a prolonged time and is actually capable of doing so while avoiding to alienate the user base. That's a pretty tall order.

The more interesting question would be, if the bug bounty is enough to keep legitimate researchers engaged to investigate and document the threats. But..

The bug bounty itself is only a drop in the bucket for security companies, as it's a, unsteady and b, not enough to cover even trivial research environment cost.

Pratcially it's a nice monetary and reputation bonus (for having the name associated with the detection) in addition to the regular bussiness of providing baseline security intelligence, solutions and services to enterprises, which is what earns the regular paycheck.

Living from quests and bonties is more the realm of fantasy.

Bomb findings during construction is nothing especially rare in these countries.

ps. And even modern buildings suffer from this, like the projects where the requirements change all the time. Like Irelands new children's hospital, that should have cost just a couple of million Euros and balooned to billions. Construction projects are somemites done exactly like software development projects with all the fallout that comes with it. Same story with the airport in Germany (BER).

As for file manager usability, I grew up with Norton commander and pretty much gave up on ever seeing power user addressed file manager. It's fine for simple office type stuff that I bother few times a month on my Linux system but that's basically it.

When I have any more elaborate needs I fall back to plain old terminal with something like git or maybe even midnight commander, because that's what's getting the job done.

What I find really sad is, that they have like a million bindings to every programming language there is (including one that they made up) and I have no idea how they want to maintain that codebase. The basic API still looks somewhat antiquated and disjointed, but now it's in JavaScript and Vala. So even the more OCD type developers that would accept the design language constraints are frustrated that it looks so sad under the hood.

But I mean, I get it. Building a consistent desktop environment with a clean design language is hard and especially expensive. I'm impressed by what GNOME actually manages to get done with the few resources that they have. Is it anywhere close to being consistent and complete. I don't think so.

But than again, I mostly just use the desktop environment to open Chrome and the terminal, so for me it's perfectly fine.

Not saying you have to be a sociable person. I'm a total introvert myself, but knowing a couple of insiders that act as multipliers for these kinds of jobs would sound like it could help you, especially if you have a proven track record.

Now if you throw larger context or more obscure interface expectations at it, it'll start to discard code and hallucinate.

I personally don't really mind that bit of capitalization that English does. German is much worse.

Not that I'd take the recycling percentage at face value, there are certainly challenges. But the overall system is fairly solid.

Thing is, when computers permeated society in the 90's, everything looked so simple and wondrous, few people did nefarious stuff and if so mostly for fun. Now during the 2000s computers matured in companies to a degree that they became fundamental infrastructure, and that's where complications start, as someone eventually wants to take advantage of that to make a profit without regards to the means. The Internet bringing the world closer together of course changed the playing field.

Now trust me, many companies would love to sing kumbaya and ignore the topic all together, but that's just a way of presenting oneself as a low hanging target, as many have painfully recognized. And that includes low skill and targeted attacks on all levels. That's why there is a security industry, because IT infrastructure became so fundamental to how we do business.

Now it's a part of everyday life, being a risk the same as other externalities, like market cycle, supply chain and a million other things. The main issue really is, that back in the day nobody cared all that much, so there are few people that got into this branch, and thus there is a constant shortage.

But generally, the kind of stuff like in the article is just one of many security threats both low and high skill that companies are facing and they need a sophisticated system/process to categorize and counteract them (both in terms of prevention and damage mitigation). Unless you manage to remove global inequality and the incentives to exploit affluent entities, this reality just is.

Now I know this sounds grim, but statistically we are currently way better off than just a few decades ago, much less centuries. Things get better. It's just in our human nature to bitch about it anyway. Just take a deep breather and enjoy your shipping free delivery of basically anything you could want at reasonable rates straight from the other side of the world while looking at the bleak news than in no way reflect statistical reality (like, nobody wants to hear how good things work compared to 20-50 years ago, that's boring).

I mean sure, you can nicely ask or try to shame people, but when did that ever do anything of note?

The researchers really just raise awareness on where things are going, but ultimately the solution will be to improve process and verify anything that has to do with money through specific internal company channels that are hard to forge - and anybody in a call like this that would not use them needs to automatically raise an alarm by procedure.

Python with it's C API basically gives you the keys to the kingdom on a machine code level. Modifying something that has an API to connect to essentially anything is not an easy proposition. Of course, it has the advantage that you can make Python faster by performance analysis and moving the expensive parts to optimized C code, if you have the resources.

So what I want to say is, that poor people have better things to worry about than EVs and sustainability, like getting through the day with food on their plate and maybe a roof over their head. While they will be the most impacted, they can afford to care about it the least.

Also, EVs right now just shift the problem around until we manage to produce electricity from renewable sources, which is still some way off, especially in the poor places that will drive the least efficient ICEs while they last.