In that case, you may get some mileage as well out of Old Reddit Redirect. It will automatically force all Reddit links to open in old Reddit for you.

OldLander

It’s only available for Firefox.

I think I’d keep using the slow cooker in that situation, because 100% of slow cooker time is parallelized with work time. Even if the pressure cooker is fast, it can’t compete with zero.

Though, having the pressure cooker available for when I’m a brainless oaf who didn’t start the slow cooker in the morning sounds like a great fallback option.

Not on low, no. I make no promises about high.

I think slowcookers in general avoid reaching boiling temps because the whole point is being able to leave them run unattended for hours, which you can’t safely do if it’s boiling off.

My best guess for a potential solution if you’re gung-ho to try and find a way is to pour the juice into a saucepan and bring it to a boil separately, let it cool, then prepare as directed. But I have no idea what that will do to this compound she is allergic to, whether boiling water is sufficiently hot to do that, how long you need to hold it there to make it safe, or what else boiling it will do to the flavor. I also have no idea what the nature of the allergic reaction is and how much risk it puts her in. So for lawyer reasons I can’t in good faith reccommend you make this for her at all.

If you have actual medical advice telling you what temp denatures the bad compound and how long it needs to be held there to make it safe, try leaving water sit in your slow cooker with an accurate thermometer and see for yourself if it gets to that temp. If you can confirm that, then it might be safe.

Experiment with it at your own risk with her consent, I guess.

+1 for Reddit API exodus.

Lemmy was sold to me as a Reddit replacement. And it is, superficially. I knew it wasn’t going to be drop-in going in. But the longer I use it the more I think it’s not really quite like Reddit, and never will be. And that’s fine. Lemmy is its own character and I like it for what it is.

I still use Reddit. Lemmy doesn’t scratch all the itches for me. But only old.reddit on the desktop and on mobile with a UI de-shittifying extension. I’m amazed they still offer it at all. Once that’s cut off, something I’ve been bracing myself for for years, I’ll consider the UX enshittification to have fully completed and I’ll truly bail. I simply refuse to use their gentrified UI. And I’m tired as it is having to slap on compatibility layers just to keep their less terrible alternative on life support; I’m not going to do the same thing to make their mainstream UI somewhat more palatable.

I’d rather have multiple monitors so I have the more intuituve window snapping. But to each their own.

Zero-effort french dip:

1. Buy an arm roast at the grocery store the night before, sleep.
2. Wake up, dump in arm roast, a can of french onion soup, top off with water or beef stock
3. Cover and set to Low, then go to work for the day
4. Return home in the evening, shred meat with some forks, serve on buns with cheese of your choice

It’s not glamorous, and you could do a lot better with more intelligent ingredient choice and more prep (searing the roast first, adding veg, doing the broth from scratch, etc). But the result-to-effort ratio of the bare minimum is unmatched if you’re ever in a “fuck it, guyslop night” kinda mood.

For slightly more effort, I sometimes make a very simple hot apple cider recipe. That’s non-alcoholic for all the non-Americans, though you can always spike it with your spirit of choice:

For every 8 cups (~1.8L, 2L is probably fine) of apple juice from concentrate, add:

• 1 tsp whole cloves
• 1 tsp whole allspice
• 2 cinnamon sticks
• 1/3 cup packed (~70g) light brown sugar
• 1 large orange, sliced

Cook on low for 2 hours, fish out solids, serve hot.

If you can specifically find “honeycrisp” apple cider at the grocery store to use as your base, it’s even better. I can sometimes find it seasonally at Walmart.

Well, I also tend to consider ultrawide monitors a mistake in their own right. Why would you want a 49" wide literally anything if it’s not some kind of immersive media experience where menus are irrelevant anyway?

Of course, if that is in fact exactly what you bought it for, I have no complaints. Even if I disagree with having one for other purposes, that’s still no reason for the OS to punish you for having one when you try to use it that way when that problem is completely avoidable.

I’ve personally always loathed the global menu bar paradigm of macOS. Having a menu bar that’s wholly detatched from the currently open window that is context-aware based on which window has focus always felt like an irritating speed bump to me. My mind feels like the OS itself is hiding things from me by only allowing me to see a single app’s menu bar at a time.

