Get a CRT that's designed for the refresh rate you run it, rather than the one with the fastest phosphors, at and you won't need such ridiculous frame rates. 100+ Hz video sample rates are as useless as 96 kHz audio sample rates.
So what you're saying is your phosphors were too fast to drive any reasonable refresh rate, so you wasted a bunch of processing power driving the screen at 160 Hz?
Multi-sync CRTs were a terrible plan; there is a reason they never caught on in real video/movie production. I understand why they happened -- they're great for compatibility and idiot-proof setup, and at the time on-board resampling was not cost effective -- but in terms of video quality it's a bad time. If the screen isn't going to ghost at 160 Hz it needs to have *fast* phosphors. Which means if you drive it at 75 Hz, which is plenty fast for almost any human use, it's going to be dim and flickery. You can pretend to adjust for that by driving the gun at a different intensity scale for different refresh rates, but it's a hack; CRTs really need to be driven at their design rate to work correctly.
Don't get me wrong; I'm all for ditching the 24 Hz rate for movies -- that's much too slow. But 160 Hz frame rates are just silly, in the same way that 96 kHz audio sampling is silly -- unless you're going to do some sort of re-sampling or conversion it's just extra noise and extra data with no practical improvement in quality.
Also, the reason people like 120 Hz LCDs is not because they have a high refresh rate -- unless you're doing 3D or the like (which in most designs effectively halves the frame rate) there's little use for the 120 Hz refresh -- it's because 120 Hz is an integer multiple of all the common video rates so you can display most input types frame-for-frame without any resampling or desync.
So your explanation is that Apple has a dominate position because they have a dominate position. That makes perfect sense, unless there was some point in the past when Apple was near failure, had virtually no capital, and a negligible market share in all their market segments. But if that was ever the case I guess we can just say "magic" got them to where they are, so we don't have to admit anyone ever wanted to buy an Apple product on its merits.
Appliances with heavy compute loads typically have dedicated hardware (or at least an FPGA) to do their primary task -- your TV almost certainly does demuxing, MPEG decoding, and AC3 decoding outside the main CPU. So even assuming a poorly written software the hardware design does quite a bit to protect you from inline attacks.
You'd probably have better luck attacking something like the closed-caption system, or the virtual channel number or the like. That stuff is low-bandwidth enough that it may happen on the main CPU.
If you licensed your work to distributers that license would typically include a prohibition on sale outside their designated market, and a guarantee that you would not license your work to other distributers in the same market -- without those limitations you'd have trouble getting distributers to accept the contract -- and you could sue the distributer for violating their licensing agreement.
Also, this kid is not licensing a work for reproduction, he's buying finished goods. He has no agreement with the copyright holder.
The only "security" NAT provides is *exactly* the same as a stateful firewall. No more, no less. It makes no sense to talk about NAT providing some different kind or amount of security than a stateful firewall.
There are all sorts of IPv6->IPv4 proxies available. Virtually every load-balancing appliance and proxy software project with any IPv6 support provides such capabilities. All you need to make your IPv6-only internal network compatible with an IPv4-only website, or visa versa, is a copy of squid. Plus no one is suggesting that IPv4 should be shut off immediately when you enable IPv6. Depending on your environment that may make sense, but generally speaking dual-stack configurations are likely to be around for a while, at least on publicly-accessible hosts.
And I'm still not sure what so many people want to do with DHCPv6. Router announcements and default DNS servers cover a very significant portion of DHCP uses under IPv4. There are some things that need additional configuration -- any sort of netboot arrangement for example, probably needs additional configuration data -- but those are all specialized applications, and given self-configured IP networking, quite easy to do without DHCP or at least without DHCP-based address assignment (i.e. just use DHCP for configuration of the non-IP-network parameters). And I have no idea what you mean by "buggy or exploitable" -- both IPv6 stateless autoconfig and DHCPv4 can be disrupted or hijacked by any host on the same broadcast segment, and even at that IPv6 has better recovery modes because the refresh interval is typically orders or magnitude shorter.
That's not a problem with "fly-by-wire systems", that's a problem with "systems". In any related group of components it's possible for a failure in one component to affect other components, even if they are "fully independent". If the FA-18 had totally separate, completely mechanical control systems it would still be possible for one engine to interfere with the other, if for no reason other than their physical proximity -- if a throttle cable snapped it could become engaged with the rudder cable, or the other throttle cable, or short out the navigational lights.
A) Because a warrant has always been needed to follow someone on private property. Unless your cell phone knows to stop sending location data to the cops as soon as you walk out of public view then it's a new power that the cops didn't have before, to observe your actions when you have a reasonable expectation of privacy.
B) Because the effort required to physically follow someone acts as a balance; the labor costs associated with manually tracking a person discourage the police from engaging in widespread or long-term tracking. It could still be done if the police thought it was worth the resources, but it's not something they could do routinely or for large groups of people. However, using cell-phone location data, the police could easily track everyone in town, 24/7, indefinitely, with very little effort or cost, and can obtain such tracking data retroactively -- they don't even need to start tracking you, they can search your location history after the fact. Both those changes represent a significant increase in police power with respect to physically tailing someone.
The color of my bathroom tiles is not a matter for state law. I don't see why it follows that my tiles are therefore a matter for federal law.
I'm also not sure why you think airports aren't subject to state/local law. Try building an airport in violation of local zoning laws and see how that works out for you.
The constitution does not grant any rights to anyone. My rights are inherent; in order to form a more perfect union I choose to relinquish some of those right to the government. The constitution details that delegation of rights to the government; I retain all other rights without exception or limitation.
The system needs to be adjusted if merchants want to ensure they're processing a PIN-verified transaction, as opposed to an unauthenticated transaction. It doesn't make the card inherently insecure -- you can't generate PIN-verified transaction using this method -- but it does open up the merchant for chargebacks because they didn't require a PIN. And if your card allows non-PIN transactions it could be stolen and used without the PIN.
There are a variety of solutions. The technical one is to have the payment processor send back terminal-verifiable data about the type of transaction, so the card can't lie to the terminal. But an easy workaround for a merchants and cardholders would be to have their payment processor refuse any non-PIN transactions; if only PIN-authneticated transactions are allowed this flaw becomes meaningless.
They tell parents here to submit their children's fingerprints (and DNA), claiming it will be useful should their child go missing. And I agree it might be -- if they find a child's arm somewhere fingerprints would sure be handy in finding the deceased's next of kin. But it's clearly not useful in any significant number of cases involving live missing children (unless those fingerprints are discovered in the investigation of an unrelated crime, presumably one committed by the child) -- it's just a scam to get worried parents to submit their children's information into the database.
Honestly I'd probably be willing to submit my fingerprints to the government if we could get an actual scientific study of fingerprint uniqueness and the reliability of various collection and matching techniques. I'm not disputing that fingerprints are fairly unique, I just don't think we should send people to jail based on the completely subjective but still somehow "expert" opinion of a fingerprint examiner who uses a process that's demonstrably unreliable.
Not that it significantly changes your point, but HIPAA (enacted in 1996) already limited preexisting condition exclusions on group health plans to a maximum of 18 months in all cases, 12 months for anyone enrolling on-time, and eliminated them completely for people that held insurance for that period (12 or 18 months) without a lapse of more than 63 days. So it would certainly have been a hassle, but it wouldn't have "kept her from ever having medical insurance again".
It's not the same China. The government that we saved in WWII lost control of the mainland in 1949. The government that we saved is now commonly known as Taiwan, and in comparison to the PRC they are quite friendly.
"Smart Quotes" is a feature of MS Word that automatically translates straight quotes to directional quotes. But the actual directional quote characters are not new; they aren't part of ASCII (mostly because typewriter designers wanted to save a key) but they're available in windows-1252 if you're willing to press the right keys to show them, and windows-1252 was most definitely available in 1994.
Most reactors in the UK were built without any secondary containment -- even at the time they were built they knew it was dangerous, but they did it anyway. It's really not fair to compare them to any of the more reasonable designs, including similarly aged US reactors.
As for physical protection of these small reactors, the plan is simply to bury them. It's really hard to smash a car or plane into something that doesn't start until 6' under the local terrain.
And I'm not sure what your logistical concerns are beyond the installation of any sort industrial equipment. Power companies (among many others) already have a huge amount of infrastructure in urban areas and seem to be able to install, fuel, maintain and uninstalled those devices without too much double.
Did you intentionally reply to something other than what you quoted? What evidence of ad-hoc WiFi would you find on visual inspection? What evidence of Bluetooth tethering or a WiFi hotspot would you find on visual inspection?
Adjusting premiums to match individual risk does not eliminate the fundamental insurance benefits of risk and capital pooling -- you still get to free up all the capital you'd need to self-insure by pooling premiums from all policyholders, even if those policies have difference prices. If anything accurate risk assessment and pricing makes insurance more efficient; if risk is inaccurately estimated the insurance company itself takes on more risk and must charge a higher margin to justify the cost of that risk.
That's not to say there aren't privacy implications, but I don't see the financial downside to better risk assessments with respect to insurance.
Slashdot Mirror
Get a CRT that's designed for the refresh rate you run it, rather than the one with the fastest phosphors, at and you won't need such ridiculous frame rates. 100+ Hz video sample rates are as useless as 96 kHz audio sample rates.
So what you're saying is your phosphors were too fast to drive any reasonable refresh rate, so you wasted a bunch of processing power driving the screen at 160 Hz?
Multi-sync CRTs were a terrible plan; there is a reason they never caught on in real video/movie production. I understand why they happened -- they're great for compatibility and idiot-proof setup, and at the time on-board resampling was not cost effective -- but in terms of video quality it's a bad time. If the screen isn't going to ghost at 160 Hz it needs to have *fast* phosphors. Which means if you drive it at 75 Hz, which is plenty fast for almost any human use, it's going to be dim and flickery. You can pretend to adjust for that by driving the gun at a different intensity scale for different refresh rates, but it's a hack; CRTs really need to be driven at their design rate to work correctly.
Don't get me wrong; I'm all for ditching the 24 Hz rate for movies -- that's much too slow. But 160 Hz frame rates are just silly, in the same way that 96 kHz audio sampling is silly -- unless you're going to do some sort of re-sampling or conversion it's just extra noise and extra data with no practical improvement in quality.
Also, the reason people like 120 Hz LCDs is not because they have a high refresh rate -- unless you're doing 3D or the like (which in most designs effectively halves the frame rate) there's little use for the 120 Hz refresh -- it's because 120 Hz is an integer multiple of all the common video rates so you can display most input types frame-for-frame without any resampling or desync.
So your explanation is that Apple has a dominate position because they have a dominate position. That makes perfect sense, unless there was some point in the past when Apple was near failure, had virtually no capital, and a negligible market share in all their market segments. But if that was ever the case I guess we can just say "magic" got them to where they are, so we don't have to admit anyone ever wanted to buy an Apple product on its merits.
About 47 times as difficult as it is to Google "barcode generator" and print out a new piece of paper with a new flight number barcode on it.
Why are you letting felons register to vote? And how would an ID requirement stop them? Do they get special passports that say "felon" on the cover?
Appliances with heavy compute loads typically have dedicated hardware (or at least an FPGA) to do their primary task -- your TV almost certainly does demuxing, MPEG decoding, and AC3 decoding outside the main CPU. So even assuming a poorly written software the hardware design does quite a bit to protect you from inline attacks.
You'd probably have better luck attacking something like the closed-caption system, or the virtual channel number or the like. That stuff is low-bandwidth enough that it may happen on the main CPU.
If you licensed your work to distributers that license would typically include a prohibition on sale outside their designated market, and a guarantee that you would not license your work to other distributers in the same market -- without those limitations you'd have trouble getting distributers to accept the contract -- and you could sue the distributer for violating their licensing agreement.
Also, this kid is not licensing a work for reproduction, he's buying finished goods. He has no agreement with the copyright holder.
The only "security" NAT provides is *exactly* the same as a stateful firewall. No more, no less. It makes no sense to talk about NAT providing some different kind or amount of security than a stateful firewall.
There are all sorts of IPv6->IPv4 proxies available. Virtually every load-balancing appliance and proxy software project with any IPv6 support provides such capabilities. All you need to make your IPv6-only internal network compatible with an IPv4-only website, or visa versa, is a copy of squid. Plus no one is suggesting that IPv4 should be shut off immediately when you enable IPv6. Depending on your environment that may make sense, but generally speaking dual-stack configurations are likely to be around for a while, at least on publicly-accessible hosts.
And I'm still not sure what so many people want to do with DHCPv6. Router announcements and default DNS servers cover a very significant portion of DHCP uses under IPv4. There are some things that need additional configuration -- any sort of netboot arrangement for example, probably needs additional configuration data -- but those are all specialized applications, and given self-configured IP networking, quite easy to do without DHCP or at least without DHCP-based address assignment (i.e. just use DHCP for configuration of the non-IP-network parameters). And I have no idea what you mean by "buggy or exploitable" -- both IPv6 stateless autoconfig and DHCPv4 can be disrupted or hijacked by any host on the same broadcast segment, and even at that IPv6 has better recovery modes because the refresh interval is typically orders or magnitude shorter.
Because the sequence number is part of the encrypted payload, and already-seen sequences do not update the state.
That's not a problem with "fly-by-wire systems", that's a problem with "systems". In any related group of components it's possible for a failure in one component to affect other components, even if they are "fully independent". If the FA-18 had totally separate, completely mechanical control systems it would still be possible for one engine to interfere with the other, if for no reason other than their physical proximity -- if a throttle cable snapped it could become engaged with the rudder cable, or the other throttle cable, or short out the navigational lights.
A) Because a warrant has always been needed to follow someone on private property. Unless your cell phone knows to stop sending location data to the cops as soon as you walk out of public view then it's a new power that the cops didn't have before, to observe your actions when you have a reasonable expectation of privacy.
B) Because the effort required to physically follow someone acts as a balance; the labor costs associated with manually tracking a person discourage the police from engaging in widespread or long-term tracking. It could still be done if the police thought it was worth the resources, but it's not something they could do routinely or for large groups of people. However, using cell-phone location data, the police could easily track everyone in town, 24/7, indefinitely, with very little effort or cost, and can obtain such tracking data retroactively -- they don't even need to start tracking you, they can search your location history after the fact. Both those changes represent a significant increase in police power with respect to physically tailing someone.
It's good to know that "natural" sources can't result in an overdose.
The color of my bathroom tiles is not a matter for state law. I don't see why it follows that my tiles are therefore a matter for federal law.
I'm also not sure why you think airports aren't subject to state/local law. Try building an airport in violation of local zoning laws and see how that works out for you.
The constitution does not grant any rights to anyone. My rights are inherent; in order to form a more perfect union I choose to relinquish some of those right to the government. The constitution details that delegation of rights to the government; I retain all other rights without exception or limitation.
The system needs to be adjusted if merchants want to ensure they're processing a PIN-verified transaction, as opposed to an unauthenticated transaction. It doesn't make the card inherently insecure -- you can't generate PIN-verified transaction using this method -- but it does open up the merchant for chargebacks because they didn't require a PIN. And if your card allows non-PIN transactions it could be stolen and used without the PIN.
There are a variety of solutions. The technical one is to have the payment processor send back terminal-verifiable data about the type of transaction, so the card can't lie to the terminal. But an easy workaround for a merchants and cardholders would be to have their payment processor refuse any non-PIN transactions; if only PIN-authneticated transactions are allowed this flaw becomes meaningless.
They tell parents here to submit their children's fingerprints (and DNA), claiming it will be useful should their child go missing. And I agree it might be -- if they find a child's arm somewhere fingerprints would sure be handy in finding the deceased's next of kin. But it's clearly not useful in any significant number of cases involving live missing children (unless those fingerprints are discovered in the investigation of an unrelated crime, presumably one committed by the child) -- it's just a scam to get worried parents to submit their children's information into the database.
Honestly I'd probably be willing to submit my fingerprints to the government if we could get an actual scientific study of fingerprint uniqueness and the reliability of various collection and matching techniques. I'm not disputing that fingerprints are fairly unique, I just don't think we should send people to jail based on the completely subjective but still somehow "expert" opinion of a fingerprint examiner who uses a process that's demonstrably unreliable.
Not that it significantly changes your point, but HIPAA (enacted in 1996) already limited preexisting condition exclusions on group health plans to a maximum of 18 months in all cases, 12 months for anyone enrolling on-time, and eliminated them completely for people that held insurance for that period (12 or 18 months) without a lapse of more than 63 days. So it would certainly have been a hassle, but it wouldn't have "kept her from ever having medical insurance again".
So what you're saying is this changes nothing with respect to the security of printed documents.
Exactly what do you think is currently stopping people from selling their vote?
It's not the same China. The government that we saved in WWII lost control of the mainland in 1949. The government that we saved is now commonly known as Taiwan, and in comparison to the PRC they are quite friendly.
"Smart Quotes" is a feature of MS Word that automatically translates straight quotes to directional quotes. But the actual directional quote characters are not new; they aren't part of ASCII (mostly because typewriter designers wanted to save a key) but they're available in windows-1252 if you're willing to press the right keys to show them, and windows-1252 was most definitely available in 1994.
Most reactors in the UK were built without any secondary containment -- even at the time they were built they knew it was dangerous, but they did it anyway. It's really not fair to compare them to any of the more reasonable designs, including similarly aged US reactors.
As for physical protection of these small reactors, the plan is simply to bury them. It's really hard to smash a car or plane into something that doesn't start until 6' under the local terrain.
And I'm not sure what your logistical concerns are beyond the installation of any sort industrial equipment. Power companies (among many others) already have a huge amount of infrastructure in urban areas and seem to be able to install, fuel, maintain and uninstalled those devices without too much double.
Yes, since they use exactly the same process at all points past the "fuel->heat" stage. But you get more attention if you say "nuke" in the headline.
Did you intentionally reply to something other than what you quoted? What evidence of ad-hoc WiFi would you find on visual inspection? What evidence of Bluetooth tethering or a WiFi hotspot would you find on visual inspection?
Adjusting premiums to match individual risk does not eliminate the fundamental insurance benefits of risk and capital pooling -- you still get to free up all the capital you'd need to self-insure by pooling premiums from all policyholders, even if those policies have difference prices. If anything accurate risk assessment and pricing makes insurance more efficient; if risk is inaccurately estimated the insurance company itself takes on more risk and must charge a higher margin to justify the cost of that risk.
That's not to say there aren't privacy implications, but I don't see the financial downside to better risk assessments with respect to insurance.