My corp laptop auto-locks the screen (if that's what you mean), but can also be unlocked by biometrics, but only if it's already on. (And only for a limited time; I think after a week, the password is required again.) If the laptop is booting fresh, the password is required.
I always switch off the biometric access of any machine, so you can save yourself the hassle of cutting off my thumb or trying to unlock a device when I am asleep.
I guess you could hope for their decency to cut off bits only after they've killed you. Combine that with their possible (probable?) stupidity to assume you have biometrics enabled, and they might kill you without even asking for any password, so you'd die secure in the knowledge that they'll never crack your data.
Windows Powertoys has an Awake applet that does the same thing nowadays. Same thing as in, has the same effect of keeping the machine awake, that is; dunno how it does it, if it's simulating a keypress or something else.
Oh boy, I see the potential for very weird bug reports that will be fun to debug when you forget that that thing is active (or another user is using the computer).
Yes it's better to have a hardware fix, like a USB stick that moves the cursor regularly or sends a key press, or even just put your mouse on top of a watch that has hands.
What do you mean by process ID? A PID seems like a useless bit of information. Now an app bundle or process executable checksum... Seems more useful. But couldn't you build the app from source and add a but of random data into the executable?
In other words, you didn't report a touchpad malfunction that was interfering with obvious and clearly stated security policies, and allowed the malfunction to interfere with your work for days/weeks/months without seeking assistance from IT?
This is not a good look, but if that's how you want to play the game of lying to your employer, fine with me!
I just 3D printed a little clip that holds the scroll lock key down. Or, there’s always the mechanical or electronic mouse jigglers you can buy off of Amazon.
I'm not affiliated with either site. Just thought it was cool. I don't think one could argue that building an MVP/SMB on a platform is more buggy than a 1-2 man shop building from scratch, though. At least not in the same amount of time.
Sorry, I just realized that the above workflow is wrong: Since you want to fix a bug, you'll probably clone the development branch of the repo, which doesn't even have a configure script – only source releases have that. So prepend these steps:
0.1) Install the autotools.
0.2) Run autoconf, no wait, automake, no wait, autoreconf, no wait, autoreconf --install.
0.3) Delete all files in the directory and checkout a fresh copy.
1 through 3 (I rarely encounter 6 and never 9) are baked into most OS installers and can be done once then saved as a VM or Docker image to be cloned. That level of pedantry is akin to saying "To compile the project applepie.io from scratch you must first create the universe."
_carbyau_: Simple command to configure your complete dev environment in respect to this project" ?
layoutIfNeeded: configure
adwn: No, because ...
I don't see any pedantry on my part. Also, this:
> [...] and can be done once then saved as a VM or Docker image to be cloned
is like that infamous HN comment proclaiming that nobody needs Dropbox, because you can simply "get an FTP account, mount it locally with curlftpfs, and then use SVN or CVS on the mounted filesystem". The original question asked about a simple command to configure a complete environment.
If ./configure just would work for that project out of the box, that would be great, but it seems more like an exception, because usually it's not sufficient and it breaks on some dependency issues that are easily solvable if you know the dev environment and pretty much need mailing list assistance if you don't know how their project works and you just want to fix an off by one error.
Oh no! Safari refuses to support some "standards" that were unilaterally fast-tracked so that some PM at Google could put it in their promotion case. This is unacceptable!
Cherries and apples have seeds with traces of a cyanide derivative that can be converted in the stomach.
> Cherries have a small, hardened pit that surrounds their seed, also called a kernel. The kernels of cherry pits and other stone fruits contain the chemical amygdalin. Amygdalin is a cyanogenic glycoside — a chemical that your body converts into the toxic compound hydrogen cyanide.
In Ozark episode S2E19, Darlene poisons her husband Jacob's coffee with ground cherry pits, for a current cultural reference.
That’s because the human body can metabolise a small quantity of cyanide. Going by Wikipedia sweet apricot kernels produce ~0.3mg of cyanide when eaten, but the toxic threshold is around 100mg for acute effects.
Still, chronic cyanide exposure isn’t good for you.
"Tampering with FREE DOMAIN and Freenom Traffic-Check.
You understand that a viewer is engaged in Freenom server infrastructure to record the number of visitors to your Freenom domain name (Freenom Traffic-Check). By accepting this Agreement, you hereby agree that you will not tamper with, disable or limit the functionality of the Freenom Service or the Freenom Traffic-Check in any way, including, but not limited to, disabling or otherwise tampering with the viewer displayed when your domain name is accessed by you or a third party."
Pretty easy to solve. We know that electricity can go around the Earth 7 times in a second. Now, if Germany has excess electricity during the day, they can simply pospone that electricity by wrapping a long cable 302 400 times around the globe (12h * 3600s/h * 7/s = 302 400). During the day they feed the excess electricity into one end of the cable, and then 12 hours later at night, electricity comes out the other end at just the right time, when they need it!
IIRC, antopodal HVDC would have resistive losses of either 70% or 30% — I’d have to recalculate from scratch to find out which, but it doesn’t matter much either way: the real issues are “How much does the line cost?” and “what are the political implications of that size power line in all the places it has to pass through?”
Batteries and HVDC to your nearest major desert are what I expect to be the solutions.
The following claims HVDC transmission losses of 3.5% per 1,000 km @ 800kV, therefore 20,000 km is 100% - ((100% - 3.5%)^20) ~= 51% loss; I guess my previous calculations were a different voltage, but as I’m asserting that even the difference between 30% and 70% doesn’t matter, neither does this :)
> Several systems which exhibit all three properties of Zooko's triangle have now been created, including:
> Computer scientist Nick Szabo's paper "Secure Property Titles with Owner Authority" illustrated that all three properties can be achieved up to the limits of Byzantine fault tolerance.
> Activist Aaron Swartz described a naming system based on Bitcoin employing Bitcoin's distributed blockchain as a proof-of-work to establish consensus of domain name ownership. These systems remain vulnerable to Sybil attack, but are secure under Byzantine assumptions.
> Several platforms implement refutations of Zooko's conjecture, including: Twister (which use Swartz' system with a bitcoin-like system), Blockstack (separate blockchain), Namecoin (separate blockchain), LBRY (separate blockchain and peer-to-peer file-sharing), Monero OpenAlias and Ethereum Name Service.
https://en.m.wikipedia.org/wiki/Alice_in_Wonderland_syndrome