But then again, I have no objective qualms with it. I’m sure I could adapt to it. When have I realistically needed to see more than one menu bar at once? I can’t name a time. I’m probbably just pearl-clutching at the perceived arresting of my agency to do things when in fact I’m losing effectively nothing.

At any rate, we agree it’s a sure sight better than the shitshow that is GTK. “Hm? Window decorators and shit? Nahhh, those are your problem. Go roll your own.” For the flagship windowing toolkit of the GNOME Project, the DE I’d consider the closest in philosophy to what macOS has going on, that was a rather strange position to take.

I do honestly miss the level of artistic and aesthetic polish that a multi-billion dollar corporation can afford to field that no Linux distro really can.

Linux as a rule is and always has been generally quite “Guys Live In Apartments Like This”. Often utilitarian to a fault. UX design by backend devs, because actual frontend devs cost money. No one wants to pay the “beauty tax” for software. DEs like KDE and Gnome are trying very hard and have made great strides, but it’s very slow progress.

And I imagine this comment will be a magnet for power user types who will flock to my post and retort something along the lines of, “All that stuff is bloat/a usability nightmare/clutter/gets in my way/comes at the cost of features”, blah, blah, blah, waaahhhh boo hiss… Yes, it’s all true, and yes, I understand. But Linux and the free software it surrounds itself with tends to be crusty, clunky, and god-awful ugly, and I’d be lying if I said that didn’t frustrate me a bit now and again. Does it bother me to the point that I don’t want to use it? Fuck no. Windows isn’t worth the bullshit. But they do at least know how to make an OS slick and beautiful, when it works, anyway.

I’m sure people will also cherry pick examples of FOSS software that are quite ergonomic and lovely to feel. Yeah, there are many examples that exist, but they tend to be diamonds in the rough rather than exemplars of the ecosystem. For every one dev in this community who actually has a fucking clue how to make smooth-feeling and aesthetically pleasing software, there’s a score of devs who slapdash together their programmer-art-tier UIs and call it a day, and a thousand other dev-brained users who look at it and go, “this is fine”. And yeah, it is fine. But sometimes I want more than fine.

It’s a divesting of unwanted responsibility.

If any change can break something then all broken bits will need fixing.

Right. So the less decrepit, old code that contains annoying little time bombs, the less time spent fixing things.

But that’s true of all code in the kernel. […] Why not remove all drivers in case an update breaks them.

And how many people actually need these ancient drivers maintained? More than zero, sure, but how many more than zero?

Maintenance effort is a finite resource. Choosing where it gets spent is an executive decision. Every dev hour you assign to debugging some ancient driver that one or two enthusiasts might still want someday is a dev hour not spent on development of some new feature, or fixing a problem affecting thousands, potentially millions of known, current, active users.

We can’t maintain all code forever. At some point the theoretical value it may have is outweighed by its cost to keep alive, and it gets cut.

A driver can be complete and only need updating if someone else breaks stuff, so leave it alone until then and only remove it I’d no one comes to fix it.

That’s sort of where we’re at now, in a way.

Yes, all of these drivers presumably are still fully functional at the time of cutting. But the devs have essentially all decided, “We are not fixing these anymore” already. If any of these break for any reason, they would all be immediate candidates for axing by your system.

The reason they aren’t just left in with a “we’ll just run it until it dies, then!” mentality is because a project like the Linux kernel doesn’t want to be full of software with undefined mystery behavior where they can reasonably avoid it.

A chunk of code being part of it at all is an implicit promise of, “This is intended to function as-documented. If it does not, we are responsible to fix it.” But we already know no one will fix it. So instead it just becomes, “This chunk of code may or may not work. We don’t know and we don’t care, lol. Use at your own risk. If you can prove it’s broken, we’ll just remove it”.

The Linux kernel does not want to be full of code like that. All of its code should be reliable to build things on. If it’s coming out, it needs to be announced in advance so users have time to migrate. A “we will run it until it suddenly breaks” system doesn’t afford that. The feature ideally has to be sunset while it’s still functional.

“Unstable code, use at your own risk” projects are better relegated to optional packages. If someone wants to bundle up these ancient drivers and offer them as an optional package, they are free to do so. If there ends up being zero will from anyone to do even that, I guess it’s more evidence to how little the functionality was actually demanded.

Choice is an irritating speed bump to people who don’t care to choose, which unfortunately is most of them.