4) Martial Law. Wha? Nope. It's real. President now has the authority to declare martial law for... "Other Reasons" (unspecified). It's in the law!
Citation? I checked against Cornell's US Code database and found only five passages that contain the phrase "martial law." Two pertain to China (Title 12, 635 and Title 22, 2151), one to suspension of aid to Eastern Europe (Title 22, 5491), and two to governors of Guam and the US Virgin Islands (Title 48, 1422 and 1581).
Want to earn some money? Nope the IRS will take a bunch of your income, although there is no LAW permitting them to do it. (Look It Up)
There's a law authorizing regulations authorizing what the IRS does. You can read the IRS regulations in the US Code of Federal Regulations, specifically Section 26. The laws that the IRS enforces are in Title 26 of the US Code.
6) Concentration camps. Excuse me, what? Yes, the USA now has about 800 concentration camps dotting the countryside.
Again, citation? I remember this being talked about on Cipherpunks years ago, and I shot it down then with satellite pictures courtesy of the then-fledgling Microsoft satellite photo system, not to mention that I was familiar with some of the areas in question in SoCal and that many of the cross streets identified ran parallel for miles -- sometimes miles apart -- and never intersected once.
My histories tend to not be more than about ten pages or so per tab, and I frequently close out tabs as I finish with them, even if they were only used for one story. What I will do often on a site is Ctrl-click on multiple stories on a page and then read them in sequence, closing out each story as I finish with it. It's my belief that closing that page should result in all memory associated with that tab being freed, but when testing that by watching memory use as I close the tabs, there is little or no change in the overall memory usage, and that strikes me as something that should be addressed.
There may be a fix (I think I know what you mean with the in-memory caching), but I'm not going to do that because when in forums, I will often jump back several pages, and I don't need or want them reloading just going back or forward. Besides, if I have to look up a method to do it, then it's not something that I'm likely to want to be sending my parents through, and that's an important point, especially since they have much older, slower systems than do I.
I'll add LeakMonitor in and have a look on my next restart. Thanks for that.
I don't run NoScript, because I almost always leave the pages with default settings, and even in those cases where I'd want to block functionality, I'd probably lose out on the leak you mention because they'd be relatively rare.
I don't install Flash in Firefox, but I routinely reach 200MB use by the end of the day with an average of about four tabs open; I've only had it running today for about 2.5 hours and it's at 135MB. I do have 23 add-ons installed, but many of them are low-usage (Add-N-Edit Cookies, BugMeNot, ColorZilla, Copy Plain Text, IdentitySelector, IETab, Location Navigator, MeasureIt, and SecureWire Web Relay [for SSL VPN]). Even those that get heavier usage (AIOS, DownThemAll!, Forecastfox Enhanced, Gmail Manager, Google Toolbar, Slashdotter) shouldn't be eating up gobs of memory. I routinely run two or three virtual machines at a time on this 2GB notebook, so Firefox isn't helping things there, even with swapping enabled. Even disabling the add-ons doesn't save me from enormous memory usage by the end of the day.
I'd watch CSPAN if there were a chance of this happening during debates now. Instead we either get $MAJORITY_PARTY bending the rules into pretzels to prevent the other side from getting their fair say, or we get both parties working together to further sweeten their little corners of the world.
Would it be difficult to do alternating line shading using CSS, with automatic reflow as the window is rescaled in size? Alternating 0% and 10% shading may be subtle enough to allow proper eye tracking while discouraging uptake of other information.
A completely non-scientific test with my eyes and a stopwatch after reading both paragraphs several times but paying attention to read every word resulted in reading the normal paragraph form in ~12.6 seconds, and the lengthened form that you posted in ~10.6 seconds.
Of course, this may be completely out of whack. However, the flow felt more intuitive. Maybe the Japanese were onto something with the vertical writing.
Indeed, the turnaround time from patch release to first exploit is now well under 24 hours for many of them, and exploit code is often out the very same afternoon. This makes it that much more difficult to safeguard the enterprise.
Every company I've been at over the last decade has been stretched on resources, and my current employer much moreso than any before. While I have some additional control over systems that are my responsibility, and will apply updates as I find them, we have numerous fragile applications that have to be carefully managed in shutdown and restart, and they can take from five to fifteen minutes per system of engineer time in coaxing through a proper patch, shutdown, and restart. Spread this over several hundred systems, and that's a lot of time that engineers don't often have -- and usually after hours, since most of the systems are not permitted to be shut down during business hours. We're looking at solutions like WSUS, but the ironic twist is that no one has the time to devote to it to ensure that it's properly done.
There are much larger networks than mine, and some of them even more fragile. Microsoft was blasted for releasing scattershot patches before, and since the change, they've been blasted for releasing them once a month (with the occasional super-critical patch released off-schedule). No matter which way they do things, they're going to have half of the industry mad at them. Better to go with the one that makes their lives easier.
I still sort of tepidly back the idea, though not for national security purposes, since that will be a minor effect, if there is any at all. Instead, the safeguards proposed seem to make identity theft more difficult for both con artists and illegal immigrants. (Of course, there's the problem that the state IDs under REAL ID then become even more trusted, and a successfully forged ID then provides even more access.)
However, in the last year, I've started to root for the states, not because I've turned against the idea of a national ID card standard, but rather because I support states' rights more. I would love to see RealID work with all of about eight states, forcing the federal government to back down on the issue since they can't force it. It's time that the states reasserted themselves a bit, and forced Congress and the White House to face up to their limitations.
Infiltration can take years to do effectively, and has its limits -- there are some activities which are forbidden to any US agent even under the most dire of circumstances, which may limit how far the person can go in moving up through the ranks, and there is always a limit to the manpower available. Bribing someone on the inside can take weeks or less, and has fewer limitations. Both have their place. However, since Congress decided that money could not be sent to known murderers or certain other undesirables, it put a serious cramp in the abilities of the intelligence divisions.
If you put a complete bar on it, then you get no human intelligence. Corruption is a risk that can be mitigated through careful inspection of your people; lack of HUMINT virtually guarantees blindness as to the inner workings of an enemy organization.
Part of that blame goes to Congress, who didn't like who the agents on the ground were hanging out with. They forbade the trading of money for tips and information to those who were significant parts of criminal enterprises, so they couldn't give, say, $50,000 for information on where drug lords were hiding out or $10,000 for a tip on where some shoulder-fired SAMs might be delivered next week if the person telling you might be a drug trafficker or be involved in some jihad-related mayhem himself. The net effect was forcing the intelligence community to pay nice guys -- who rarely have good information -- or rely on their electronic intelligence -- and satellites are very bad at hearing whispers inside a crowded bar.
That's not to say that the various intelligence groups didn't miss the big picture on their own, but part of the blame does deserve to be elsewhere.
Vonage does provide some very clear warnings about e911, and the need to fill out and update the address information. When they were mandated to support e911, they sent out numerous very clear, very stern warnings about the requirements, and I still see them from time to time. They don't get ominous, but they explain that the service is limited in accuracy to what the customer provides, and that the service relies on the status of the customer's Internet uplink. I believe I've seen at least one situation where they recommend a standard land-line if there is a situation where emergency services need to be available at all times, such as with an elderly or infirm resident.
I liked the old AT&T. I had local service with them for several years, moving it to two new apartments. Then SBC took over, and in a matter of a few months, they had disconnected my service for "abandonment" even though they had talked to me 45 minutes after the alleged abandonment call took place. Since I already had Vonage for my long-distance service and kept the land-line around primarily for guaranteed 911 availability, I simply chose to give up the insurance and switch everyone to my Vonage number (even after AT&T offered to reconnect my service for free), since AT&T refused to reinstate my old number and I had to hand out a different number anyway.
Perhaps it's published as a means of trying to get an explanation for the mechanism. Sort of like saying, "OK, we see this, and we can't think of any other reason why this might be happening, but we're scratching our heads bald, so anyone with an idea, please speak up."
I'm happy to give them a voting representative in Congress if and when the area that they are in is declared a state, or when the Constitution is changed to provide that DC gets voting representation. The Constitution does not provide for DC to get a representative in the House or any Senators, and until changed it should not.
I'd be happier making DC a no-residence zone, though it's too late for that, considering the number of people who live there.
Oranges do have edible skin. I've had coworkers in the past that eat every last bit of citrus fruit (oranges, tangerines, grapefruit), which I found odd, but they never keeled over and died. The only use I've ever made of orange rinds is using the zest in the occasional baked chicken.
For that matter, seeing something marked as cloned may get me to opt in. Products that are made to be of higher quality may attract my attention faster, especially since I've been avoiding most red meat for health reasons. I'd like to be able to go back to eating a little more of it if it can be shown to be very lean and have certain other characteristics more likely to be found in poultry, simply because I like the taste of a nice steak.
I've walked in Los Angeles, as well as in Chicago. In Los Angeles, stepping out on the road even in a crosswalk when you have the walk signal is essentially betting your life on the skills and hubris of the drivers of all kinds of vehicles -- private cars, vans, trucks, public transit buses, whatever. In Chicago, it takes some practice to get in the general hang of things, but jaywalkers and vehicles have what seems to be a symbiotic rhythm, with far less apparent danger in Chicago than in LA.
Even the police take note of this. In LA, you can get a fairly large fine for jaywalking, while twice in a matter of a few days, I saw people (one pair, one group of about ten) cross in front of a CPD cruiser and the cops didn't show any suggestion that they noticed. The cruisers never had to slow down below their speed (probably around 30mph) because they crossed early and quickly enough, but it was still very puzzling to me as someone from SoCal who is not used to cars and people working in a synchronous operation.
There seems to be a lively debate on this, and it's never been tested in the courts, but a company with an investment of hundreds of millions of dollars in the technology cannot afford to release the source code to the binary and allow any random person to easily modify the binary to actively interfere in others' transmissions, especially when their software radio is perfectly capable of working in restricted frequencies such as the 4.9GHz range, not to mention potential interference in the radar frequencies that 802.11h was designed to mitigate.
OpenBSD's development staff desires to remain pure in this matter. That is their decision, but they may end up having to make some sacrifices to do so, as might Debian and other projects that refuse to use anything not under clear and accepted open source licenses.
The ability to build a transmitter that can interfere with others does not mean that it's legal, and in fact is expressly illegal in the United States. 47 CFR 15.5b states:
Operation of an intentional, unintentional, or incidental radiator is subject to the conditions that no harmful interference is caused and that interference must be accepted that may be caused by the operation of an authorized radio station, by another intentional or unintentional radiator, by industrial, scientific and medical (ISM) equipment, or by an incidental radiator.
Emphasis added.
I can drive my car the wrong way on the road, but that doesn't make it legal.
Looking around, it seems that Intel released in February a new driver using the d80211 subsystem that does away with the regulatory binary. There's still a binary microcode update that has to be loaded, and it's freely (as in beer) redistributable. I haven't played with it yet, but the initial response seems to be relatively positive.
Ham operators behave because they don't want to lose their license, and Intel and Atheros behave because they don't want to lose their licenses. (There's no license required to operate the devices, but devices have to be certified by the FCC as conforming to regulations.)
So, where's that Free Software Intel wireless chipset driver, then? (Just sayin'...)
That would be right here. Everything non-binary is licensed under either GPLv2 or dual-license BSD/GPLv2, according to the documentation. The binaries are released in that form because they are prohibited by FCC regulations from releasing anything that could be modified by the end user to violate regulatory limits. Exactly the same thing applies to the MADWifi drivers for Atheros, who makes available a binary HAL to the developers.
I start with the presumption of a decent microphone built in, which has been the case for all of my phones, going back to a PacBell Wireless cell nearly a decade ago. Many people around me yell (my coworkers can sometimes be heard from the other side of heavy office doors), and I often ask people to not talk so loudly into their own phones as even at low volumes it hurts my ear, but I try to remain courteous when in the company of others, and not subject them to my conversations.
Slashdot Mirror
4) Martial Law. Wha? Nope. It's real. President now has the authority to declare martial law for... "Other Reasons" (unspecified). It's in the law!
Citation? I checked against Cornell's US Code database and found only five passages that contain the phrase "martial law." Two pertain to China (Title 12, 635 and Title 22, 2151), one to suspension of aid to Eastern Europe (Title 22, 5491), and two to governors of Guam and the US Virgin Islands (Title 48, 1422 and 1581).
Want to earn some money? Nope the IRS will take a bunch of your income, although there is no LAW permitting them to do it. (Look It Up)
There's a law authorizing regulations authorizing what the IRS does. You can read the IRS regulations in the US Code of Federal Regulations, specifically Section 26. The laws that the IRS enforces are in Title 26 of the US Code.
6) Concentration camps. Excuse me, what? Yes, the USA now has about 800 concentration camps dotting the countryside.
Again, citation? I remember this being talked about on Cipherpunks years ago, and I shot it down then with satellite pictures courtesy of the then-fledgling Microsoft satellite photo system, not to mention that I was familiar with some of the areas in question in SoCal and that many of the cross streets identified ran parallel for miles -- sometimes miles apart -- and never intersected once.
My histories tend to not be more than about ten pages or so per tab, and I frequently close out tabs as I finish with them, even if they were only used for one story. What I will do often on a site is Ctrl-click on multiple stories on a page and then read them in sequence, closing out each story as I finish with it. It's my belief that closing that page should result in all memory associated with that tab being freed, but when testing that by watching memory use as I close the tabs, there is little or no change in the overall memory usage, and that strikes me as something that should be addressed.
There may be a fix (I think I know what you mean with the in-memory caching), but I'm not going to do that because when in forums, I will often jump back several pages, and I don't need or want them reloading just going back or forward. Besides, if I have to look up a method to do it, then it's not something that I'm likely to want to be sending my parents through, and that's an important point, especially since they have much older, slower systems than do I.
I'll add LeakMonitor in and have a look on my next restart. Thanks for that.
I don't run NoScript, because I almost always leave the pages with default settings, and even in those cases where I'd want to block functionality, I'd probably lose out on the leak you mention because they'd be relatively rare.
I don't install Flash in Firefox, but I routinely reach 200MB use by the end of the day with an average of about four tabs open; I've only had it running today for about 2.5 hours and it's at 135MB. I do have 23 add-ons installed, but many of them are low-usage (Add-N-Edit Cookies, BugMeNot, ColorZilla, Copy Plain Text, IdentitySelector, IETab, Location Navigator, MeasureIt, and SecureWire Web Relay [for SSL VPN]). Even those that get heavier usage (AIOS, DownThemAll!, Forecastfox Enhanced, Gmail Manager, Google Toolbar, Slashdotter) shouldn't be eating up gobs of memory. I routinely run two or three virtual machines at a time on this 2GB notebook, so Firefox isn't helping things there, even with swapping enabled. Even disabling the add-ons doesn't save me from enormous memory usage by the end of the day.
I'd watch CSPAN if there were a chance of this happening during debates now. Instead we either get $MAJORITY_PARTY bending the rules into pretzels to prevent the other side from getting their fair say, or we get both parties working together to further sweeten their little corners of the world.
Would it be difficult to do alternating line shading using CSS, with automatic reflow as the window is rescaled in size? Alternating 0% and 10% shading may be subtle enough to allow proper eye tracking while discouraging uptake of other information.
A completely non-scientific test with my eyes and a stopwatch after reading both paragraphs several times but paying attention to read every word resulted in reading the normal paragraph form in ~12.6 seconds, and the lengthened form that you posted in ~10.6 seconds.
Of course, this may be completely out of whack. However, the flow felt more intuitive. Maybe the Japanese were onto something with the vertical writing.
Indeed, the turnaround time from patch release to first exploit is now well under 24 hours for many of them, and exploit code is often out the very same afternoon. This makes it that much more difficult to safeguard the enterprise.
Every company I've been at over the last decade has been stretched on resources, and my current employer much moreso than any before. While I have some additional control over systems that are my responsibility, and will apply updates as I find them, we have numerous fragile applications that have to be carefully managed in shutdown and restart, and they can take from five to fifteen minutes per system of engineer time in coaxing through a proper patch, shutdown, and restart. Spread this over several hundred systems, and that's a lot of time that engineers don't often have -- and usually after hours, since most of the systems are not permitted to be shut down during business hours. We're looking at solutions like WSUS, but the ironic twist is that no one has the time to devote to it to ensure that it's properly done.
There are much larger networks than mine, and some of them even more fragile. Microsoft was blasted for releasing scattershot patches before, and since the change, they've been blasted for releasing them once a month (with the occasional super-critical patch released off-schedule). No matter which way they do things, they're going to have half of the industry mad at them. Better to go with the one that makes their lives easier.
I still sort of tepidly back the idea, though not for national security purposes, since that will be a minor effect, if there is any at all. Instead, the safeguards proposed seem to make identity theft more difficult for both con artists and illegal immigrants. (Of course, there's the problem that the state IDs under REAL ID then become even more trusted, and a successfully forged ID then provides even more access.)
However, in the last year, I've started to root for the states, not because I've turned against the idea of a national ID card standard, but rather because I support states' rights more. I would love to see RealID work with all of about eight states, forcing the federal government to back down on the issue since they can't force it. It's time that the states reasserted themselves a bit, and forced Congress and the White House to face up to their limitations.
Infiltration can take years to do effectively, and has its limits -- there are some activities which are forbidden to any US agent even under the most dire of circumstances, which may limit how far the person can go in moving up through the ranks, and there is always a limit to the manpower available. Bribing someone on the inside can take weeks or less, and has fewer limitations. Both have their place. However, since Congress decided that money could not be sent to known murderers or certain other undesirables, it put a serious cramp in the abilities of the intelligence divisions.
If you put a complete bar on it, then you get no human intelligence. Corruption is a risk that can be mitigated through careful inspection of your people; lack of HUMINT virtually guarantees blindness as to the inner workings of an enemy organization.
Part of that blame goes to Congress, who didn't like who the agents on the ground were hanging out with. They forbade the trading of money for tips and information to those who were significant parts of criminal enterprises, so they couldn't give, say, $50,000 for information on where drug lords were hiding out or $10,000 for a tip on where some shoulder-fired SAMs might be delivered next week if the person telling you might be a drug trafficker or be involved in some jihad-related mayhem himself. The net effect was forcing the intelligence community to pay nice guys -- who rarely have good information -- or rely on their electronic intelligence -- and satellites are very bad at hearing whispers inside a crowded bar.
That's not to say that the various intelligence groups didn't miss the big picture on their own, but part of the blame does deserve to be elsewhere.
Vonage does provide some very clear warnings about e911, and the need to fill out and update the address information. When they were mandated to support e911, they sent out numerous very clear, very stern warnings about the requirements, and I still see them from time to time. They don't get ominous, but they explain that the service is limited in accuracy to what the customer provides, and that the service relies on the status of the customer's Internet uplink. I believe I've seen at least one situation where they recommend a standard land-line if there is a situation where emergency services need to be available at all times, such as with an elderly or infirm resident.
I liked the old AT&T. I had local service with them for several years, moving it to two new apartments. Then SBC took over, and in a matter of a few months, they had disconnected my service for "abandonment" even though they had talked to me 45 minutes after the alleged abandonment call took place. Since I already had Vonage for my long-distance service and kept the land-line around primarily for guaranteed 911 availability, I simply chose to give up the insurance and switch everyone to my Vonage number (even after AT&T offered to reconnect my service for free), since AT&T refused to reinstate my old number and I had to hand out a different number anyway.
Perhaps it's published as a means of trying to get an explanation for the mechanism. Sort of like saying, "OK, we see this, and we can't think of any other reason why this might be happening, but we're scratching our heads bald, so anyone with an idea, please speak up."
I'm happy to give them a voting representative in Congress if and when the area that they are in is declared a state, or when the Constitution is changed to provide that DC gets voting representation. The Constitution does not provide for DC to get a representative in the House or any Senators, and until changed it should not.
I'd be happier making DC a no-residence zone, though it's too late for that, considering the number of people who live there.
Oranges do have edible skin. I've had coworkers in the past that eat every last bit of citrus fruit (oranges, tangerines, grapefruit), which I found odd, but they never keeled over and died. The only use I've ever made of orange rinds is using the zest in the occasional baked chicken.
For that matter, seeing something marked as cloned may get me to opt in. Products that are made to be of higher quality may attract my attention faster, especially since I've been avoiding most red meat for health reasons. I'd like to be able to go back to eating a little more of it if it can be shown to be very lean and have certain other characteristics more likely to be found in poultry, simply because I like the taste of a nice steak.
I've walked in Los Angeles, as well as in Chicago. In Los Angeles, stepping out on the road even in a crosswalk when you have the walk signal is essentially betting your life on the skills and hubris of the drivers of all kinds of vehicles -- private cars, vans, trucks, public transit buses, whatever. In Chicago, it takes some practice to get in the general hang of things, but jaywalkers and vehicles have what seems to be a symbiotic rhythm, with far less apparent danger in Chicago than in LA.
Even the police take note of this. In LA, you can get a fairly large fine for jaywalking, while twice in a matter of a few days, I saw people (one pair, one group of about ten) cross in front of a CPD cruiser and the cops didn't show any suggestion that they noticed. The cruisers never had to slow down below their speed (probably around 30mph) because they crossed early and quickly enough, but it was still very puzzling to me as someone from SoCal who is not used to cars and people working in a synchronous operation.
There seems to be a lively debate on this, and it's never been tested in the courts, but a company with an investment of hundreds of millions of dollars in the technology cannot afford to release the source code to the binary and allow any random person to easily modify the binary to actively interfere in others' transmissions, especially when their software radio is perfectly capable of working in restricted frequencies such as the 4.9GHz range, not to mention potential interference in the radar frequencies that 802.11h was designed to mitigate.
OpenBSD's development staff desires to remain pure in this matter. That is their decision, but they may end up having to make some sacrifices to do so, as might Debian and other projects that refuse to use anything not under clear and accepted open source licenses.
The ability to build a transmitter that can interfere with others does not mean that it's legal, and in fact is expressly illegal in the United States. 47 CFR 15.5b states:
Operation of an intentional, unintentional, or incidental radiator is subject to the conditions that no harmful interference is caused and that interference must be accepted that may be caused by the operation of an authorized radio station, by another intentional or unintentional radiator, by industrial, scientific and medical (ISM) equipment, or by an incidental radiator.
Emphasis added.
I can drive my car the wrong way on the road, but that doesn't make it legal.
Looking around, it seems that Intel released in February a new driver using the d80211 subsystem that does away with the regulatory binary. There's still a binary microcode update that has to be loaded, and it's freely (as in beer) redistributable. I haven't played with it yet, but the initial response seems to be relatively positive.
Ham operators behave because they don't want to lose their license, and Intel and Atheros behave because they don't want to lose their licenses. (There's no license required to operate the devices, but devices have to be certified by the FCC as conforming to regulations.)
So, where's that Free Software Intel wireless chipset driver, then? (Just sayin'...)
That would be right here. Everything non-binary is licensed under either GPLv2 or dual-license BSD/GPLv2, according to the documentation. The binaries are released in that form because they are prohibited by FCC regulations from releasing anything that could be modified by the end user to violate regulatory limits. Exactly the same thing applies to the MADWifi drivers for Atheros, who makes available a binary HAL to the developers.
I start with the presumption of a decent microphone built in, which has been the case for all of my phones, going back to a PacBell Wireless cell nearly a decade ago. Many people around me yell (my coworkers can sometimes be heard from the other side of heavy office doors), and I often ask people to not talk so loudly into their own phones as even at low volumes it hurts my ear, but I try to remain courteous when in the company of others, and not subject them to my conversations.