EM radiation from the wireless source drops off according to the inverse square law. This has been figured out in the time since Tesla. So no, Tesla's tower could never have worked. Beyond a short distance (like the inches between an RFID card and its reader) power transmission is not feasible because of, you know, physics.
Every gmail UI redesign Google has ever done has decreased the contrast of the elements on the screen. Every time I hear its updating again, I fully expect a "pure" interface that's simply white on white.
We want the military to protect us against threats from outside the country. To do so, it must first identify the threats we face. To do that, it must do enough research in to threats which can be imagined to classify them in to the plausible and implausible. To do that, it must first spend effort identifying what indicators, if found, would allow it to determine that a threat was plausible or implausible.
Nukes weren't possible until they were. If we want to discover that a new technology based on a new science poses a threat before it shows up in the middle of New York City, we have to spend some effort figuring out how we'll figure it out. Research into that "how" makes sense.
It's pretty clear that it should not be possible to disable these transponders / beacons during flight by anyone on board the plane.
Under routine conditions, the modern airliner can pretty much fly itself. The pilot is there to deal with things that go wrong,. Since you can't possibly predict and program for everything that can go wrong, it's important that the pilot have the final say.
Better that a human be the one who killed us than a machine.
Know what else is cheaper than non-disgusting housing in Palo Alto? Non-disgusting housing in about 90% of the country that isn't Palo Alto reachable by a motor vehicle such as an RV.
I'm supposed to feel sorry for someone who has seven dogs? Life choices man. She chose the expense of seven dogs over the expense of non-disgusting housing.
Farmers aren't the only ones. Retail in December. Political work in October. Resort work in the summer. Lots of industries have a crunch time. There's nothing inherently wrong with having a crunch time where employees are expected to work the hours it takes to get the job done. Folks who don't like that sort of work don't have to take that sort of job.
The problem happens when either:
A) The employee was not fully informed about the crunch time and its nature.
B) The crunch time is not accompanied by a comparable lean time in which employees are invited to take paid vacation, relax and attend to their families.That's under-staffing and under-staffing is not an acceptable way to treat employees.
Rand's Atlas Shrugged was first and foremost a work of science fiction. Spoiler alert: the book's mystery-man hero is the inventor of a free energy reactor. To see the book as something else you really have to start with an agenda.
Not only that, it was a work of science fiction with an unusually clever premise: What if the Elon Musks, Larry Pages, Warren Buffets and Jeff Bezos' of the world all got pissed off and decided to go on strike, just like union blue collar workers do?
You don't have to buy in to Rand's political philosophies. I certainly don't. But she wrote an intriguing book.
Exactly. They should have been able to lay their hands on at least one of the hacked servers.
Personally, I grew suspicious when Bloomberg started talking about "signal conditioning couplers," a part which does not actually exist on server motherboards. Maybe they meant the little capacitors marked 103 which condition the power on the advanced electronics boards so they don't have localized voltage sags and surges as the chips change activity and draw more or less power? I don't know but if their sources don't have the basics right, what are the odds they have the rest of it right?
Incidentally, the technical name for this is "settlement-free reciprocal peering." It means that without either company paying the other, they trade data packets whose destination has already paid the receiving ISP to handle those packets. ISPs who refuse a peering request are usually double-billing.
Frontier is not lying. Correctly implemented Net Neutrality does give Netflix and Google free Internet. You see, under Net Neutrality, ISPs are not supposed to double-bill. Once the end user has paid for "Internet," they can't charge the content provider for the same "Internet." Can't charge Netflix for the same bytes that the end user has already paid for.
Since the end user has already paid for those bytes, Netflix gets them for free. Frontier isn't lying; they're "spinning" a desirable trait as if it was undesirable.
You badly misdefine security theater. Like saying a bank robber is a terrorist.
Security theater is highly visible security activity which costs more (typically much more) to operate than it reduces the risk-cost of breach. It's activity whose purpose is to be seen to do something about security regardless of whether the activity is effective.
Risk-cost is Threat times Vulnerability times the Cost of an incident. Operating cost is implementation cost plus the cost of impairment to the primary operating purpose of the protected system.
Where security decreases Risk-cost by more than it increases Operating cost, it isn't theater. It's just security.
Oracle knows they've no prayer of winning the contract outright, so they hope to require a rewrite to facilitate multiple vendors. This will allow Oracle to snooker the occasional fool in DoD procurement who still thinks Oracle is the hotness.
That exposes a basic misunderstanding of how software in Linux is built. The program which presents a remote filesystem should be separate from the program which synchronizes files. That's the unix way.
It also makes Dropbox's job simple: a fuse (filesystem in userspace) driver and then let folks stack whatever other Linux software they want to on top of it.
Google and Azure. Which others? Linnode? Nope. Vultr? Nope. Several offer a "private interface" for talking between servers at a data center without incurring bandwidth charges but that's it.
The "must already have $2B in revenues" is a little sketchy.
These two don't seem particularly discriminatory: Data centers 150 miles or more apart is something every cloud provider of any significance already has. Maybe not every data center is 150 miles from every other, but Amazon doesn't have that either. 32gb ram virtual servers is trivially added for anyone who didn't have it -- the physical servers backing the VMs often have 1TB ram or more.
Here's what really cuts out almost everybody: Amazon has a virtual networking system (VPCs) with their cloud product that allows for complex security infrastructures with VMs behind multiple layers of protection devices. Most cloud providers offer VMs plugged directly in to the Internet. Period.
That's not fair at all. You've no clue what work I've done trying to get word to qualified candidates that I have a job available or how many resumes I've sifted to reach a point where I want to sit down with you. And now you waste my time waiting for you to show up because you couldn't be bothered to let me know you changed your mind. Your self-absorption makes me glad I didn't hire you.
Fortunately for employers you'll exhibit that self-centeredness in ways which show up more obviously on your resume like with the amount of time you spend at each job. In 5 years time, you won't just be unemployed, you'll be unemployable.
My experience with offshore developers was a piece of software which used 100% of all CPU cores while idle. The culprit? A busywait checking the job queue.
I've never been a no-show period. If I won't make it somewhere I've promised to be, I contact the folks I was to meet with and let them know as soon as I know. Basic courtesy folks.
I've been on the other end of this too. Seen candidates not show up and then submit an application to a different job 6 months later. Guess who doesn't get considered for the job?
Following this argument to its natural conclusion, only what exists today can possibly be secure because everything that does NOT exist today fails "the security requirement of Availability".
Exactly. Raymorris grossly misstates the security criterion of Availability.
Availability is about outage: where the app is unavailable or malfunctions either directly due to an attack or indirectly due to features meant to thwart an attack. For example, if your account is locked as a result of 3 wrong passwords, that's a hit to availability. Which is why NIST 800-63 says to rate-limit password attempts rather than imposing lockouts.
Merely having to throw more hardware at it because of a linear change in running efficiency, as happens with microkernels, is not an availability impairment.
The strongest security argument you can make against microkernels is that it's a security failure to spend more money protecting an asset than the asset is worth.
You're correct, but then you have an origin problem: how do you determine that the first record in the new chain is the authentic descriptor of the property? For that matter, how do you determine that the first record in any chain is an authentic descriptor of the property?
Anonymity has nothing to do with it. If the key is lost you can't perform the cryptography necessary to transfer the asset. Regardless of whether you can legally prove who the lost key belonged to.
Slashdot Mirror
EM radiation from the wireless source drops off according to the inverse square law. This has been figured out in the time since Tesla. So no, Tesla's tower could never have worked. Beyond a short distance (like the inches between an RFID card and its reader) power transmission is not feasible because of, you know, physics.
You beat me to to. This is a stylized "retro" web site not a '90s style web site.
Every gmail UI redesign Google has ever done has decreased the contrast of the elements on the screen. Every time I hear its updating again, I fully expect a "pure" interface that's simply white on white.
We want the military to protect us against threats from outside the country. To do so, it must first identify the threats we face. To do that, it must do enough research in to threats which can be imagined to classify them in to the plausible and implausible. To do that, it must first spend effort identifying what indicators, if found, would allow it to determine that a threat was plausible or implausible.
Nukes weren't possible until they were. If we want to discover that a new technology based on a new science poses a threat before it shows up in the middle of New York City, we have to spend some effort figuring out how we'll figure it out. Research into that "how" makes sense.
It's pretty clear that it should not be possible to disable these transponders / beacons during flight by anyone on board the plane.
Under routine conditions, the modern airliner can pretty much fly itself. The pilot is there to deal with things that go wrong,. Since you can't possibly predict and program for everything that can go wrong, it's important that the pilot have the final say.
Better that a human be the one who killed us than a machine.
Know what else is cheaper than non-disgusting housing in Palo Alto? Non-disgusting housing in about 90% of the country that isn't Palo Alto reachable by a motor vehicle such as an RV.
I have no more strategy for caring for stray animals than I do for the bears in the forest or the birds in the sky. And why should I?
I'm supposed to feel sorry for someone who has seven dogs? Life choices man. She chose the expense of seven dogs over the expense of non-disgusting housing.
Farmers aren't the only ones. Retail in December. Political work in October. Resort work in the summer. Lots of industries have a crunch time. There's nothing inherently wrong with having a crunch time where employees are expected to work the hours it takes to get the job done. Folks who don't like that sort of work don't have to take that sort of job.
The problem happens when either:
A) The employee was not fully informed about the crunch time and its nature.
B) The crunch time is not accompanied by a comparable lean time in which employees are invited to take paid vacation, relax and attend to their families.That's under-staffing and under-staffing is not an acceptable way to treat employees.
Rand's Atlas Shrugged was first and foremost a work of science fiction. Spoiler alert: the book's mystery-man hero is the inventor of a free energy reactor. To see the book as something else you really have to start with an agenda.
Not only that, it was a work of science fiction with an unusually clever premise: What if the Elon Musks, Larry Pages, Warren Buffets and Jeff Bezos' of the world all got pissed off and decided to go on strike, just like union blue collar workers do?
You don't have to buy in to Rand's political philosophies. I certainly don't. But she wrote an intriguing book.
Exactly. They should have been able to lay their hands on at least one of the hacked servers.
Personally, I grew suspicious when Bloomberg started talking about "signal conditioning couplers," a part which does not actually exist on server motherboards. Maybe they meant the little capacitors marked 103 which condition the power on the advanced electronics boards so they don't have localized voltage sags and surges as the chips change activity and draw more or less power? I don't know but if their sources don't have the basics right, what are the odds they have the rest of it right?
Incidentally, the technical name for this is "settlement-free reciprocal peering." It means that without either company paying the other, they trade data packets whose destination has already paid the receiving ISP to handle those packets. ISPs who refuse a peering request are usually double-billing.
Frontier is not lying. Correctly implemented Net Neutrality does give Netflix and Google free Internet. You see, under Net Neutrality, ISPs are not supposed to double-bill. Once the end user has paid for "Internet," they can't charge the content provider for the same "Internet." Can't charge Netflix for the same bytes that the end user has already paid for.
Since the end user has already paid for those bytes, Netflix gets them for free. Frontier isn't lying; they're "spinning" a desirable trait as if it was undesirable.
You badly misdefine security theater. Like saying a bank robber is a terrorist.
Security theater is highly visible security activity which costs more (typically much more) to operate than it reduces the risk-cost of breach. It's activity whose purpose is to be seen to do something about security regardless of whether the activity is effective.
Risk-cost is Threat times Vulnerability times the Cost of an incident. Operating cost is implementation cost plus the cost of impairment to the primary operating purpose of the protected system.
Where security decreases Risk-cost by more than it increases Operating cost, it isn't theater. It's just security.
Oracle knows they've no prayer of winning the contract outright, so they hope to require a rewrite to facilitate multiple vendors. This will allow Oracle to snooker the occasional fool in DoD procurement who still thinks Oracle is the hotness.
That exposes a basic misunderstanding of how software in Linux is built. The program which presents a remote filesystem should be separate from the program which synchronizes files. That's the unix way.
It also makes Dropbox's job simple: a fuse (filesystem in userspace) driver and then let folks stack whatever other Linux software they want to on top of it.
Google and Azure. Which others? Linnode? Nope. Vultr? Nope. Several offer a "private interface" for talking between servers at a data center without incurring bandwidth charges but that's it.
The "must already have $2B in revenues" is a little sketchy.
These two don't seem particularly discriminatory: Data centers 150 miles or more apart is something every cloud provider of any significance already has. Maybe not every data center is 150 miles from every other, but Amazon doesn't have that either. 32gb ram virtual servers is trivially added for anyone who didn't have it -- the physical servers backing the VMs often have 1TB ram or more.
Here's what really cuts out almost everybody: Amazon has a virtual networking system (VPCs) with their cloud product that allows for complex security infrastructures with VMs behind multiple layers of protection devices. Most cloud providers offer VMs plugged directly in to the Internet. Period.
That's not fair at all. You've no clue what work I've done trying to get word to qualified candidates that I have a job available or how many resumes I've sifted to reach a point where I want to sit down with you. And now you waste my time waiting for you to show up because you couldn't be bothered to let me know you changed your mind. Your self-absorption makes me glad I didn't hire you.
Fortunately for employers you'll exhibit that self-centeredness in ways which show up more obviously on your resume like with the amount of time you spend at each job. In 5 years time, you won't just be unemployed, you'll be unemployable.
My experience with offshore developers was a piece of software which used 100% of all CPU cores while idle. The culprit? A busywait checking the job queue.
These were top notch C++ developers. Top notch.
I've never been a no-show period. If I won't make it somewhere I've promised to be, I contact the folks I was to meet with and let them know as soon as I know. Basic courtesy folks.
I've been on the other end of this too. Seen candidates not show up and then submit an application to a different job 6 months later. Guess who doesn't get considered for the job?
NCSA Mosaic was first released in January 1993, 25 years and 8 months ago. Lynx only predated it by 6 months; it's tenure on top was short indeed.
Home users didn't particularly discover the Internet until 1995.
Security was primitive. Even by 1996, most of DoD hadn't deployed firewalls yet and NAT's use was pretty rare.
Following this argument to its natural conclusion, only what exists today can possibly be secure because everything that does NOT exist today fails "the security requirement of Availability".
Exactly. Raymorris grossly misstates the security criterion of Availability.
Availability is about outage: where the app is unavailable or malfunctions either directly due to an attack or indirectly due to features meant to thwart an attack. For example, if your account is locked as a result of 3 wrong passwords, that's a hit to availability. Which is why NIST 800-63 says to rate-limit password attempts rather than imposing lockouts.
Merely having to throw more hardware at it because of a linear change in running efficiency, as happens with microkernels, is not an availability impairment.
The strongest security argument you can make against microkernels is that it's a security failure to spend more money protecting an asset than the asset is worth.
You're correct, but then you have an origin problem: how do you determine that the first record in the new chain is the authentic descriptor of the property? For that matter, how do you determine that the first record in any chain is an authentic descriptor of the property?
Anonymity has nothing to do with it. If the key is lost you can't perform the cryptography necessary to transfer the asset. Regardless of whether you can legally prove who the lost key belonged to.