imagine caring about a meme template

I was going to comment this too

I love the intonation. 10/10

mike tyson is two pigeons

You’re not a developer.

shit, don’t tell my employer

HDR was always broken to me, desktop was under saturated and browser pages over saturated.

Let’s try to not mislead people here by pointing to some a/b testing thing that has nothing to do with policy changes and enforcement

The Nimbus migration is literally why it was kept behind telemetry for a couple days, that’s not a red-herring. You’re attributing malice to neglect - which is now fixed.

incidentally gatekeeping new features being A/B tested is hardly fucking anyone over. Let’s save the rage for things that matter.

no, it’s quite reasonable actually:

Nimbus was originally designed to be an A/B test platform and so it made sense at the time that if telemetry was disabled that Nimbus should be disabled because there if you need to collect data in order to do quantitative experimentation. However, as Nimbus has grown into more of a feature delivery platform, it no longer makes sense to gate everything behind having telemetry or even studies enabled.

not sure, but it’s probably just an interface to an embedded battery controller and this controller is the one actually determining how/when the battery must charge, so it doesn’t need constant input from the CPU.

right? I don’t watch TV because of all this crap. I don’t understand how some people have the patience, honestly.

ln -s /dev/null /dev/nul
ln -s /dev/nul /dev/shhhhh
ln -s /dev/shhhh /dev/shhhhh
ln -s /dev/shhh /dev/shhhh
ln -s /dev/shh /dev/shhh

kool

I’ve known Zed for almost a year now, but it still lacks a lot of what VS Code offers. Especially when it comes to customization.

> Welp, that precisely recreated it -- even identical shas! Looking at
> the b4 output, I do see a suspicious "39 commits" listed for some reason.

Well, that's the point where the user, in theory, goes "this is weird, why is
it 39 commits," and does Ctrl-C, but I'm happy to accept blame here -- we
should be more careful with this operation and bail out whenever we recognize
that something has gone wrong. To begin with, we'll output a listing of all
the commits that will be rewritten, just to make it more obvious when things
are about to go wrong.

> So, I assume the "git-filter-repo" invocation is what mangled it. I will
> try to dig into what b4 actually asked it to do in the morning...

Thanks for looking into this. Linus, this is accurate and I am 100% convinced
that there was no malicious intent. My apologies for being part of the mess
through the tooling.

I will reinstate Kees's account so he can resume his work.

-K

I change them all to bind mounts. Managed volumes is where data goes to die, if it’s not in my file tree I’ll forget it.

sir, this is a wendy’s

on second though: “ugh, light mode”

I want to convert all lossless files to lossy, preferably before uploading them

so it’s not exactly a mirror, right?

here’s an idea:

• A - the source containing lossless files
• B - the local storage of lossy files
• C - a remote mirror of B

With that, you can do:

• A -> B: a systemd service that makes this conversion.
• B -> C: git or syncthing to mirror and/or version control.

This uses more storage than you probably intended to (lossy files are also stored locally), but it’s a mirror.

Because that’s a release page. The first paragraph in the readme tells you what open webui is.

https://github.com/open-webui/open-webui

the best thing is when not even the author knows the correct order of running the cells; because of course it isn’t top-to-bottom.