![](https://feddit.uk/pictrs/image/22e50f06-ec00-4e07-a853-a523f75c60bf.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
I don’t think that was a malfunction…
That was ‘working as intended’.
I don’t think that was a malfunction…
That was ‘working as intended’.
Almost happened to Frank Rubio when the radiator blew on his ride.
You could make a religion out of this.
I thought one thruster has been permanently disabled now? Not that that’s a major problem, but it does eat into their redundancy somewhat.
How will they filter it out? If they just don’t mirror anything with ‘forbidden’ terms, we can poison repos to prevent them being mirrored. If they try to tamper with the repo histories then they’ll end up breaking a load of stuff that relies on consistent git hashes.
Kenya believe it‽
I just take a chip
Cheers.
I got an overpriced 250×200mm sheet off Amazon, just because it was easy. It’s definitely available cheaper elsewhere. I was trying to get blank black G10 / FR4 board to match the PCB but it doesn’t seem easily available in small quantities (except from China). I just searched for 1.6mm sheet and this stuff came up (it’s 0.06 inch but close enough). It cuts really well with a hacksaw - didn’t chip or crack at all and cleans up with a file or just a craft knife. I roughed it up the surface with sandpaper to CA glue it together and they’re holding together great.
The key cap set I got only had 1 and 1.5U. There are some 1.25U caps available separately online so I may well do that, thanks!
Is there any reason to keep the existing set-up? If it’s just one drive, you could replace it with another and install Alma or something fresh. Then you could copy over whatever config the old system had to get up and running again. You could swap to the old drive if you needed to revert. If you have a spare machine, you could stand up the fresh setup side-by-side with the old one before swapping over.
I think you meant “mean”, hitch is completely different to “moan”.
libera te tutemet ex inferis
The Seebeck effect. The same way a thermocouple works.
Whichever one has the smallest relative path to the workbook using it? How does it find the workbook if it isn’t open already?
Don’t forget that there’s a hidden system junction at C:\ProgramData\Application Data
that points to C:\ProgramData
. Because everyone loves loops in their filesystem. Of course C:\Users\All Users
is also a junction to C:\ProgramData
. This kills updatedb in WSL.
Don’t hurt me
Brush tools.
I still don’t understand the point of namespaces. I guess it’s less overhead to pass through a namespace to a VM rather than having a virtualised disk image or bind mount.
Because then it would be 'a;imodo not qazimodo.