In 2004, when color printers were still somewhat novel, PCWorld magazine published an article headlined: “Government Uses Color Laser Printer Technology to Track Documents.”
It was one of the first news reports on a quiet practice that had been going on for 20 years. It revealed that color printers embed in printed documents coded patterns that contain the printer’s serial number, and the date and time the documents were printed. The patterns are made up of dots, less than a millimeter in diameter and a shade of yellow that, when placed on a white background, cannot be detected by the naked eye.
Continue reading Computer printers have been quietly embedding tracking codes in documents for decades
This is good news for many that could only get a connection less than 10Mbps down.
The FCC’s release goes to say that:
Rural Consumers Must Receive Broadband Delivering At Least 10 Mbps Downloads, 1 Mbps Uploads from Providers Who Benefit from Connect America Support.
Congress directed the FCC to make available in rural areas communications services that are reasonably comparable to those in urban areas. Increasing the Connect America speed requirement means that rural Americans, like urban Americans, can tap the benefits provided by broadband through faster web downloads, improved video streaming, and service capable of supporting multiple users in a household.
AT&T and Verizon have both pleaded with the FCC to keep the definition of ‘broadband’ locked at the 4:1 threshold.
“Given the pace at which the industry is investing in advanced capabilities, there is no present need to redefine ‘advanced’ capabilities,” wrote AT&T. “Consumer behavior strongly reinforces the conclusion that a 10Mbps service exceeds what many Americans need today to enable basic, high-quality transmissions,” AT&T wrote later in its filing. Verizon made similar arguments.
This issue has been recorded as being a Windows issue but I have been seeing this on Mac as well. Will have to check on it and see how to test this on my machine.
There is a serious bug in Chrome that causes the browser to wake up the CPU as many as 1,000 times per second even when idle, thanks to the system clock tick rate being set to 1.00ms by Chrome. This is many times more than the 64 times per second usually observed with the Windows default clock tick rate of 15.625ms. Believe it or not, this bug has been known to Google for many years now and they have just recently decided to deal with it.
As noted on code.google.com:
What steps will reproduce the problem?
1. Just open Google Chrome and navigate to a website with any flash content.
2. System clock tick rate is increased to 1ms
3. Close the website or navigate to page without flash content
4. 1ms tick rate is left forever (until browser is closed)
Seems that Goole Chrome has no system clock tick interval management. Just increases it and keeps forever. Keeping tick rate at 1ms is not recommended. See document:
“If the system timer interval is decreased to less than the default, including when an application calls timeBeginPeriod with a resolution of 1 ms, the low-power idle states are ineffective at reducing system power consumption and system battery life suffers. System battery life can be reduced as much as 25 percent, depending on the hardware platform. This is because transitions to and from low-power states incur an energy cost. Therefore, entering and exiting low-power states without spending a minimum amount of time in the low-power states can be more costly than if the system simply remained in the high-power state.”
Currently your options are to star the code tracker here to vote for it’s resolution or use a different browser, we recommend Firefox and check out our fav plugins for it here.
Catch the Google I/O 2014 – Keynote and find out about the latest product and platform innovations at Google.