Permanently Deleted
Permanently Deleted
This has the slight problems that:
Permanently Deleted
Modern nukes contain a subcritical mass of fissile material and require an injection of tritium to arm them, and also require tritium for their second stage to get most of their rated yield. Tritium doesn't last very long, so needs regularly topping up. If you've secretly buried a nuke, you'll have to dig it up pretty often, undermining the advantages of secret burial. There's also not much point in having a better nuclear deterrent than your enemy knows about, as the goal is to make them know you can destroy them so they're too scared to attack you rather than to actually destroy them.
TOML's design is based on the idea that INI was a good format. This was always going to cause problems, as INI was never good, and never a format. In reality, it was hundreds of different formats people decided to use the same file extension for, all with their own incompatible quirks and rarely any ability to identify which variant you were using and therefore which quirks would need to be worked around.
The changes in the third panel were inevitable, as people have data with nested structure that they're going to want to represent, and without significant whitespace, TOML was always going to need some kind of character to delimit nesting.
Permanently Deleted
CV padding and main character syndrome.
You can get loads of frames per second with cloud gaming, just not necessarily from the right second.
Password managers are supposed to be designed to resist a situation where they're compromised, and are only ever supposed to see a mysterious blob of encrypted data without ever having access to any information that would help decrypt it. The headline's more like M1 Abrams Tanks Vulnerable to Small Arms Fire - it'd be totally expected that most things die when shot with bullets, but the point of a tank is that it doesn't, so it's a big deal if it does.
The DHT11 has been replaced twice with similarly-priced but more accurate models, first the DHT22 and then the AHT20. In my experience, the AHT20 is a lot better than the DHT22, mainly because its power consumption is far lower, so it doesn't mess up its readings by getting hot.
Also, at that size, I'd be very surprised if the dehumidifier has a compressor. It's much more likely that it's got a Peltier plate, and they're not very good. They use a lot of power to develop and maintain a fairly small temperature difference, so if they're in a confined space, they heat up the air quite a bit, and then the water from their tank will more easily evaporate.
If you're willing to spend some money, a solid state ion membrane dehumidifier might be better for a small cabinet than a compressor-based one, as it'll be easy to ensure the water goes out of the cabinet instead of into a container that can't be emptied without opening the cabinet and letting more humidity in. They're definitely not cheap, though. I think they're still under patent as there's only one manufacturer that I can find, so maybe they're the dehumidifier of the future even if they're not suitable right now.
If it's the problem that I've seen people complain about in the past, it's effectively the same as HTTPS 'not supporting' end to end encryption because it runs over IP and IP packets contain the IP address of where they need to go, so someone can see that two IP addresses are communicating, which is unavoidable as otherwise there's nothing to say where the data needs to go, so no way for it to get there. Someone did a blog post a couple of years ago claiming Matrix was unsecure as encrypted messages had their destination homeserver in plaintext, but that doesn't carry any information that isn't implied by the fact that the message is being sent to that homeserver's IP.
It was £7, so likely not worth the effort - if they want me to pay to ship it back, then that would cost about as much as the roll did - and it's now outside the warranty period, so that would be pointless anyway.
When it's hot, it stinks of hot ABS, and it dissolves in acetone. I've read that sometimes budget filament manufacturers will use the same pigment across their whole material range, even if it's not capable of withstanding the print temperatures of some of them, but it's ABS+ rather than pure ABS, so it could be full of mystery additives that don't handle heat well, too.
There's not much point using it as glue as I'm not going to get through a whole kilo worth of ABS glue, and produce more than enough ABS scraps from test prints and support to always make a colour-matched glue anyway.
TIL: Besides offering a free compromised email check, haveibeenpwned.com also offers a free password compromise checking service (It's also fun to see what weird passwords have been used/leaked.)
It makes a cryptographically-secure hash of the password you enter, then truncates that before sending it to the server so the only information they get would be in common with a huge number of other passwords. They then send back the leaked passwords with the same truncated hash, and your computer checks to see if what you've entered matches anything on the list. It's not practical to send the whole list for every query as there's just too much data, but if you don't trust their site, you can just download the whole list and check against it yourself.
Permanently Deleted
It had some Kings, they'd just become feral ghouls. It was effectively one guy's Elvis fan club, so having any identifiable members decades later would be a surprise.
I dug up a manual for the Windows 3.1 SDK, and it turns out that it had the same GetVersion function with the same return value as the Windows 2000 SDK, and it's just that the live MSDN docs pretend that Windows 2000 was the first version of Windows, so show that as the earliest version that every function that came from an older version of Windows. http://bitsavers.informatik.uni-stuttgart.de/pdf/microsoft/windows_3.1/Microsoft_Windows_3.1_SDK_1992/PC28914-0492_Windows_3.1_SDK_Getting_Started_199204.pdf page 31.
I then looked at a manual for the Windows 1.03 SDK, and it, too, has a matching GetVersion function.
The only change to GetVersion over the entire history of Windows is that at some point it switched from returning a sixteen bit value with eight bits for the major version and eight bits for the minor version to a 32-bit value with bits split between major, build number and minor versions, and then later on, GetVersionEx was added to return those numbers as members of a struct instead. There has never been a version of Windows where string comparisons of the display name were appropriate or recommended by Microsoft.
If you're checking for Windows 9 in order to disable features, which is what the jump straight to ten was supposed to protect against (when running a 16-bit binary for 3.1/95 on 32-bit Windows 10, it lies and says it's Windows 98), then you're using at least the Windows 2000 SDK, which provided GetVersion, which includes the build and revision numbers in its return value, and the revision number was increased over 7000 times by updates to Windows 2000.
There was a function that would give you a monotonically-increasing build number that you could compare against the build that any given feature was added in that people should have used, but there was also a function that gave you the name of the OS, and lots of people just checked if that contained a 9. The documentation explicitly said not to do that because it might stop working, but the documentation has never stopped people using the wrong function.
Fillets are easier to print horizontally than chamfers as they spread the acceleration (i.e. the thing that makes sharp corners bad) over the while fillet instead of just splitting it into two stages like a chamfer would.
Chamfers are easier to print vertically than fillets as the overhang is limited and consistent.
There's no overhang for a horizontal corner as you're printing the same shape onto the layer below, and no acceleration for a vertical corner as it's entirely separate layers so the toolhead never has to follow the path of the corner.
It sounds like you've read (or only remembered) half a rule. It's not the case that either half of the rule is used the majority of the time because 3D printers are used to print 3D objects, so they always produce objects with both horizontal and vertical edges.
But this guy says it, and he's defined himself to be the sole authority, so that matters more than any number of biologists.
Every argument they come up with has been refuted in past threads, and they just dismiss anything they disagree with as irrelevant, but treating tenuous sources like a supposed screenshot of Imane Khalif's SRY test originating from an obscure site that's never been republished by a mainstream one, even if they'd been calling for her to be barred from future tournaments based on no evidence so would love to vindicate their stance with test results.
It's not worth your time to engage with them in good faith.
This is far from the second time. They show up a lot.
I've never actually needed primer to paint PLA unless the paint I was using was terrible, and wouldn't have stuck to the primer very well, either. Tamiya's acrylics have been entirely issue-free for me, both with a brush, or thinned and airbrushed, and they're not that expensive, but I've also had acceptable results with random fifteen-year-old tubes of really cheap acrylics that were sold more as a children's toy than a serious paint (although a lot of these tubes had gone bad in that time) and with Humbrol and Revel acrylics and enamels (although their acrylics come in pots that don't seal very well, so it's not that uncommon for them to be already cured when you first open them - if you're buying liquid acrylics for model painting, Tamiya is a better choice).
That only debunks it if Lucas spent a lot of time thinking about Dutch and if Luke Skywalker is the only person who ever had a father.