pleroma.debian.social

@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... 🙄

@lina
If you depend on X then probably not, either. X is no longer bug compatible with X of 20 years ago. In general that's a good thing, but not if you're trying to run old binaries.
@jmtd @trix

@760ceb3b9c0ba4872cadf3ce35a7a4
@mirabilos

So true. I used to always find it difficult to recognize the difference between "this is easy, doesn't need a blog post" and "this is genuinely interesting, people will learn from it". I have learned since they it doesn't matter, there will always be someone who hasn't yet learned the something you care about and who will be grateful that you spent some time writing things down...

@highvoltage
Where are you doing that? I've been wanting to learn isiXhosa since I've moved here, just never got around to it...

@dermoth
I am aware of that, but to see that there are two power states, especially at the lower level, where the frequency is exactly the same, was something I found quite surprising.

@marcan confirmed that it wasn't that, so, 🤷

@marcan
Oh, right. That makes sense, thanks.

@marcan
Why do states 1 and 2 on cluster 0 have the same frequency? Does state 1 perhaps save power in other, less obvious, ways?

@liw
Here's hoping that this one was NOT prompted by some API that did not follow this very obvious rule...

@mjg59
That blog post reminded me of the time I skip-upgraded Branden Robinson's m68k Mac which is a terrible idea for very similar reasons, and everything suddenly started failing because libc was upgraded before bash and now bash didn't work anymore and most postints require bash, not to mention init scripts.

That was a pretty fun ride, too. And no, I should not have done that either.

@foone
Docker on dos?
@shac