160 karma · joined August 11, 2016
Thus I applaud the author of this website. And I'm really bored of the dullards who chip away at my freedom saying "but it's only a tiny transgression, what does it matter?"
http://www.itv.com/news/wales/update/2015-05-08/angry-voter-...
A Yubikey consists of some secure memory to store a secret and a program, and a processor to run the program to perform computations using the secret.
The programs are different but they are basically the same thing. The author wonders why there isn't a simple general purpose gadget you can load your own program on to. As long as the action of loading a program clears existing secrets, the device could be secure.
Or to put it another way, consider a Raspberry Pi acting as a router and as a Raspberry Pi acting as a media streamer. They have completely different purposes, but they are the same thing.
But in every company I've worked for mail is signed for by whoever and, if it's addressed to an executive, delivered to a secretary who reads it and decides what to do it.
Given the requirement for secrecy, there is zero chance that an NSL will be treated in this way. And it won't be served by a random process server. Most likely it will be served by an NSA employee, in a discreet situation of their choosing.
Historical evidence suggests that there would indeed be fewer accidents but more car drivers would die (because even quite trivial bumps would be fatal), though pedestrians and cyclists would be safer. As someone who chooses not to drive, that sounds pretty good to me.
I don't know if there's a name for this class of problem. I'd be interested to know.
Of course, now you have no UI no restart a particular video. But the advertisers would figure this out about 30s after a global pause feature was introduced.
Thus an aligned read of a 32-bit integer took one memory access; an unaligned read took two, which took twice as long. This killed performance.
Rather than quietly performing badly, the processor threw an exception to encourage you to fix your code.
The ARM2 worked a bit differently. It ignored the bottom two bits of the address when it read a value from memory. When the read was complete the value was rotated by the value of the bottom 2 bits multiplied by 8. This had the effect of putting the byte referenced by the full address in the bottom 8 bits of the 32-bit register. A flag in the instruction let you optionally mask off the top 24 bits to simulate a byte read.
But really, I know it wouldn't have made a difference. From an early age I was taught at school that smoking would kill me and I started anyway. The idea that detailed knowledge of one particular cause of death would have made a difference is laughable. It's just a way of deflecting blame from one's own responsibility.
A quick search turned up [1] which reckons £300 million for installation and £800,000 per annum to maintain. Which seems a bit pricey.
That said, there was a plan to trial it this year, but I can't remember if that was pre- or post-brexit.
tldr: NTFS does a better job of avoiding fragmentation than FAT, but both need defragging.
http://www.aircontrolindustries.com/dangers-of-compressed-ai...
It doesn't seem especially different to the continental systems.
Absolutely. I've been practising this for more than 20 years. When the NT 4.0 Option Pack came out in 1998 I was delighted because it gave me a search engine on my desktop and I could stop feeling guilty about my lack of organisation. I don't have trouble finding things.
You lost a factor of ten. 500 times 1000 is 500,000 so 1GB can hold 500,000 pages. 1TB can hold 500 million.