pleroma.debian.social

@marcan
It means they have too much money and don't mind suing until you get tired if it and go 'fine, give me that paper', it run out of money, whichever comes first.

No, you should not give in. Yes, it does happen.
@developing_agent

@ariadne
This is not news?

@ska @reproducible_builds Note that reproducible builds doesn't necessarily give you bit-for-bit identical binaries, and that's also not necessary. What they give you is a toolkit to figure out which changes are normal results of different build dependencies, and which ones aren't. Things like diffoscope, e.g.

@ska @reproducible_builds If I build a version of some reproducibly-built software using a compromised tool chain and you built it using a non compromised one, and you shared the relevant bits of the output with me, then we know that one of us has a fishy compiler and the trusting trust issues are discovered.

That still leaves figuring out what happened, of course, but you don't need to be an expert to get this far. With your method of auditing binaries, you do.

@autism101 @actuallyautistic Some (also spectrum) people find emails extremely difficult to deal with properly and prefer getting a phone call... 🤷

Maybe better to discuss with the party involved and see what works for the both of you?

@fsfe why is only the audio of your "What is Free Software" videos translated, and not the visuals? That seems suboptimal. https://media.fsfe.org/w/p/9gYSyoEYggsqBExLWjRejL

@ska
Or, well, that the compromise will be exposed, I mean 😉
@reproducible_builds

@ska
Only if the reproducer uses the same compromised tool chain. The whole point of reproducible builds is that you can in fact use your own version of the tool chain and still get the same result.

Cc @reproducible_builds

@ska
Reproducible builds is what solves trusting trust. Handwritten binaries isn't; very few people have the skills required to validate those.
@dalias @daxtens @ariadne @dysfun

@ska
We have that, modulo the fact that to bootstrap, you first cross compile on a different platform.

Binaries are really just compiler output; writing and maintaining them by hand has no benefits and only downsides.

I mean, it's not the 1950s anymore.
@ariadne @dysfun @daxtens @dalias

@dancinyogi
With a spoon is gross!

@ska
So, I understand the need to say that everything is capitalism's fault, but I dunno, perhaps look at the language based on its merits? There's a lot to dislike but also a lot to like in rust, regardless of where it came from. 🙄
@ariadne @dysfun

@ska
Following that logic, since C was developed at AT&T, it must be complete shit.

I think you might be on to something here. /s
@ariadne @dysfun

@0x4d6165
You're required to build and test on unstable. You're not required to run unstable though. Chroots exist, and there are tools to help you manage those and build packages in them, such as sbuild and pbuilder.
@Ganneff

And installing that seems to have fixed the issue! 🥳

@simevidas Eh, a "scroll this page up" swipe should never ever ever be confused with a "please refresh this page and lose all my context"? Seems rather obvious to me 🤷

@simevidas I would have liked it if it wasn't so broken. Sometimes, when scrolled way down and I try to scroll up a bit, that triggers it, causing me to lose where I was in the page... no thanks.

Today's complete waste of time yakshaving:

I want to switch on my home server with home-assistant.io
So I enable wake-on-lan in the system's BIOS
Which causes it to immediately power on after every "sudo poweroff"
Which I try to fix using "fwupdmgr"
Which, it turns out, requires UEFI boots, which I did not yet move the server to
Which I got to work for 99% using incomplete Internet guides
Which I could fix using a live image
At which point I find that there is no firmware update... 🙄