There are a fair few troubleshooting things I’ve seen where I could have smugly pointed out a clever way Windows avoids the same problem or an easy way it provides to solve it, so it doesn’t even always need the lol at the end. It’s just an annoying thing to see when you’re already annoyed at a disobedient computer, unless learning the technical details would be an interesting distraction, so should be saved for when you know your audience and know it’s interesting.
The format was originally designed to interchange animated palettised depictions of giraffes, so Giraffic Interchange Format made sense. They just changed the acronym when they realised that by storing different colours in the palette, you could depict things other than giraffes.
The green slime was originally mouldy bin contents made of food waste from several days before. It was far from innocent.
I’ve never used or dissassembled an American microwave, so wouldn’t know about anything American-specific.
Having a ceramic plate at the end of the wave guide isn’t evidence that there’s not a wave stirrer on the other side of the plate or part way along the wave guide. As far as the microwaves are concerned, the ceramic plate is a hole, though, because (unless the manufacturer selected a stupid material), it should be about as transparent to microwaves as the air is.
if the diagram’s any good, it should show the wave stirrer in the roof rather than on the ceiling of the food chamber. There’s typically a waveguide to take the microwaves from the magnetron to the top of the chamber, then the wave stirrer is at the end of the waveguide to vary the angle that microwaves enter the chamber at. There’s usually something to stop food splashing/spraying into that section, though, e.g. an extra few centimetres of waveguide afterwards with a bend in it.
Of all the dangerous devices to disassemble, they’re one of the safest. A phone charger might still have 400V across one of the capacitors ten minutes after unplugging it (if you’re in a 230V RMS country, so have more than 400V peak-to-peak), but a microwave’s high-voltage section is only powered when it’s plugged in, and microwaves are so long wavelength that even if you reassemble the waveguide or outer case badly and leave gaps, there probably won’t be dangerous levels of microwaves escaping as gaps much smaller than the wavelength in question don’t compromise the Faraday cage.
Usually it’s not inside the same chamber as the food as then it would be a nuisance to clean. You need to take a microwave apart to see the wave stirrer.
Most microwaves have a spinning wave stirrer in addition to the rotating plate. From the description here, it just sounds like either your plate rotation motor is broken or you’ve got a weirdly simple microwave.
Instead of git history, you get a git fairy tale. Practically, the merge conflicts and their resolutions get spread across one or more commits on the branch that was rebased, and the history makes it look like all the work was done after the upstream commit(s) that there was a conflict with. This can be much tidier, but also loses the context of changes. E.g. you can no longer see that something is done differently to everywhere else that does the same thing not because it needs to do it differently, but because it copied and pasted something from ten lines above and the thing ten lines above received a bug fix on another branch which the feature branch was rebased onto. Based on my experience working on large projects that used both approaches, I’d rather scroll past extra commits and squiggly branch lines than try to reconstruct what someone was thinking when they made a mistake without access to the original commit they made the mistake in. If I had to allow history-rewriting operations in git, the one I’d pick would be rewriting the history of Earth so that when history rewriting operations were implemented in git, they defaulted to adding some metadata to the rewritten commits making the operations reversible so I could decide I wanted the real history back.
In this case, the product was free to OSS developers not because they were the product, but because they’re influencers likely to end up encouraging their users and/or employers to buy the paid version, so it was the marketing that those people could do that was the product.
This change with the data harvesting makes those developers the product, though.
Technically it’s even a ToS violation to install extensions from the VS Code marketplace (or whatever it’s called) if you’re using VS Codium. Many are also available somewhere else like the code forge where they’re developed and are under open source or free software licenses, but quite a few important ones are only available through the one distribution channel you’re not allowed to use, and contain proprietary components that can’t be forked to lift this restriction.
Oops. I’d somehow missed that there was now a third kind of JPEG.
The compression technique it used was patented, and the licence fee was extortionate. By the time the patent expired, other, royalty-free, techniques were available that outperformed it.
With how the law is written, if you think anyone might ever make a mistake (likely), think the government might ever bother going through the hassle of enforcing it (probably less likely if you’re not running a big website), and don’t have loads of spare money to pay huge fines with or to pay an age verification service with (likely), then blocking the UK is the only way to be compliant. It doesn’t require a technicality. The law just doesn’t have any leeway for honest minor mistakes or small hobbyist websites.
Some instances use the image proxy and others don’t. It seems that mine doesn’t.
Fun fact: I can’t see the screenshot as I’m in the UK and your instance has taken the maximally paranoid literal meaning of the OSA and blocked access just in case anything’s accidentally not flagged as NSFW.
He’d already contributed to humanity by writing the definition of wanker for the Oxford English Dictionary by the age of 28, though.
Windows permissions are more flexible than basic Unix ones. A file doesn’t just have an owner and a group, it can have individual permissions for arbitrarily many entities, so taking ownership doesn’t remove any of the permissions from anything that already had access, it just adds more. The command shown here is closest in effect to deciding you’re always going to log in as root from now on, although Windows has a way to effectively do that without modifying the ACL of every file. Either way, it’s silly, and usually people who suggest it are under the impression that XP did permissions right by not meaningfully enforcing them and not having an equivalent of a root account you can temporarily switch to, and Vista only changed things specifically to annoy people, and not to be more like Unix.
I’m not saying it’s not worthwhile to do this to fix a broken phone, just that if you have to do this, then the phone was bricked, and once you’re replacing hardware, you’re not just recovering it.
It’s its default use case - adding MBA idiocy to things that were already fine and didn’t need changing.