skilltheamps

joined 1 year ago
[–] [email protected] 12 points 6 months ago (1 children)

Well, doing none of the many chores to transform his pedo club into something socially acceptable, and instead killing his boredom by holding talks about a topic that has neither anything to do with church nor is he remotely qualified to say anything about, is on a whole other level of disrespect, isn't it?

[–] [email protected] 3 points 6 months ago

Nono, you are demanding in a not nice tone from a open source community to implement some bloat workaround to fix some you-specific-issue with commercial software. You know how free and open source software works? Either you contribute something positive, or you color yourself glad you get to use something so great completely for free and stay silent. Bark at that commercial vendor that doesn't use the money from licenses + selling your soul to build something half decent! This upcoming demand-culture around things that others kindly share with wanting nothing in return pisses me off. Especially when it's not even something about the project, but carrying over unrelated cruft, instead of directing the demand to the entitiy it would be justified against.

Just build a browser extension that does the conversion. Or a script that watches a folder where you drag it into as an intermediary, and then it converts it automatically. And then share it for free, because you are a kind person! You might find a handful of people that like it. And then watch some asshat writing you a demand that "stop converting to jpeg, forever stop that! I need bitmaps for my gameboy! Just give me a SETTING where I can chooose and a nice dialog where I can pick the freaking color palette!"

[–] [email protected] 33 points 6 months ago (2 children)

Research what happened to Upstart, Mir or Unity. It won't take long until snap becomes one of them. Somebody at canonical seems to desperately obsess over having something unique, either as a way to justify canonicals existance or even in the hopes of making the next big thing. Over all these years they never learned that whatever they do exclusively will always fall short of any other joint efforts in the linux world, because they always lack the technical advances, ability/will to push it for a prolonged time and/or the non-proprietary-ness. So instead of collaborating like every serious linux vendor, they're polluting their distro with half-assed, ever changing and unwanted experiments. They're even hijacking apt commands to push their stupid snap stuff against the users intent. With the shengians they're pulling Ubuntu cannot be relied on, and with that they're sabotaging their own success and drive away any commercial customers that generate revenue.

[–] [email protected] 4 points 6 months ago* (last edited 6 months ago)

This is the correct answer, every device you use a bitwarden-client regularly on automatically becomes a backup

[–] [email protected] 11 points 7 months ago* (last edited 7 months ago)

Also I think nobody so far weighed the energy consumption of e.g. using copilot against the environmental footprint of a human doing the legwork manually

[–] [email protected] 3 points 7 months ago (5 children)

Yes I know it, and sometimes use it for a little. But the vast majority of things it presents to complete to me feel rather unimportant. My leisure time isn't exactly plenty, and then I rather do other things I see more value in. Even surface type is mapped most of the time, and I don't take the effort to map surface quality because it is not used for anything. Maybe I'll make an App at some point that infers surface quality automatically while road biking from the acceleration sensor in the phone mounted to the handlebar...

[–] [email protected] 4 points 7 months ago (7 children)

At least for the more fundamental information like paths or trails this is true. I only really get to map stuff when in holidays abroad, because here you have to check a 100 times if something is mapped to find a handful of chances to contribute anything, which has a frustrating feel to it 😅

[–] [email protected] 1 points 7 months ago

Specifically the shitty IPU6 situation is on Intel, and is invariant to any laptop manufacturers. I also have a Thinkpad X1 with that issue. So for that the situation that one manufacturer would support it properly (i.e. upstream) and others don't can't exist, as soon as anybody puts it upstream it works for everybody. Thankfully there's some progress (search for libcamera) and in the not too distant future it should work ootb. For fingerprint readers it is a different story though, as there are many different ones, so that one is on Dell indeed

[–] [email protected] 5 points 7 months ago (1 children)

One possibility would be Huginn I guess https://github.com/huginn/huginn

[–] [email protected] 5 points 7 months ago (3 children)

You have this view because your hardware is from an era where fingerprint reader largely weren't a thing and webcams were connected via internal usb. The issue is not that the Linux kernel drops anything (between you and op, you're the one with the old hardware). The issue is, that fingerprint readers became a commodity without ever gaining universal driver support, and shengians like Intel pushing its stupid IPU6 webcam stuff without paving the way upstream beforehand

[–] [email protected] 14 points 7 months ago (1 children)

As far as I understand, in this case opaque binary test data was gradually added to the repository. Also the built binaries did not correspond 1:1 with the code in the repo due to some buildchain reasons. Stuff like this makes it difficult to spot deliberately placed bugs or backdors.

I think some measures can be:

  • establish reproducible builds in CI/CD pipelines
  • ban opaque data from the repository. I read some people expressing justification for this test-data being opaque, but that is nonsense. There's no reason why you couldn't compress+decompress a lengthy creative commons text, or for binary data encrypt that text with a public password, or use a sequence from a pseudo random number generator with a known seed, or a past compiled binary of this very software, or ... or ... or ...
  • establish technologies that make it hard to place integer overflows or deliberately miss array ends. That would make it a lot harder to plant a misbehavement in the code without it being so obvious that others note easily. Rust, Linters, Valgrind etc. would be useful things for that.

So I think from a technical perspective there are ways to at least give attackers a hard time when trying to place covert backdoors. The larger problem is likely who does the work, because scalability is just such a hard problem with open source. Ultimately I think we need to come together globally and bear this work with many shoulders. For example the "prossimo" project by the Internet Security Research Group (the organisation behind Let's Encrypt) is working on bringing memory safety to critical projects: https://www.memorysafety.org/ I also sincerely hope the german Sovereign Tech Fund ( https://www.sovereigntechfund.de/ ) takes this incident as a new angle to the outstanding work they're doing. And ultimately, we need many more such organisations and initiatives from both private companies as well as the public sector to protect the technology that runs our societies together.

view more: ‹ prev next ›