AnyOldName3

It’s not Kessler Syndrome until it’s so bad that we can’t feasibly launch anything new. A single cascading collision chain might calm down again after breaking a lot of stuff without any catastrophic long term impact if all the debris ends up either in a stable orbit that can be predicted and avoided by other objects, or unstable orbits that decay until the debris falls out of orbit.

As someone who’s just spent half an hour reading Wikipedia thanks to this thread, I can now dispense a summary of what I read to make it feel like I didn’t just waste a chunk of time I should have spent in bed by wasting another chunk of time I should be spending in bed.

Fats are made out of fatty acids, which are carboxylic acids with a longish carbon chain. A saturated fatty acid only has single bonds between carbon atoms, a monounsaturated fatty acid has a single double bond somewhere in the chain (and these are sometimes things that turn into buzzwords, e.g. omega three oils are ones where there’s a single double bond three along from the end of the chain), and a polyunsaturated fatty acid has more than one double bond.

Single bonds in a carbon chain can only be one way around, so you don’t get isomers of saturated fatty acids, but double bonds in a carbon chain can be in either of two orientations. If the hydrogens are on the same side for both sides of the bond, that’s the cis orientation, and if they’re on opposite sides, that’s the trans orientation. Most natural unsaturated fats are cis, so they generally don’t get explicitly labelled as cis fats, and just the trans ones get the extra label. Notably, though, vaccenic acid, which is about 4% of the fat in butter, is trans by default, so it’s cis-vaccenic acid that gets the extra label.

Unsaturated fats tend to be more liquid at room temperature, but can be made by growing cheap vegetables. They also go off faster as free radicals can attack the double bonds. Saturated fats tend to be solid at room temperature, but mostly need to come from animals or more expensive plants (palm fat is an exception - it’s cheap and mostly saturated). It’s therefore desirable to use industrial processes to artificially saturate fats, and we can do that by heating them up and exposing them to hydrogen in the presence of a catalyst like Nickel. You don’t necessarily want to fully saturate your fat, though, so might stop part way, and if you do, unless you intentionally tweak the process to avoid it because it’s the 21st century and you’re legally obliged to, you get some of the partially hydrogenated fat switching from cis to trans.

Over the course of the last century, we realised that (except for a few like vaccenic acid) trans fats are harmful in lots of exciting ways, e.g. messing up cholesterol, blocking your arteries, and building up in your brain. They’ve therefore been banned or restricted to certain percentages in a lot of the world. You can get a similar effect by fully hydrogenating things to get safe (or at least safer) saturated fat and mixing it with the unmodified fat, or by switching everything that used to use hydrogenated vegetable oil to using palm oil, which is one of the driving forces behind turning rainforests into palm plantations.

Apparently, this was twenty five minutes of writing, so I’m nearly up to an hour of thinking about fats.

I said he more-or-less killed him, not that he actually killed him. Care was not taken to ensure he’d be revived or revivable. He was left forgotten in a pocket. The likely outcome was that he remained forgotten and didn’t get wet until he’d been dropped under some furniture, crushed like a stock cube or gone mouldy. Maybe he had dependents, like a young child who’d have died without their parent. It being theoretically possible to revive someone later doesn’t make turning them into a dehydrated cube meaningfully better than making them dead if you don’t have a strong plan with a failsafe to make sure they stop being a cube. Even with guaranteed revival, if they’re a cube for long enough that they notice the lost time, it’s just like roofying someone and holding them hostage for a while. Do not turn museum guys into dehydrated cubes.

If not for an accident where he ended up in a washing machine, he’d have been left as a cube indefinitely. From a cube’s perspective, there’s no difference between being a cube and being dead.

Upstream Firefox doesn’t comply with FDroid’s rules (thanks to the ‘proprietary bits and telemetry’ Handles mentioned), so is only available from the Play Store or as a loose APK that won’t auto-update.

He did more-or-less kill, and then steal the identity of, the museum guy. He’s not a paragon of virtue, either.

I’m pretty sure Reddit used to be profitable. There used to be a bar on the right-hand side that showed how far each day’s Reddit Gold purchases had gone towards covering the day’s server costs. When I first started using Reddit, it’d typically be about a third of the way full when it reset, but a few years after the at, it was filling up after about eight hours, suggesting they were covering the server costs three times over, which should have left plenty of money for staffing costs as they didn’t have many staff back then. Eventually, they got rid of the bar. Later, they did things that would have increased costs, like hiring people to make New Reddit and the Reddit App, and hosting images and videos themselves instead of leaving it to imgur, and I guess these were enough to make them no longer profitable and force them to aim for faster growth.

But it does mean you can spend forty hours a week or thereabouts putting effort into a particular goal and maintaining the knowledge, skills and experience to keep doing it to a high standard without having to sink time and effort into something else in order to get paid enough to live on.

