I want to thank Beau for including the explanation of backbone providers for all of us who would have been scratching our heads about how a tier 1 outage could possibly be affecting us personally.
Just FYI, any time you are given something of value, it is income.
This is nonsense. You realize taxable income only on items of value (including in-kind) when part of an economic transaction.
Let a friend live in your house? Not income. Write off a debt? Potentially income, depending on the specifics of the debt. Fee waivers? Not income, simply a reduction in price. (Newsflash: Coupons aren't income.) Interest-free loans? Not an issue unless connected to some other transaction and in reality away of compensating you for something.
They aren't. The best guess I've seen is that the product can only handle SHA-1 certificates, and the company is unwilling or unable to obtain a replacement SHA-1 that will be trusted by the cert store.
And in order to produce more natgas, they pump refinery wastes into the ground and shock them, in a process euphemistically called "fracking"
This sounds like an argument from someone who was ejected from Greenpeace for going too far.
Fracking fluids don't contain any "refinery waste"--they're mostly water and sand, along with various chemicals that help keep the fluid flow laminar rather than turbulent (primarily friction reducers). They aren't "shocked" in any sense of the word, simply pumped at insanely high pressure. And "fracking" isn't a euphemism, it's a typically-formed abbreviation of the straightforwardly descriptive term "hydraulic fracturing".
The phrase "hop on" is vastly more infuriating than either of those canards. It's a reliable tell that the person who's using it doesn't have to do any stateful work that gets derailed in an environment of constant pointless interruptions.
It's the section of the penal code that explicitly enumerates the situations in which conduct that is otherwise unlawful is justified. It is there specifically to override the "brandishing" prohibition in such cases.
Sec. 9.04. THREATS AS JUSTIFIABLE FORCE. The threat of force is justified when the use of force is justified by this chapter. For purposes of this section, a threat to cause death or serious bodily injury by the production of a weapon or otherwise, as long as the actor's purpose is limited to creating an apprehension that he will use deadly force if necessary, does not constitute the use of deadly force.
tl;dr: It's lawful if you're in a "legitimate defensive situation".
I was initially annoyed by the Material Design specification that button text should be in all caps, and I wish that they'd explain their rationales more thoroughly. However, after a bit, here's what I think is going on:
We all know about the tendency for users to click buttons blindly; browser security warnings were notorious for a decade. All-caps text is known to be more difficult to read, and I suspect that having buttons as all-caps (in combination with strong advice to make them action descriptions rather than "OK" and "Cancel") is intended to slow users down just a tad so that they have a moment to think about the action. Once the UI is learned, it's irrelevant, and any slowdown doesn't apply.
I worked for amex as an analyst for a couple of years. They do not (nor do visa or mc) have the ability to see itemised transactions from stores. They can see the merchant id (ie. the store), the amount of $, and they have a lookup table that will assign the merchant to a particular industry. That's pretty much it.
This is blatantly false. My Amex online account lists itemized receipts for at least some retailers (I remember offhand all of the office-supply chains).
He put his faith in two organizations no one trusts.
In fact, he reasonably relied on their assurances that service was available to his detriment. It seems to me that he should be contacting an attorney.
Knowing the ins and outs isn't necessary. Knowing generally what it's used for is, just as much as any developer should know "don't store plaintext passwords". I'm not offhand familiar with how to securely generate a salt, and I use a library that does that, but I certainly know that there's a Wrong Way to handle passwords.
How many deployment avenues don't use cryptographic signatures? Usually you're either producing downloadable code, in which case the packages or tarballs are generally signed, or deploying to an HTTP or similar server, in which case you should at least understand what the purpose of TLS is.
That's if you're trying to permit AJAX requests cross-site, and that's pretty easy. The difficulty with the JavaScript image-decoding shims is that they're trying to intercept the browser's ordinary page-loading flow, and at least Firefox (the one major browser that doesn't support WebP) won't let JavaScript hook into third-party img loads.
What in the world are you talking about? I have an application that's focused on processing and displaying user images. Are you seriously claiming that it would be better practice for me to deal with reinventing the storage wheel instead of saving everything to S3 and serving it from there?
Same-origin policy is a nightmare for use with CDNs. I really wanted to use WebP for image handling for the application I'm working on, but Firefox adamantly refuses to merge a patch adding WebP support, and the JavaScript shim can only access the images if they're pulled of the same host. Images loaded from a CDN aren't accessible to the JS decoder.
Slashdot Mirror
Most likely Antminer S9s.
I want to thank Beau for including the explanation of backbone providers for all of us who would have been scratching our heads about how a tier 1 outage could possibly be affecting us personally.
In other news, Google Maps still pulls a megabyte of data when you open it to display a useless "what's nearby" panel that can't be disabled.
Maybe start with cutting out data-hungry misfeatures in your own applications?
This is nonsense. You realize taxable income only on items of value (including in-kind) when part of an economic transaction.
Let a friend live in your house? Not income. Write off a debt? Potentially income, depending on the specifics of the debt. Fee waivers? Not income, simply a reduction in price. (Newsflash: Coupons aren't income.) Interest-free loans? Not an issue unless connected to some other transaction and in reality away of compensating you for something.
They aren't. The best guess I've seen is that the product can only handle SHA-1 certificates, and the company is unwilling or unable to obtain a replacement SHA-1 that will be trusted by the cert store.
This sounds like an argument from someone who was ejected from Greenpeace for going too far.
Fracking fluids don't contain any "refinery waste"--they're mostly water and sand, along with various chemicals that help keep the fluid flow laminar rather than turbulent (primarily friction reducers). They aren't "shocked" in any sense of the word, simply pumped at insanely high pressure. And "fracking" isn't a euphemism, it's a typically-formed abbreviation of the straightforwardly descriptive term "hydraulic fracturing".
Odd that the judge calls this "unprecedented", when there have been multiple similar instances, and Lawn Chair Larry was internationally infamous.
The phrase "hop on" is vastly more infuriating than either of those canards. It's a reliable tell that the person who's using it doesn't have to do any stateful work that gets derailed in an environment of constant pointless interruptions.
It's the section of the penal code that explicitly enumerates the situations in which conduct that is otherwise unlawful is justified. It is there specifically to override the "brandishing" prohibition in such cases.
tl;dr: It's lawful if you're in a "legitimate defensive situation".
I was initially annoyed by the Material Design specification that button text should be in all caps, and I wish that they'd explain their rationales more thoroughly. However, after a bit, here's what I think is going on:
We all know about the tendency for users to click buttons blindly; browser security warnings were notorious for a decade. All-caps text is known to be more difficult to read, and I suspect that having buttons as all-caps (in combination with strong advice to make them action descriptions rather than "OK" and "Cancel") is intended to slow users down just a tad so that they have a moment to think about the action. Once the UI is learned, it's irrelevant, and any slowdown doesn't apply.
checks article Yup, Airbus.
You mean Groovy, which was the inspiration for Swift and has been able to target Android for at least a year and a half?
This is blatantly false. My Amex online account lists itemized receipts for at least some retailers (I remember offhand all of the office-supply chains).
Well, the sociopathic profit-seekers who work for companies whose customers can go elsewhere. The sociopathic profit-seekers in government get to abuse to their heart's content. And lest there be any doubt about the latter, the regulator in question was yesterday specifically calling for abuse of "antitrust" action against American companies.
Reliance doesn't require a contract. Both providers reasonably should have known that service wasn't available at the address.
In fact, he reasonably relied on their assurances that service was available to his detriment. It seems to me that he should be contacting an attorney.
Knowing the ins and outs isn't necessary. Knowing generally what it's used for is, just as much as any developer should know "don't store plaintext passwords". I'm not offhand familiar with how to securely generate a salt, and I use a library that does that, but I certainly know that there's a Wrong Way to handle passwords.
How many deployment avenues don't use cryptographic signatures? Usually you're either producing downloadable code, in which case the packages or tarballs are generally signed, or deploying to an HTTP or similar server, in which case you should at least understand what the purpose of TLS is.
And they make money by ensuring that there are drivers.
That's if you're trying to permit AJAX requests cross-site, and that's pretty easy. The difficulty with the JavaScript image-decoding shims is that they're trying to intercept the browser's ordinary page-loading flow, and at least Firefox (the one major browser that doesn't support WebP) won't let JavaScript hook into third-party img loads.
What in the world are you talking about? I have an application that's focused on processing and displaying user images. Are you seriously claiming that it would be better practice for me to deal with reinventing the storage wheel instead of saving everything to S3 and serving it from there?
Same-origin policy is a nightmare for use with CDNs. I really wanted to use WebP for image handling for the application I'm working on, but Firefox adamantly refuses to merge a patch adding WebP support, and the JavaScript shim can only access the images if they're pulled of the same host. Images loaded from a CDN aren't accessible to the JS decoder.
No, the actual number of defensive gun uses is only around 7000 per day in the United States.
and still no merge of the working WebP patch that was proposed four years ago because NIH.