Comment Re: Act like a Democrat... (Score 1) 371
A real recovery, one for more than just the 1%, would be greatly appreciated.
Not gonna happen until all the private debt we've accumulated in the last 50 years is gone.
A real recovery, one for more than just the 1%, would be greatly appreciated.
Not gonna happen until all the private debt we've accumulated in the last 50 years is gone.
Everyone works with their files locally, changes are synced via a common server. Everyone has a compressed backup of the complete history of the entire filesystem for disaster recovery. Everyone should be able to browse and recover any version of any file without adding load to the server, though usability might be slightly lacking. You could also setup a FUSE filesystem on a linux box to browse the history.
You may need to partition the file storage into multiple repositories, so that people don't need to synchronise folders that they don't use.
You can hide the videos with a simple adblock filter; "slashdot.org##article#firehose-000".
You could also make the share button go away (slashdot.org##div.popularity), but that does break the tags css.
And in C not just the result, but the behaviour is undefined. If you divide by zero the compiler, runtime libraries and the CPU can do whatever they like. They could ignore you, crash, format your hard drive or kill your pet.
For speed reasons, this is a good thing. If it looks like you might run into undefined behaviour, the compiler can assume that the inputs to the program won't trigger that behaviour. This allows all kinds of optimisations to be performed, from dead code elimination, to hoisting invariant code out of loops.
At least other high level languages define precisely what a divide by zero should do. That way you run into platform or compiler specific heisenbugs far less frequently.
The drive's media wear indicator ran out shortly after 700TB, signaling that the NAND's write tolerance had been exceeded. Intel doesn't have confidence in the drive at that point, so the 335 Series is designed to shift into read-only mode and then to brick itself when the power is cycled. Despite suffering just one reallocated sector, our sample dutifully followed the script. Data was accessible until a reboot prompted the drive to swallow its virtual cyanide pill.
In the logjam paper, they speculate that the NSA has the funds to run the first part of a number field sieve on a small number of 1024bit primes. So long as we keep using software implementations with these well known primes hard coded in their source code, HTTPS SSH & VPN connections may be vulnerable.
Not putting all of our eggs in one basket reduces this risk considerably. In response to this threat, we should periodically publish and use a new set of primes that are appropriate for DH exchanges. Though I would be happier if it were possible to generate a new prime on the first boot of a server.
Or we could swap to using a different method for producing session keys.
OpenSSL has added protection for TLS clients by rejecting handshakes with DH parameters shorter than 768 bits. This limit will be increased to 1024 bits in a future release.
Good. But it doesn't go far enough. How about some kind of deprecation warning if DH is using any well known prime number?
One port to rule them all. One place to find them
One cable to bring them in and be left wondering why nothing is working
FTFY. Look, I like the idea of a single cable and port standard. But there should also be a single protocol. At least you'll have USB3 to fall back on, but I imagine many sales drones and users getting confused on the finer points of compatibility issues.
Humans only have = two hands, and they take up a fair amount of vertical space too. Stack the picking arms 10-20 high, build a conveyor belt that can bring shelves to them and they start to look much more interesting. Sure each robot may take a minute to pick one item. But this is an embarrassingly parallel problem.
Sure you need a directory service. But it needs to be tamper proof. OP is suggesting that all service names should be public keys. So all DHT records that would be published / fetched can be signed. And the connection to the service can also be signed.
That way noone can guess the current key for a known service. Then the only chance of a sybil attack is to convince someone that your key is the service they are looking for. Something that should only be possible by intercepting the first request.
Where there's a will, there's a relative.