When the internet was becoming a world-changing technology, there weren’t thirty years of websites to keep working and malware to protect from, web standards were far simpler, and a much higher proportion of users were enthusiasts who were excited by anything they could get and didn’t mind if things were rough around the edges. Similarly, two brothers could make the world’s first aircraft that flew under its own power, and yet with the combined might of everyone working for Boeing, people are worried about airliner doors falling off and an eight-day space trip has become an eight-month one. Mature technologies need a lot more effort to build and maintain than emerging ones.

Maintaining a web browser in the 2020s is an expensive thing to do. You need full time employees who specialise in all the systems that make up a browser, and can’t leave security-critical parts like ensuring the integrity of the JavaScript sandbox to volunteer hobbyists. It’s far from the only thing Mozilla spend money on, so if they need to mage cost savings, it won’t necessarily stop them being able to maintain Firefox, but another organisation picking it up if they do stop isn’t likely.

If you give a chip more voltage, its transistors will switch faster, but they’ll degrade faster. Ideally, you want just barely enough voltage that everything’s reliably finished switching and all signals have propagated before it’s time for the next clock cycle, as that makes everything work and last as long as possible. When the degradation happens, at first it means things need more voltage to reach the same speed, and then they totally stop working. A little degradation over time is normal, but it’s not unreasonable to hope that it’ll take ten or twenty years to build up enough that a chip stops working at its default voltage.

The microcode bug they’ve identified and are fixing applies too much voltage to part of the chip under specific circumstances, so if an individual chip hasn’t experienced those circumstances very often, it could well have built up some degradation, but not enough that it’s stopped working reliably yet. That could range from having burned through a couple of days of lifetime, which won’t get noticed, to having a chip that’s in the condition you’d expect it to be in if it was twenty years old, which still could pass tests, but might keel over and die at any moment.

If they’re not doing a mass recall, and can’t come up with a test that says how affected an individual CPU has been without needing to be so damaged that it’s no longer reliable, then they’re betting that most people’s chips aren’t damaged enough to die until the after warranty expires. There’s still a big difference between the three years of their warranty and the ten to twenty years that people expect a CPU to function for, and customers whose parts die after thirty-seven months will lose out compared to what they thought they were buying.

It wasn’t me who you replied to originally - I agree that it’s most likely AMD are just being super cautious given historically how many times bad news for their competitors has been falsely equated by the press as equivalent to a minor issue they’ve had, and the delay moving things after the microcode update and therefore making launch-day benchmarking more favourable is just a bonus.

You’ve misunderstood. The original release date was set, then Intel announced the microcode update, which was after the original release date, then AMD announced that they’d be delaying the release date, and that new release date is after the microcode update.

If anyone’s in this thread because they’re looking for a new mail client after Microsoft killed the old Mail app, and haven’t been happy with the typical suggestions of using each email service’s web interface or Thunderbird, I found I don’t hate Mailspring (with the fancy features disabled - I just want my email client to do email well and don’t want extras that provide clutter).

Coal, not oil, but it’s still an interesting fact.

It’s at least common on forums as bots love making accounts with non-megacorp email addresses on PhpBB and MyBB forums. Typically, there aren’t people signing up the same services with business emails as personal ones, so if ones expecting not to be used by businesses want to fight spam, it’s generally pretty effective and consequence-free to block email providers not known to have effective anti-bot measures built in.

That would be annoying for people who work on files with a double extension for legitimate reasons, e.g. .tar.gz, and (this can’t be stressed strongly enough) Windows users do not pay attention to warning popups, so it wouldn’t actually help. Despite it being eighteen years since Windows Vista released, and therefore vanishing unlikely that any given software was written assuming that Windows didn’t have a permissions system, it’s still most people’s first troubleshooting step to try and run things as admin, and you still get loads of people (including ones who should know better, e.g. ones who also use Linux and would never log in as root) who disable UAC as one of the first things they do when setting up a windows install, and end up running everything as the equivalent of root just to suppress the mildly annoying pop-up when something asks for elevated permissions.

So, your proposed popup:

• would be annoying including for legitimate uses
• wouldn’t help as anyone who already ignores the smart screen popup that shows up when running a dodgy application will ignore the new popup, too
• would be disabled by huge swathes of users anyway

Better have comments on Crunchyroll than make me go to R*ddit to find out if I missed something in an episode, especially as anime subreddits typically start permitting episode spoilers before the dub for that episode is out, so there’s often nowhere except the dub comments on Crunchyroll that’s safe to look for dub watchers.

Super useful for something like Overlord, where scenes with background information were cut and there’d be someone saying what else you’d know by this point in the manga, or if you’d forgotten something since watching a previous season and needed a reminder.

It’s a silly flag to use as it only works when running 32-bit Windows applications on 64-bit Windows, and if you’re compiling from source, you should also have the option to just build a 64-bit binary in the first place. It made a degree of sense years ago when people actually used 32-bit Windows sometimes (which was usually just down to OEMs installing the wrong version on prebuilt PCs could have supported 64-bit) if you really wanted to only have one binary or you consumed a precompiled third party library and had to match its architecture.