"Over the next seven days...wore a device on their wrist... the thinking group were far less active during the week than the non-thinkers"
It doesn't mention if these people had a week off work, or if they had to work normally during those hours. So one wonders if there is a correlation here between "thinking people" having desk job, and "non-thinking people" having more active jobs, like pizza delivery -- was the job they do taken into account in the study?
I know after a day working out problems and stretching my mind, when I get home I just want to sit and unwind. About the most active thing I would do is walk the dog. So I can understand why thinking people may be lazier, to some respect (at least to _my_ respect), but I know a lot of intelligent "thinking people" who would be quite active, which would go against the reported findings of this study.
Without access to the paper itself I can't answer these for myself.
Actually, download the demo of Kerbal Space Programme and play through the tutorial. It gives a really good example of how orbits work. You can learn a lot in just those few minutes.
The orbit will eventually, after a couple of planned manoeuvres in the coming months, bring Juno as close at ~4500km from the surface of Jupitor. Currently the orbit brings Juno quite far from the planet, out beyond Callisto. Stage 1 was just to get Juno captured by Jupiter's gravity. We can expect better photos in the coming months when Juno gets closer.
Take the 4th right, take exit number x, or the exit for downtown. Also, not all city blocks are based on miles on all US cities. Manhattan has rectangular blocks, so heading up 5th 4 blocks wouldn't even be a mile (it might be a kilometre).
International, nautical, Roman, Italiian, Arabic, long, British, Irish, Welsh, Scots, English, US Survey, or "metric"... can you be a little bit more specific as to which mile you are referring?
The number of keys generated is huge - 3.4x10^38. It would take a Very Long Time (tm) to just count that far. Take a single CPU running at 2.3GHz. Let's assume best case we can do one iteration in 1 clock cycle, so that's 2.3billion iterations per second for a single core. That amounts to 1.47x10^29 seconds, or around 5.6x10^22 years. How many CPU cores do you think Amazon, Microsoft, and Google have between them? Even if we were to assume they each had 10million x 4 core CPUs (so 120,000,000 cores), it would still take ~4.6x10^14 years, or approx. 33,510 times the current age of the universe.
So scale all you like, it'll still take a tad longer than 2 weeks... (and that's assuming you stick to 128bit keys. If you were to go with 256bit keys, then the number of keys is slightly less than the number of atoms in the known universe...)
How are Samsung defining IP68? IP68 requires that the phone be able to be placed in at least 1m (~3ft) of water. The manufacturer should then state to what depth it's covered. Do Samsung say that it's certified to greater than 1m?
IP68 is _typically_ up to 3m, but has a minimum spec of 1m.
The 6 of 68 is the dust spec - this is the highest dust spec and requires that the phone be subject to a vacuum for up to 8 hours. The 8 is the water spec and is the 2nd highest spec (9K being the next)
512 bit implies public/private key encryption, and bad encryption at that. For public/private key encryption you don't need to list every number, just every prime, and the list of every prime multiplied by every other prime. To do this properly, head to 4096 bits, though.
This is just one of those reasons I don't use facebook, and why I believe more people shouldn't. Yes, it's convenient. But that's about it's only pro...
When I was in college (in the early 90s!!!) the keypad to get through the door to the computing labs out-of-hours would scramble like this. It always looked cool and was a good idea, but also a bad idea for the very reason you mentioned - several of the students were blind and then couldn't get through the door. Then ended up turning off the scrambling.
I was back there a couple of years ago, and the same keypad was still in place (and the same codes still worked - great security!). And it still didn't scramble.
If you add braille to the keys too (the relevant bumps could present themselves), then it would work for blind people. But I'm sure there will be others that will run into issues... maybe put a button to the side or a selection on the screen to set them in the normal order, but default them to scramble...
Not really - the watch will still pick up on the repetitive movements and still know what PIN you are entering. It might be better to fake press all of the buttons on the keypad in order 4 times, and only really press one button on each iteration to correspond with the PIN digits. It would be harder for the watch to determine the difference in this case, but still not impossible.
Interestingly Android N has this built in too. A new emergency contact screen has been added allowing you to add contacts that will appears under 'emergency call' when your screen is locked. Along side this, you can specify some information about yourself, like date of birth, blood type, and whether you are an organ doner. And it doesn't require that you installed an app first - it's part of the OS.
So a poor homeless latino gets "(sentence + 5 + 10) * 2", and a poor homeless black man get "(sentence + 5 + 10) * 3" Sounds about right, unfortunately...
My personal preference for cooking a steak is to put it in a 60C oven for an hour and a half, tightly wrapped in cellophane. This will ensure that the meat is fully cooked, but still rare (it's completely pink throughout). I then throw it in a hot pan for a minute on each side, and it's done. Juicy and tender.
I got this method from a professional chef who cooks full fillets in this restaurant like this - when someone orders a fillet, he cuts a steak off the already-fully-cooked fillet and then just caramelises the outsides quickly in a hot pan. He'll use a thermometer to ensure that the beef is 58C before cutting it.
Interesting. I would suggest that if you are just taking a sip when the tea is above 63C, then it would have lost several degrees by the time it hits your throat. Unless, that it, you swallow that sip really fast.
It interesting that the comfortable temperature to drink the tea is around 59C/60C. Our pain receptors tend to react to thing that are dangerous to us, and it's almost as if they are already saying that the tea it too hot and is dangerous. It would be interesting to see similar data from some other people for comparison.
They actually said 65C, in case anyone was wondering why it was a strange number (149F).
I really wish people would report what WHO actually said, and then put the equivalent units in brackets:
"... at temperatures hotter than 65C (149F)..."
I also wish people would report in SI units always. Put local units also, but always have SI, either as the primary number, or a secondary in brackets. The preference would be SI as primary and local in brackets as secondary. (remembering, of course, that 6.6bn people use SI units, and 350-400m use those other ones)
But that just my wish... I know it'll likely not happen. But one can always wish and hope...
Slashdot Mirror
"Over the next seven days ...wore a device on their wrist... the thinking group were far less active during the week than the non-thinkers"
It doesn't mention if these people had a week off work, or if they had to work normally during those hours. So one wonders if there is a correlation here between "thinking people" having desk job, and "non-thinking people" having more active jobs, like pizza delivery -- was the job they do taken into account in the study?
I know after a day working out problems and stretching my mind, when I get home I just want to sit and unwind. About the most active thing I would do is walk the dog. So I can understand why thinking people may be lazier, to some respect (at least to _my_ respect), but I know a lot of intelligent "thinking people" who would be quite active, which would go against the reported findings of this study.
Without access to the paper itself I can't answer these for myself.
The iPhone was really just a copy of the Palm Pilot phone...
That first comic was the reason I started playing KSP!
I was thinking to myself "Focus! FOCUS!!!"...
Actually, download the demo of Kerbal Space Programme and play through the tutorial. It gives a really good example of how orbits work. You can learn a lot in just those few minutes.
I never knew the moons had their names hovering below them like that... wow! The names look huge - should I be able to see them with the naked eye?
The orbit will eventually, after a couple of planned manoeuvres in the coming months, bring Juno as close at ~4500km from the surface of Jupitor. Currently the orbit brings Juno quite far from the planet, out beyond Callisto. Stage 1 was just to get Juno captured by Jupiter's gravity. We can expect better photos in the coming months when Juno gets closer.
Take the 4th right, take exit number x, or the exit for downtown. Also, not all city blocks are based on miles on all US cities. Manhattan has rectangular blocks, so heading up 5th 4 blocks wouldn't even be a mile (it might be a kilometre).
More details (with animated gif) here: http://cfht.hawaii.edu/en/news...
(include measurements in SI units)
International, nautical, Roman, Italiian, Arabic, long, British, Irish, Welsh, Scots, English, US Survey, or "metric"... can you be a little bit more specific as to which mile you are referring?
Hopefully this table will shed some light on on the complexity of the question: https://en.wikipedia.org/wiki/...
The number of keys generated is huge - 3.4x10^38. It would take a Very Long Time (tm) to just count that far.
Take a single CPU running at 2.3GHz. Let's assume best case we can do one iteration in 1 clock cycle, so that's 2.3billion iterations per second for a single core.
That amounts to 1.47x10^29 seconds, or around 5.6x10^22 years.
How many CPU cores do you think Amazon, Microsoft, and Google have between them? Even if we were to assume they each had 10million x 4 core CPUs (so 120,000,000 cores), it would still take ~4.6x10^14 years, or approx. 33,510 times the current age of the universe.
So scale all you like, it'll still take a tad longer than 2 weeks...
(and that's assuming you stick to 128bit keys. If you were to go with 256bit keys, then the number of keys is slightly less than the number of atoms in the known universe...)
At least you camelCase your hash tags...
#noncamelcasedhashtagscanbedifficulttoread
How are Samsung defining IP68? IP68 requires that the phone be able to be placed in at least 1m (~3ft) of water. The manufacturer should then state to what depth it's covered. Do Samsung say that it's certified to greater than 1m?
IP68 is _typically_ up to 3m, but has a minimum spec of 1m.
The 6 of 68 is the dust spec - this is the highest dust spec and requires that the phone be subject to a vacuum for up to 8 hours.
The 8 is the water spec and is the 2nd highest spec (9K being the next)
https://en.wikipedia.org/wiki/...
https://www.youtube.com/watch?...
512 bit implies public/private key encryption, and bad encryption at that.
For public/private key encryption you don't need to list every number, just every prime, and the list of every prime multiplied by every other prime.
To do this properly, head to 4096 bits, though.
for (i=0; i0xffffffffffffffff; i++)
printf("%16x\n",i);
printf("ffffffffffffffff");
or something along those lines. That'll produce all 128bit keys. Just don't ask me to match each key with each piece of data...
This is just one of those reasons I don't use facebook, and why I believe more people shouldn't.
Yes, it's convenient. But that's about it's only pro...
When I was in college (in the early 90s!!!) the keypad to get through the door to the computing labs out-of-hours would scramble like this. It always looked cool and was a good idea, but also a bad idea for the very reason you mentioned - several of the students were blind and then couldn't get through the door. Then ended up turning off the scrambling.
I was back there a couple of years ago, and the same keypad was still in place (and the same codes still worked - great security!). And it still didn't scramble.
If you add braille to the keys too (the relevant bumps could present themselves), then it would work for blind people. But I'm sure there will be others that will run into issues... maybe put a button to the side or a selection on the screen to set them in the normal order, but default them to scramble...
Not really - the watch will still pick up on the repetitive movements and still know what PIN you are entering. It might be better to fake press all of the buttons on the keypad in order 4 times, and only really press one button on each iteration to correspond with the PIN digits. It would be harder for the watch to determine the difference in this case, but still not impossible.
Interestingly Android N has this built in too. A new emergency contact screen has been added allowing you to add contacts that will appears under 'emergency call' when your screen is locked. Along side this, you can specify some information about yourself, like date of birth, blood type, and whether you are an organ doner. And it doesn't require that you installed an app first - it's part of the OS.
So a poor homeless latino gets "(sentence + 5 + 10) * 2", and a poor homeless black man get "(sentence + 5 + 10) * 3"
Sounds about right, unfortunately...
Sounds like the same algorithms that are used to calculate your insurance premium...
Beef is cooked once it hits 58C (136.4F).
My personal preference for cooking a steak is to put it in a 60C oven for an hour and a half, tightly wrapped in cellophane. This will ensure that the meat is fully cooked, but still rare (it's completely pink throughout). I then throw it in a hot pan for a minute on each side, and it's done. Juicy and tender.
I got this method from a professional chef who cooks full fillets in this restaurant like this - when someone orders a fillet, he cuts a steak off the already-fully-cooked fillet and then just caramelises the outsides quickly in a hot pan. He'll use a thermometer to ensure that the beef is 58C before cutting it.
Other chefs use a Sous Vide to do this.
Interesting. I would suggest that if you are just taking a sip when the tea is above 63C, then it would have lost several degrees by the time it hits your throat. Unless, that it, you swallow that sip really fast.
It interesting that the comfortable temperature to drink the tea is around 59C/60C. Our pain receptors tend to react to thing that are dangerous to us, and it's almost as if they are already saying that the tea it too hot and is dangerous. It would be interesting to see similar data from some other people for comparison.
They actually said 65C, in case anyone was wondering why it was a strange number (149F).
I really wish people would report what WHO actually said, and then put the equivalent units in brackets:
"... at temperatures hotter than 65C (149F) ..."
I also wish people would report in SI units always. Put local units also, but always have SI, either as the primary number, or a secondary in brackets. The preference would be SI as primary and local in brackets as secondary. (remembering, of course, that 6.6bn people use SI units, and 350-400m use those other ones)
But that just my wish... I know it'll likely not happen. But one can always wish and hope...