A better bit would be a Firefox plugin (you can't do greasemonkey, it needs to be lower down) that just strips all references to google adwords, analytics, and doubleclick and replaces them with noops.
Now google can't track you and you don't see the adds.
While the "clickfraud" solution sounds cute, those are easy easy to detect and Google will just ignore those clicks.
Its not "all that to get the OS to run" its "damn, thats an amazing amount of hardware for practically free".
Using a Windows 7 rollout as an excute to S@#)*can all the old hardware can actually save money, because you can set up a new install like this to be very clean to manage, eg, use network booting and TRK to roll out images, etc.
It may make more sense for many businesses to just forklift-upgrade their desktops.
EG, a Intel Atom dual-core, dual-thread-per-core motherboard should be just fine for most business desktops. Yeah, the graphics aren't great, but at 2GB, an 80 GB disk, and a price of a hair over $300 for a complete system, the hardware costs are so dwarfed by software and support costs that just throwing all the old systems out may be cheaper.
Card counting really doesn't work that well in Vegas casinos unless you go with a distributed ring: its pretty obvious when an individual is card counting, if you miscount slightly the casino ends up winning big, and the casions can really mess you up, from shuffling more to "backrooming" you and intimidating the F-outta you.
But if they start suspecting this (which is easy, its just like detecting any other card counter, and then looking more fully at where you keep your hands), then they can not just backroom you, but through the legal process, make you WISH they'd just have settled for the old days when they'd have shoved your iPhone where the sun don't shine.
For all those who go "But BitTorrent has noninfringing usages", having PirateBay go away will have no effect on the legitimate torrents. Its only the pirate-trackers that will melt down.
So for those interested in legitimate P2P content delivery, this "meltdown" would be a feature, not a bug, because as long as BitTorrent is almost all piracy, it is easier to make a case for traffic management.
The XO is more rugged, but its not really lower power than netbooks. Most Netbooks are using things like the Atom, which is very low power and with sub-ms sleep states. The XO's only real power-advantage is the non-backlight mode on the screen.
Does the mesh networking actually work in the XO? And the mesh networking, how useful is it anyway?
And the XO's G1G1 is hardly "poor economy", its that the XO early adopter-types got them the first go-round (and realized how useless they are: the keyboard is abysmal, the trackpad flakey, and teh software an abomination in the sight of God and Man), so there was no one LEFT in the second.
If someone is doing very high traffic, enough to get into Comcast's temporary "QOS Low" category, they are probably sending and full rate. If you are sending at full rate, the typical end-host NAT and buffering alone will cause bad quality for VoIP (search for VoIP and BitTorrent for a lot of such tales). There is nothing Comcast's network management really does to affect things in this case anyway.
Comcast's network management should only cause additional VoIP issues when the big transfer STOPS and the VoIP call is made within only a few minutes (before the user's link is reclassed back into the "QoS normal" category).
The "arty" is irrelevant. The backgrounds and music are spot on, but ignore the texts and you still have a mindblowingly-cool puzzle-platformer. And I mean MINDBLOWINGLY cool.
The problem is, fuel efficient cars weigh less, and therefore do less damage to the road.
Thus a gasoline tax is actually better at putting many of the costs on the actual source: heavier, less efficient vehicles. As a bonus, fuel taxes encourage smaller, lighter, more efficient cars which are better for society in the long run.
From a developer standpoint, the iPhone is actually damn good.
The dev kit is $0, and a signing key/registration is $100. So the barrier to entry is very VERY low.
And the app store is a godsend. A distribution system where the distributor gets a flat 30% and thats it? And already has a micropayment infrastructure? Thats unheard-of nice.
If you can make a $10 app that sells to just 10,000 people, thats $70K gross revenue to you as a small developer.
A huge part of the reason why people buy the iPhone is the unified user experience. Yes, I'd like a platform that I don't have to pay $100 to develop on...
But my mother doesn't care. she wants a smartphone that "Just Works": its easy to use, with lots of apps.
Apple has provided a great unified user experience on the iPhone, and thats the secret. Its a smartphone my MOTHER can use.
The argument against DNSSEC is that its not needed for securing DNS: that the in-path adversary can F@#)* the final app anyway, unless the final app never trusted the DNS name.
However, there is one key adversary which is in-path on the naming but NOT in path on the data: the DNS recursive resolver. We have seen resolver settings changed by malcode, ISPs wildcarding NXDomain errors, and even DNS service providers (like OpenDNS) man-in-the-middle'ing google!
DNSSEC addresses this adversary, because it is a data integrity protocol. DNSCurve does not: it explicitly trusts the recursive resolver and offers NO security guarentees against this very serious adversary.
Fortunatly, nobody in the DNS world cares about DNScurve, so it will probably just go away.
In fact, DNScurve really shuold be restructured to be a competitor for DTLS, a lightweight datagram communication confidentiality & integrity protocol with a much lower key-setup latency.
A CAPTCHA is only worth $.0025 to break down on the Chinese Turing farms. Thus since a CAPTCHA can only protect something worth $.0025 anyway, making it more crack resistant doesn't buy all that much.
So? Bell's restrictions are inline, not RST injected, while Comcast is dropping their out-of-band method. (and the Sandvine devices Comcast is using can operate inline as well).
And with inline traffic managment, using UDP offers no inherent advantage.
a) Unless you make it TCP fair, you stomp on the user's OWN traffic, which is already a big problem for BitTorrent clients which fill up DSL and cable-modem buffers. And if you DO make it fair, then it doesn't matter.
b) It doesn't stop ISP traffic management, it just forces their devices to be inline.
c) The biggest offender, Comcast, is moving away from P2P blocking anyway.
With a conventional PKI for your SSL certificates, Verisign or the other CA gets a cut for EVERY server.
With DNSSEC, the "CA" only gets a cut per domain. Thus DNSSEC can be used to offer key distribution with far less cost, once the root and the TLDs start signing records.
The google service is designed to minimize privacy leaks. It downloads a coarse-hashcheck database (so Google learns nothing). And then if something hits, it queries a detailed hash.
So unless you get a match on the coarse-hash database, Google learns NOTHING. And google only learns a hash if it matches, which is not very useful, AND google doesn't store this information unless it is a match with their detailed database.
There are enough cases, eg, NebuAdd, NX-domain wildcarding, P2P traffic disruption, where the ISP gains a large net benefit from behaving in a non-neutral manner, and as high-bandwidth ISPs are a duopoly at best for most individuals, unless you can reveal their practices AND the threat of regulation & marketplace rebellion, the net becomes unneutral.
Remember, the "market will take care of itself" was also promulgated by CATO in respect to Wall Street, and we know how well that worked out.
Slashdot Mirror
A better bit would be a Firefox plugin (you can't do greasemonkey, it needs to be lower down) that just strips all references to google adwords, analytics, and doubleclick and replaces them with noops.
Now google can't track you and you don't see the adds.
While the "clickfraud" solution sounds cute, those are easy easy to detect and Google will just ignore those clicks.
The OLPC project is dying. Four years ago, you didn't have the netbooks. Now you do.
Shifting to ARM will simply ensure the death of the OLPC project, because being able to run real windows is an underappreciated benefit of x86.
True, posix says that unless you do a fsync(), the file might never be written to disk before the system crashes. But Whiskey-tango-Foxtrot?
Whats wrong with "After a file is closed, its synced to disk"?!?
I tried watching Fringe. It was a crappy low-rent X-files ripoff with little redeaming value.
I tried watching Dollhouse. It was a crappy creepy low-rent show about mind-wiped prostitutes...
Its not "all that to get the OS to run" its "damn, thats an amazing amount of hardware for practically free ".
Using a Windows 7 rollout as an excute to S@#)*can all the old hardware can actually save money, because you can set up a new install like this to be very clean to manage, eg, use network booting and TRK to roll out images, etc.
It may make more sense for many businesses to just forklift-upgrade their desktops.
EG, a Intel Atom dual-core, dual-thread-per-core motherboard should be just fine for most business desktops. Yeah, the graphics aren't great, but at 2GB, an 80 GB disk, and a price of a hair over $300 for a complete system, the hardware costs are so dwarfed by software and support costs that just throwing all the old systems out may be cheaper.
Card counting really doesn't work that well in Vegas casinos unless you go with a distributed ring: its pretty obvious when an individual is card counting, if you miscount slightly the casino ends up winning big, and the casions can really mess you up, from shuffling more to "backrooming" you and intimidating the F-outta you.
But if they start suspecting this (which is easy, its just like detecting any other card counter, and then looking more fully at where you keep your hands), then they can not just backroom you, but through the legal process, make you WISH they'd just have settled for the old days when they'd have shoved your iPhone where the sun don't shine.
For all those who go "But BitTorrent has noninfringing usages", having PirateBay go away will have no effect on the legitimate torrents. Its only the pirate-trackers that will melt down.
So for those interested in legitimate P2P content delivery, this "meltdown" would be a feature, not a bug, because as long as BitTorrent is almost all piracy, it is easier to make a case for traffic management.
The XO is more rugged, but its not really lower power than netbooks. Most Netbooks are using things like the Atom, which is very low power and with sub-ms sleep states. The XO's only real power-advantage is the non-backlight mode on the screen.
Does the mesh networking actually work in the XO? And the mesh networking, how useful is it anyway?
And the XO's G1G1 is hardly "poor economy", its that the XO early adopter-types got them the first go-round (and realized how useless they are: the keyboard is abysmal, the trackpad flakey, and teh software an abomination in the sight of God and Man), so there was no one LEFT in the second.
Lets say its a tesla-equivelent battery pack, a nice 50 kWH.
To charge in 10 minutes, you'd need to shove in power at 300 kW!
At 220V, that means you'd need 1300 A of current!?!
If someone is doing very high traffic, enough to get into Comcast's temporary "QOS Low" category, they are probably sending and full rate. If you are sending at full rate, the typical end-host NAT and buffering alone will cause bad quality for VoIP (search for VoIP and BitTorrent for a lot of such tales). There is nothing Comcast's network management really does to affect things in this case anyway.
Comcast's network management should only cause additional VoIP issues when the big transfer STOPS and the VoIP call is made within only a few minutes (before the user's link is reclassed back into the "QoS normal" category).
The Knights Armaments page on both the software and the mounting system.
Really allows you to reach out and touch someone with your iphone.
The "arty" is irrelevant. The backgrounds and music are spot on, but ignore the texts and you still have a mindblowingly-cool puzzle-platformer. And I mean MINDBLOWINGLY cool.
The problem is, fuel efficient cars weigh less, and therefore do less damage to the road.
Thus a gasoline tax is actually better at putting many of the costs on the actual source: heavier, less efficient vehicles. As a bonus, fuel taxes encourage smaller, lighter, more efficient cars which are better for society in the long run.
http://www.penny-arcade.com/comic/2008/12/12/
Makes you want to rush out and get a PS3.... NOT.
From a developer standpoint, the iPhone is actually damn good.
The dev kit is $0, and a signing key/registration is $100. So the barrier to entry is very VERY low.
And the app store is a godsend. A distribution system where the distributor gets a flat 30% and thats it? And already has a micropayment infrastructure? Thats unheard-of nice.
If you can make a $10 app that sells to just 10,000 people, thats $70K gross revenue to you as a small developer.
A huge part of the reason why people buy the iPhone is the unified user experience. Yes, I'd like a platform that I don't have to pay $100 to develop on...
But my mother doesn't care. she wants a smartphone that "Just Works": its easy to use, with lots of apps.
Apple has provided a great unified user experience on the iPhone, and thats the secret. Its a smartphone my MOTHER can use.
Opening up the platform wouldn't help.
I think you can use Unbound as a stub resolver.
The argument against DNSSEC is that its not needed for securing DNS: that the in-path adversary can F@#)* the final app anyway, unless the final app never trusted the DNS name.
However, there is one key adversary which is in-path on the naming but NOT in path on the data: the DNS recursive resolver. We have seen resolver settings changed by malcode, ISPs wildcarding NXDomain errors, and even DNS service providers (like OpenDNS) man-in-the-middle'ing google!
DNSSEC addresses this adversary, because it is a data integrity protocol. DNSCurve does not: it explicitly trusts the recursive resolver and offers NO security guarentees against this very serious adversary.
Fortunatly, nobody in the DNS world cares about DNScurve, so it will probably just go away.
In fact, DNScurve really shuold be restructured to be a competitor for DTLS, a lightweight datagram communication confidentiality & integrity protocol with a much lower key-setup latency.
A CAPTCHA is only worth $.0025 to break down on the Chinese Turing farms. Thus since a CAPTCHA can only protect something worth $.0025 anyway, making it more crack resistant doesn't buy all that much.
So? Bell's restrictions are inline, not RST injected, while Comcast is dropping their out-of-band method. (and the Sandvine devices Comcast is using can operate inline as well).
And with inline traffic managment, using UDP offers no inherent advantage.
The problem with UDP rate control is:
a) Unless you make it TCP fair, you stomp on the user's OWN traffic, which is already a big problem for BitTorrent clients which fill up DSL and cable-modem buffers. And if you DO make it fair, then it doesn't matter.
b) It doesn't stop ISP traffic management, it just forces their devices to be inline.
c) The biggest offender, Comcast, is moving away from P2P blocking anyway.
With a conventional PKI for your SSL certificates, Verisign or the other CA gets a cut for EVERY server.
With DNSSEC, the "CA" only gets a cut per domain. Thus DNSSEC can be used to offer key distribution with far less cost, once the root and the TLDs start signing records.
(Not an original argument, but I agree with it.)
The google service is designed to minimize privacy leaks. It downloads a coarse-hashcheck database (so Google learns nothing). And then if something hits, it queries a detailed hash.
So unless you get a match on the coarse-hash database, Google learns NOTHING. And google only learns a hash if it matches, which is not very useful, AND google doesn't store this information unless it is a match with their detailed database.
There are enough cases, eg, NebuAdd, NX-domain wildcarding, P2P traffic disruption, where the ISP gains a large net benefit from behaving in a non-neutral manner, and as high-bandwidth ISPs are a duopoly at best for most individuals, unless you can reveal their practices AND the threat of regulation & marketplace rebellion, the net becomes unneutral.
Remember, the "market will take care of itself" was also promulgated by CATO in respect to Wall Street, and we know how well that worked out.