Kid, take your meds and fuck off.
Kid, take your meds and fuck off.
The Great Extinction, caused by Siberia becoming one gigantic lava bed (probably after an asteroid strike), was a bit further back in time. Geologically, Siberia is old. You might be confusing the vestiges of Ice Age dessication (which was 10,000 years ago) but which involves the organics on the surface with the geology (aka rocks).
Regardless, though, of how the craters are forming, the fact remains that an awful lot of greenhouse gas is being pumped into the air, an awful lot of information on early civilization is being blasted out of existence, and a lot of locals are finding that the land has suddenly become deadly.
That is a good question. The last time the courts ruled on this, the ruling was that the FCC had ceded power and couldn't claim it back without the will of god. Or Congress, or something.
Personally, I'm all in favour of Thor turning up to the Supreme Court, but he probably wouldn't be allowed in on account of not having a visa.
Myth: Anyone gives a damn about factually dubious rants.
As far as I know, Systemd has no capacity to think and therefore has no opinion on net neutrality.
Why do these assholes even take an oath of office these days? The fourth amendment isn't ambiguous, and the failure of the courts to enforce it doesn't change what it says. The NSA is committing billions of felonies.
Google "Jimmy Hoffa".
Collective bargaining forms the basis for an intelligent, social civilisastion.
Unions in the USA exist to steal money from workers to buy hookers and blow for mobsters and politicians. The teamsters in particular are as dirty as they come.
First, the complexity of the engine shouldn't matter. You will never get the bulk of users out there to use, or care about, the real power of the engine. They don't want to mess with the engine. The engine should be under the hood, in a black box, whatever engineering metaphor you want. Users just want things that work.
I remember way back when I was at university. There were various absolute rules for good software engineering. The first was that the user should be presented with a must-read manual no longer than one paragraph. Tips and tricks could be more extensive, but that one paragraph was all you needed.
The second was that the user absolutely must not care about how something was implemented. In the case of encryption, I take that to mean, in the case of e-mail, that the engine should not be visible outside of configuration. A supplied key should trigger any behind-the-scenes compatibility mode or necessary configuration to talk to that user. If the keys the user has aren't suitable to correspond with that person, the system should ask if one is needed and tie it to that protocol.
There should be no extra controls in e-mail, except at an advanced user level. If a key exists to correspond with a user, it should be used. If a key exists for inbound e-mail, the key should be applied. The process should be transparent, beyond getting passwords.
Any indexes (particularly if full indexes) should be as secure as the message, good security practices on both will take care of any issues.
Ideally, you want to have the same grades of authentication as for the early certification system, adapted to embed the idea that different people in the web of trust will have done different levels of validation and will be trusted to different degrees. The user should see, but not have to deal with, the level of trust.
Last, GnuPG is probably not the system I'd use. Compatibility cruft needs to be as an optional layer and I'm not confident in implementation.
There should be eight main libraries - public key methods, secret key methods, encryption modes, hashes (which encryption modes will obviously pull from), high level protocols, key store, index store and lacing store. (Lacing is how these are threaded together.) The APIs and ABIs to those libraries should be standardized, so that patching is minimally intrusive and you can exploit the Bazaar approach to get the best mix-n-match.
There should also be a trusted source in the community who can evaluate the code against the various secure and robust programming standards, any utilized theorum provers and the accepted best practices in cryptography. Essentially replicate the sort of work NIST does, but keeping it open and keeping it free of conflict of NSA interest.
Grinding it to filings is not fast.
Less than fifteen minutes to totally destroy it, I would say.
This is not the case for ApplePay. You get a notification on your phone asking "do you want to pay (amount) to (vendor)", and you put your thumb on the fingerprint reader if you do. Less time than handing the cashier a bill and waiting for him to count out your change.
Why is it that cops ever recover murder weapons at all? Seems to me that if you have a gun that could incriminate you, the obvious thing to do is get a bench grinder and turn it into a pile of filings.
All you need is a spot welder.
US businesses are as incompetent and insecure as Sony, but can be provoked into taking absolutely minimal action when their profits are under direct threat by sufficiently powerful financial organizations. You mean nothing, you never have, you never will. You have no say, you have no power, you have no rights, you cannot walk away. You aren't the customer, merely the product. Easily replaced if damaged.
You aren't getting security because security matters. You aren't getting security because you matter. You're getting it because two vendors and a trading bloc said so.
Show me a man who is a good loser and I'll show you a man who is playing golf with his boss.