So, what has this analysis taught me? For an ordinary pitch, the trajectory follows a smoothly curving line approximated by nearly constant acceleration. For a knuckleball, rather than a line, imagine that the trajectory is confined to lie inside a tube which itself follows a smooth curve. However, the ball is otherwise free to flutter and zig-zag within the confines of the tube. With that picture in mind, the analysis I have presented shows that the diameter of that tube is very small, on the order of a few tenths of an inch at most. ...
The smoothness conclusion appears to contradict the popular belief that knuckleball trajectories are erratic and often experience abrupt changes of direction. Let me speculate that this belief is the result of the randomness of movement, both in magnitude and direction, giving rise to the perception of erratic behavior. We have all seen instances where the catcher and pitcher get their signals crossed, and the catcher has to lunge for the ball at the last moment. The catcher expects a certain movement, and the pitcher throws something with different movement. With the knuckleball, no one really knows what movement to expect, so it is not surprising that the catcher has some difficulty cleanly catching the ball and that the batter has even more difficulty hitting it.
No, that's a separate issue. I'm literally saying that if you don't need the data, don't keep it. If it's sensitive, overwrite it, then delete it. In many businesses, they keep sensitive data (in logs, databases, etc.) that they have no use for. For example, they needed a CC number for a few seconds to process a transaction, but for reasons that have nothing to do with the transaction, they write the CC number to a log of a database. If you don't need the information, don't keep it.
So, I didn't do a bad job of stating what you think I said, I stated exactly what I meant.
I'm not young, but I stream music regularly. I use a service called FM radio.;)
But other than checking out some newer stuff on YouTube, I buy all my music because I don't have 24/7, unlimited broadband internet access, and even if I did, wireless is not, and never will be as reliable as local storage, so it wouldn't actually be 24/7 access. And that's without addressing the time I spend driving in mountains, or in tunnels, or other places where wireless (radio or internet) doesn't work (or works so poorly as to be useless for streaming)
Due process for civilians while we're not in a declared war does in fact mean in a court of law. Only members of the military and "enemy combatants" are subject to military jurisdiction outside of military facility or area declared to be under martial law.
I take a somewhat simpler approach to security: Build it so that breaking it costs more than the value of what you're protecting. There is no perfect security. All of it can be hacked. Your only responsibility, professionally, ethically, morally, is to make it cost them as much or more to break through than whatever is being guarded.
My recommendations do that, both by making sure the data has the lowest possible value (items 1-3), and by making it as difficult at possible (item 4).
As for you earlier comments, Go back and read again, they all allow for all of the situations you addressed. You have misinterpreted them.
1. Never put sensitive data on a computer connected to the internet, unless it absolutely must be there. 2. Never keep sensitive data that you don't need, overwrite it, then delete. 3. Never put confidential data into any computer system, networked or not. If you must, do so only if it's encrypted and secured by strong authentication at all times. 4. Use all practical forms of security, firewalls, strong authentication, multiple networks with isolation, IDS, AV/anti-malware, no running as Admin/root, separate accounts for every user with appropriate access restrictions, including separate accounts for any services running on your servers, whole disk encryption, etc.
The first 3 are what I call the "Mr Miyagi" approach, "Best defense, no be there." Item 4 is what most companies focus on, but it's not nearly as useful if you haven't used 1-3.
Right idea, missing a detail. Get your data and hard to replace equipment (e.g. custom orders, long lead time, no longer available) first. That may be servers, or just the HD's from them. After that, everything that is replaceable can be picked based upon it's value, size, ease of removal, and available space. If you have to take workstation HDs, try to get one of each model of workstation so you have at least one machine that you know will work with that HD. It's not critical, but it can save you some effort if the facility does burn. Most networking gear, phones, workstations, etc. are easily replaceable, don't mess with them until the more important stuff is out.
And most importantly, DO NOT WAIT until you receive the evac order, start packing at least 24 hours before an evac is likely. I don't care what management says about taking down the network early, your data and your lives are far more valuable than an extra day working.
I used a Chrome browser as a client, and proxied the sites through Cotendo to control whether SPDY is used. Note that all the tests – whether HTTP, HTTPS or SPDY – were proxied through Cotendo, to ensure we’re comparing apples to apples.
Since they all ran through the same proxy, it might be the limiting factor. We would need to see tests the bypass the proxy to determine if his results have any meaning beyond that specific proxy.
Likewise, you have to ask the question, do all of the 500 sites he tested support SPDY?
Yes, the human eye and the brain are going to be the limits. And given the range of intensities (e.g. contrast) one can see at any given time, and the ability to discern continuous color gradients, it appears that we'll need somewhere between 24 and 36 bits driving displays with contrast ~5000:1, using at least 3 color narrow band color sources centered on the frequencies to which the eye cones respond, and capable of delivering more than 1000 lux (the brightness of an overcast day) at the viewer's position to have displays that can adequately reproduce the color range we can see. The intensity range we can see is much larger than that, but we can't see all of it at once, so as long as the contrast is sufficient, we don't need full sunlight type brightness.
You read the actual comments before responding to the something that wasn't said, because it makes you look like an ass. If you read the post I replied to, and my answer, I directly addressed the problem of using multiple line frequencies. Neither of us said anything about capacity.
The fact that they use two different frequencies isn't a problem because they use HVDC between them. The capacity of that interconnect is a separate issue, just as is the capacity of any other interconnect.
Additionally, it's sometimes possible to have your product available in the market before the patent has been published (but the application is complete), again, competitors might try reverse engineering, and you are protected (even retroactively) once the patent is granted.
I'm quite familiar with patent, copyright, trade secret, and reverse engineering. And while it sounds silly to try to reverse engineer it if you can just read the patent, the fact remains that a patent DOES protect you against someone using the information they reverse engineered. Some items contain patents AND trade secrets, so even though part is patented, and the patent describes that, other parts may still require reverse engineering, so it's not as silly as it initially sounds.
That's what their company does, the primary uses of their software is in exactly the fields you mentioned. He simply applied it to BB as his pet project.
Monsanto, or the farmer who's seed contaminated a non-Monsanto seeded field should be the one receiving the injunction or other sanction. If Monsanto and their buyers can't control the distribution of their patented seed, that should in no way impair a farmer who chooses not to use Monsanto seed. If their GE seeds make it into a non-Monsanto field, they should be required to purchase all of the contaminated crop at fair market value with no penalty to the farmer whose field was contaminated through no action of his own.
Patents on bio materials that self replicate/seed need to have different rules applied to the simply because they do self-replicate. Seeds which are scattered to a non-GE crop field by wind or mechanized farming equipment should be the responsibility of the seed producer and/or the farmer using the GE seed, not any neighboring farmer whose field may be contaminated.
They do protect against reverse engineering. They can't use your patented method no matter how they learn it, unless they have a license. If they can find a way of doing it that doesn't violate the patent, they're fine.
How about starting to come up with ideas on how to apply this concept to physics, medicine, engineering and economics? Jeez...
How about RTFA? He was presenting on behalf of Ayasdi, a company run by Stanford mathematicians, whose proprietary software is used by physicians, environmentalists, and the government to understand cancer, diabetes, and oil spills.
Because the gamut of 24-bit RGB doesn't cover the entire range of visible colors and intensities. While we can only distinguish ~ 8M colors, we can distinguish a huge range of intensities. 24-bit displays cover 16M colors AND intensities, so in this case, 16M is not > 8M because they're counting different things.
While current displays are adequate for most purposes, they do not display all of the colors we can see, nor all the intensities we can see. Typical displays only cover 45%-75% of the AdobeRGB (1998) color-space, which itself is a subset of the visible gamut. Some (more expensive) displays cover a greater percentage of the visible range, but none cover the entire range.
I know patents protect against independent invention, reverse engineering, etc. but if your product produces seed that "infects" another field or wind blows those seeds to another field, you are NOT entitled to royalties on those seeds.
ARM has had competition, MIPS. ARM has generally had a slight advantage in power utilization vs MIPS.
Intel hasn't been a factor because up until a few months ago, they haven't produced a CPU that could compete on power utilization. Now it looks like they're finally competitive on power utilization, so their expertise in performance and manufacturing process technology makes them potentially a serious competitor. However, Intel has made many improvements to Android in order to be competitive with ARM based devices. If those same improvements (or the ones made by Linaro) are rolled into the standard Android distribution, will Intel's new chip still be competitive on performance and power utilization? Who knows. It's too early to say anything other than that Intel is finally close enough to be taken seriously.
Slashdot Mirror
Power, size, an cost. Like all engineering, it was a compromise. They chose to optimize those 3 rather than use a separate LTE chipset.
Actually, that's not what he said:
So, what has this analysis taught me? For an ordinary pitch, the trajectory follows a smoothly curving line approximated by nearly constant acceleration. For a knuckleball, rather than a line, imagine that the trajectory is confined to lie inside a tube which itself follows a smooth curve. However, the ball is otherwise free to flutter and zig-zag within the confines of the tube. With that picture in mind, the analysis I have presented shows that the diameter of that tube is very small, on the order of a few tenths of an inch at most.
...
The smoothness conclusion appears to contradict the popular belief that knuckleball trajectories are erratic and often experience abrupt changes of direction. Let me speculate that this belief is the result of the randomness of movement, both in magnitude and direction, giving rise to the perception of erratic behavior. We have all seen instances where the catcher and pitcher get their signals crossed, and the catcher has to lunge for the ball at the last moment. The catcher expects a certain movement, and the pitcher throws something with different movement. With the knuckleball, no one really knows what movement to expect, so it is not surprising that the catcher has some difficulty cleanly catching the ball and that the batter has even more difficulty hitting it.
They learned from Microsoft and Apple. If you just name it the same thing, you can make people think it's the same.
Same name, different phone. The US model is very different. So, yes, this is an official launch.
No, that's a separate issue. I'm literally saying that if you don't need the data, don't keep it. If it's sensitive, overwrite it, then delete it. In many businesses, they keep sensitive data (in logs, databases, etc.) that they have no use for. For example, they needed a CC number for a few seconds to process a transaction, but for reasons that have nothing to do with the transaction, they write the CC number to a log of a database. If you don't need the information, don't keep it.
So, I didn't do a bad job of stating what you think I said, I stated exactly what I meant.
I'm not young, but I stream music regularly. I use a service called FM radio. ;)
But other than checking out some newer stuff on YouTube, I buy all my music because I don't have 24/7, unlimited broadband internet access, and even if I did, wireless is not, and never will be as reliable as local storage, so it wouldn't actually be 24/7 access. And that's without addressing the time I spend driving in mountains, or in tunnels, or other places where wireless (radio or internet) doesn't work (or works so poorly as to be useless for streaming)
Due process for civilians while we're not in a declared war does in fact mean in a court of law. Only members of the military and "enemy combatants" are subject to military jurisdiction outside of military facility or area declared to be under martial law.
If you watch the video (it's about 52mins long), he's surprisingly blunt. It's not a polished presentation, but it is interesting.
I take a somewhat simpler approach to security: Build it so that breaking it costs more than the value of what you're protecting. There is no perfect security. All of it can be hacked. Your only responsibility, professionally, ethically, morally, is to make it cost them as much or more to break through than whatever is being guarded.
My recommendations do that, both by making sure the data has the lowest possible value (items 1-3), and by making it as difficult at possible (item 4).
As for you earlier comments, Go back and read again, they all allow for all of the situations you addressed. You have misinterpreted them.
1. Never put sensitive data on a computer connected to the internet, unless it absolutely must be there.
2. Never keep sensitive data that you don't need, overwrite it, then delete.
3. Never put confidential data into any computer system, networked or not. If you must, do so only if it's encrypted and secured by strong authentication at all times.
4. Use all practical forms of security, firewalls, strong authentication, multiple networks with isolation, IDS, AV/anti-malware, no running as Admin/root, separate accounts for every user with appropriate access restrictions, including separate accounts for any services running on your servers, whole disk encryption, etc.
The first 3 are what I call the "Mr Miyagi" approach, "Best defense, no be there." Item 4 is what most companies focus on, but it's not nearly as useful if you haven't used 1-3.
Right idea, missing a detail. Get your data and hard to replace equipment (e.g. custom orders, long lead time, no longer available) first. That may be servers, or just the HD's from them. After that, everything that is replaceable can be picked based upon it's value, size, ease of removal, and available space. If you have to take workstation HDs, try to get one of each model of workstation so you have at least one machine that you know will work with that HD. It's not critical, but it can save you some effort if the facility does burn. Most networking gear, phones, workstations, etc. are easily replaceable, don't mess with them until the more important stuff is out.
And most importantly, DO NOT WAIT until you receive the evac order, start packing at least 24 hours before an evac is likely. I don't care what management says about taking down the network early, your data and your lives are far more valuable than an extra day working.
I used a Chrome browser as a client, and proxied the sites through Cotendo to control whether SPDY is used. Note that all the tests – whether HTTP, HTTPS or SPDY – were proxied through Cotendo, to ensure we’re comparing apples to apples.
Since they all ran through the same proxy, it might be the limiting factor. We would need to see tests the bypass the proxy to determine if his results have any meaning beyond that specific proxy.
Likewise, you have to ask the question, do all of the 500 sites he tested support SPDY?
Yes, the human eye and the brain are going to be the limits. And given the range of intensities (e.g. contrast) one can see at any given time, and the ability to discern continuous color gradients, it appears that we'll need somewhere between 24 and 36 bits driving displays with contrast ~5000:1, using at least 3 color narrow band color sources centered on the frequencies to which the eye cones respond, and capable of delivering more than 1000 lux (the brightness of an overcast day) at the viewer's position to have displays that can adequately reproduce the color range we can see. The intensity range we can see is much larger than that, but we can't see all of it at once, so as long as the contrast is sufficient, we don't need full sunlight type brightness.
Interconnects are part of the design of all electrical grids, not "some half-assed workaround".
You read the actual comments before responding to the something that wasn't said, because it makes you look like an ass. If you read the post I replied to, and my answer, I directly addressed the problem of using multiple line frequencies. Neither of us said anything about capacity.
The fact that they use two different frequencies isn't a problem because they use HVDC between them. The capacity of that interconnect is a separate issue, just as is the capacity of any other interconnect.
Additionally, it's sometimes possible to have your product available in the market before the patent has been published (but the application is complete), again, competitors might try reverse engineering, and you are protected (even retroactively) once the patent is granted.
I'm quite familiar with patent, copyright, trade secret, and reverse engineering. And while it sounds silly to try to reverse engineer it if you can just read the patent, the fact remains that a patent DOES protect you against someone using the information they reverse engineered. Some items contain patents AND trade secrets, so even though part is patented, and the patent describes that, other parts may still require reverse engineering, so it's not as silly as it initially sounds.
That's what their company does, the primary uses of their software is in exactly the fields you mentioned. He simply applied it to BB as his pet project.
Monsanto, or the farmer who's seed contaminated a non-Monsanto seeded field should be the one receiving the injunction or other sanction. If Monsanto and their buyers can't control the distribution of their patented seed, that should in no way impair a farmer who chooses not to use Monsanto seed. If their GE seeds make it into a non-Monsanto field, they should be required to purchase all of the contaminated crop at fair market value with no penalty to the farmer whose field was contaminated through no action of his own.
Patents on bio materials that self replicate/seed need to have different rules applied to the simply because they do self-replicate. Seeds which are scattered to a non-GE crop field by wind or mechanized farming equipment should be the responsibility of the seed producer and/or the farmer using the GE seed, not any neighboring farmer whose field may be contaminated.
They do protect against reverse engineering. They can't use your patented method no matter how they learn it, unless they have a license. If they can find a way of doing it that doesn't violate the patent, they're fine.
Actually, that's not a problem, they use an HVDC line between the two grids.
How about starting to come up with ideas on how to apply this concept to physics, medicine, engineering and economics? Jeez...
How about RTFA? He was presenting on behalf of Ayasdi, a company run by Stanford mathematicians, whose proprietary software is used by physicians, environmentalists, and the government to understand cancer, diabetes, and oil spills.
Because the gamut of 24-bit RGB doesn't cover the entire range of visible colors and intensities. While we can only distinguish ~ 8M colors, we can distinguish a huge range of intensities. 24-bit displays cover 16M colors AND intensities, so in this case, 16M is not > 8M because they're counting different things.
While current displays are adequate for most purposes, they do not display all of the colors we can see, nor all the intensities we can see. Typical displays only cover 45%-75% of the AdobeRGB (1998) color-space, which itself is a subset of the visible gamut. Some (more expensive) displays cover a greater percentage of the visible range, but none cover the entire range.
I know patents protect against independent invention, reverse engineering, etc. but if your product produces seed that "infects" another field or wind blows those seeds to another field, you are NOT entitled to royalties on those seeds.
ARM has had competition, MIPS. ARM has generally had a slight advantage in power utilization vs MIPS.
Intel hasn't been a factor because up until a few months ago, they haven't produced a CPU that could compete on power utilization. Now it looks like they're finally competitive on power utilization, so their expertise in performance and manufacturing process technology makes them potentially a serious competitor. However, Intel has made many improvements to Android in order to be competitive with ARM based devices. If those same improvements (or the ones made by Linaro) are rolled into the standard Android distribution, will Intel's new chip still be competitive on performance and power utilization? Who knows. It's too early to say anything other than that Intel is finally close enough to be taken seriously.