If you don't want google to know you're downloading porn (and exactly what porn you are downloading) (and any warez, etc.) then you'll need to make very sure that you never use a site that uses recapcha. Fucking google.
Just because you release something under a permissive license doesn't mean you have to host the content forever. If people wanted a copy of the content, it's their own responsibility to mirror it.
While there a circuit split exists on the question of warrantless GPS tracking, it has long been settled that what you do on the public road isn't private and there are no protections against monitoring your whereabouts in public.
I think that anyone who thinks there is a single "odds" for people on the earth being hit by this satellite doesn't understand orbital mechanics. Or even sub-orbital ballistics. (E.g. The further you are from the thrower, the lower your odds of being impaled by the lawn dart.)
No, head said his entire cluster has to be booted one at a time. So AMD is better because it uses coreboot rather than UEFI.
If you have an environment that requires that everything goes down together and then comes back up one at a time in order, you've got bigger problems that what code executes at poweron.
The situation described is highly bizarre and would likely benefit from someone with some application architectural expertise.
No this is more like you installing a camera in your bathroom. Then you go on vacation. While you are away some pecker head breaks in, and throws a party. One of the guests uses the bathroom and you put the pictures on the internet. Even though the guest did not break in and the act of the guest using the bathroom has nothing whatsoever to do with the breaking and entering anyway.
They're not doing it to hide your address, that's just an effect of what they are doing. Google's resolvers are nowhere near the querying client. CDN and GeoIP based services are now unable to determine the nearest server based on the IP address of the resolver. Consider: If I am a customer of Xmission and I use Xmission's name servers then I will get directed to an Akamai host that is physically located in Xmission's datacenter and the content will traverse over their LAN. However if I use Google's resolver then I will get directed to an Akamai host that is near Google's resolver rather than near me. So now the content is pulled from somewhere on the otherside of the universe.
You aren't understanding what is going on here. All Google and OpenDNS are doing is providing the authoritative DNS server with the IP address of the client. Google/OpenDNS know nothing about any possible caching or local servers. They are just making it possible for the final DNS server to possibly, assuming that whoever owns the domain you are resolving supports some kind of CDN, send you to a nearby server.
What likely really happened here is this:
Akami: Hey Google! You're compulsion to violate everyone's privacy is fucking up the Internet by breaking all of the CDN/Geo-based services. Google: But... but... we must know everything about everyone otherwise we'll not be able to sell them to our customers. Akami: Whatever dude, you're causing 50% congestion on the backbone links because your shit hides the actual address of the client. Google: Well, we've got sack-fulls of PhDs. We'll find a solution that allows us to keep spying and selling and still allows the CDNs to work. Akami: Look you jackasses, the system that exists today works. Your crap is just causing problems and labor for everyone else. Google: Na-na-na-na-na-na-na-na I can't hear you. Akami: Seriously. You're being a dick. Google: No. We've just invented this awesome thing that is going to Speed-Up! The InterNets! Akami: Jesus Christ! The system that was there before you broke it works. Why the fuck do you have to keep breaking shit? Google: Because we can and people are stupid. And we are rich. So STFU. Akami: Fuck. There's no reasoning with these clowns.
Google could just not provide a service that inserts themselves into the DNS path. The problem isn't "the internet" or DNS, it's that Google's DNS servers have no relationship to the client systems. If people were using DNS servers that had some relationship to their network -- such as the one provided by their IPS -- then this wouldn't be an issue.
Plus not using Google's DNS gives you a little more privacy. Privacy of course being defined as not having every activity you do on the internet being logged by one of Google's many methods of invading your space (DNS, analytics, search, advertising, blogger, etc.)
What we're talking about here is mass buying, sight unseen and throwing the old one (still perfectly good) in the trash.
Um... no. All they have is "Will you buy an iPhone 5?" And 35% said yes. They didn't actually take anyone's money. Consider if I were to ask you this question:
"Will you buy <food item of your choice> from <your normal grocery store> next week?"
You're going to answer yes. Now if you show up and the item is spoiled you're not going to buy it. Because with any question about future events, there is built in caveats. If the iPhone 5 turns out to be a throw back to the 1980's brick phones, or if it causes your sphincter to leak, those 35% won't buy it.
One key element of communication is shared context. If you chose to ignore that context then that's your problem.
Are you sure it's the consumers that are stupid? Maybe it's the pollsters asking the wrong questions. When I buy a computer, I don't buy it in order to run windows, or run linux, or run mac osx, or run solaris, I buy it to run world of warcraft, or to run ms office. The underlying technology is relevant, but not the point and for the most part I don't need to know the details. Whether my OS uses a unified VM subsystem, COW pages, or ZFOD just isn't that important to me. In the same fashion, what the wireless technologies my phone uses are far from the most important attributes of my phone. I want to know whether it's a smart phone or not, whether it supports the features I desire.
I personally know that my iPhone 4 isn't a 4G device. But I really don't care and I certainly wouldn't expect people to know these sorts of details if they aren't just phone nerds.
The US budget problem won't go away until people stop thinking that the government should be in the business of redistribution. Particularly people expecting to get more out of SS and medicare than they put in by a factor of three or more.
Somehow I don't think you realize that this is about Microsoft's equivalent of the Google StreetView car and nothing at all to do with the phone. You're not intended to run this code, ever. It's for them to run. What they are doing is, is showing that they're doing it "right" as compared to Google's way of doing it "wrong."
And the funny thing is that in the Google threads there are tons of people who do all sorts of speculation in order to absolve Google, and in the summary of this story they go to all sorts of speculation to incriminate microsoft. Way to go people.
Everybody who keeps saying "you'll get picture or you won't" should really be saying "you'll get signal or you won't." As in you'll either get the correct data or you will get very incorrect data. Crap like "better reds, sharper picture, clearer audio" are all bullshit in this area. It's either going to be perfect or very fucked up. And the range of cables (for your normal consumer who installs their gear in close proximity) that will deliver perfect is very large. A cable that would be unacceptable in the analog world could be perfectly fine in the digital world because all you needs is to be able to accurately discern your ones and zeros.
Why would I have to weed out "legit" domains? I'd only be hitting his page once a day. He's going to detect that as a scraper? Twenty or thirty site admins, hitting the mailinator front page at random, but realistic, times once every one to two days, sending proper headers, requesting all the linked material from the page -- that's going to show up as scraping? In a month you could feasibly burn 300 - 450 domains.
Consider it this way... who has more time to dedicate to the game? You, who have a site to run, or that guy, who doesn't have to do much of anything else to do at all - not to mention all the other services that do the *exact same thing*? Remember that these guys can change IP addys and domain names in bulk.
Maintaining this kind of blacklist is part of running the site. And Mr. Tyma lives on sunshine and fresh air? He doesn't have to work? He gets free hosting, bandwidth and domain registration?
And ultimately why do you think people who might find this sort of service objectionable are stupid? You think they don't know about MX records? That they couldn't take each alternate site presented and check the DNS entries and see where it's mail is delivered. And if you want to get really clever, see who owns the IP address space involved. And the obvious thing: send a trial email. It's not that hard, eh?
I'm just ass enough to be patient and just keep eating his random domains. It's free for me to add them to the blacklist. Each on cost him $0.75 or something. And it's not like I can't republish the list. Get together with a handful of other site admins, pool our resources and we all hit the site at random times throughout the day from random locations and what do you know, in not too long it'll he'll get tired of paying for new domains.
How many of them come with high-gain antennas, more than 12db? Because the street-view cars weren't just out there rolling with POTS wifi gear. A normal person could reasonably put their AP in their house and expect that the signal isn't available in the street due to the power levels, distance and obstructions involved. All that changes when some wanker comes along with specialized gear.
I think that's only effective when you are calling the BIOS for disk access (int 19 or int 13, i forget specifically.) If you have your own device driver that accesses the hardware directly that kind of protection doesn't work.
Slashdot Mirror
If you don't want google to know you're downloading porn (and exactly what porn you are downloading) (and any warez, etc.) then you'll need to make very sure that you never use a site that uses recapcha. Fucking google.
Just because you release something under a permissive license doesn't mean you have to host the content forever. If people wanted a copy of the content, it's their own responsibility to mirror it.
While there a circuit split exists on the question of warrantless GPS tracking, it has long been settled that what you do on the public road isn't private and there are no protections against monitoring your whereabouts in public.
I bet it'll happen. What they are doing is tricking people into associating a name with a wifi hotspot. Bastards. Or something.
I think that anyone who thinks there is a single "odds" for people on the earth being hit by this satellite doesn't understand orbital mechanics. Or even sub-orbital ballistics. (E.g. The further you are from the thrower, the lower your odds of being impaled by the lawn dart.)
No, head said his entire cluster has to be booted one at a time. So AMD is better because it uses coreboot rather than UEFI.
If you have an environment that requires that everything goes down together and then comes back up one at a time in order, you've got bigger problems that what code executes at poweron.
The situation described is highly bizarre and would likely benefit from someone with some application architectural expertise.
a) It was called Niagara.
b) It had no delay when switching.
c) It was slow as shit.
No this is more like you installing a camera in your bathroom. Then you go on vacation. While you are away some pecker head breaks in, and throws a party. One of the guests uses the bathroom and you put the pictures on the internet. Even though the guest did not break in and the act of the guest using the bathroom has nothing whatsoever to do with the breaking and entering anyway.
They're not doing it to hide your address, that's just an effect of what they are doing. Google's resolvers are nowhere near the querying client. CDN and GeoIP based services are now unable to determine the nearest server based on the IP address of the resolver. Consider: If I am a customer of Xmission and I use Xmission's name servers then I will get directed to an Akamai host that is physically located in Xmission's datacenter and the content will traverse over their LAN. However if I use Google's resolver then I will get directed to an Akamai host that is near Google's resolver rather than near me. So now the content is pulled from somewhere on the otherside of the universe.
You aren't understanding what is going on here. All Google and OpenDNS are doing is providing the authoritative DNS server with the IP address of the client. Google/OpenDNS know nothing about any possible caching or local servers. They are just making it possible for the final DNS server to possibly, assuming that whoever owns the domain you are resolving supports some kind of CDN, send you to a nearby server.
What likely really happened here is this:
Akami: Hey Google! You're compulsion to violate everyone's privacy is fucking up the Internet by breaking all of the CDN/Geo-based services.
Google: But... but... we must know everything about everyone otherwise we'll not be able to sell them to our customers.
Akami: Whatever dude, you're causing 50% congestion on the backbone links because your shit hides the actual address of the client.
Google: Well, we've got sack-fulls of PhDs. We'll find a solution that allows us to keep spying and selling and still allows the CDNs to work.
Akami: Look you jackasses, the system that exists today works. Your crap is just causing problems and labor for everyone else.
Google: Na-na-na-na-na-na-na-na I can't hear you.
Akami: Seriously. You're being a dick.
Google: No. We've just invented this awesome thing that is going to Speed-Up! The InterNets!
Akami: Jesus Christ! The system that was there before you broke it works. Why the fuck do you have to keep breaking shit?
Google: Because we can and people are stupid. And we are rich. So STFU.
Akami: Fuck. There's no reasoning with these clowns.
Google could just not provide a service that inserts themselves into the DNS path. The problem isn't "the internet" or DNS, it's that Google's DNS servers have no relationship to the client systems. If people were using DNS servers that had some relationship to their network -- such as the one provided by their IPS -- then this wouldn't be an issue.
Plus not using Google's DNS gives you a little more privacy. Privacy of course being defined as not having every activity you do on the internet being logged by one of Google's many methods of invading your space (DNS, analytics, search, advertising, blogger, etc.)
Um... no. All they have is "Will you buy an iPhone 5?" And 35% said yes. They didn't actually take anyone's money. Consider if I were to ask you this question:
"Will you buy <food item of your choice> from <your normal grocery store> next week?"
You're going to answer yes. Now if you show up and the item is spoiled you're not going to buy it. Because with any question about future events, there is built in caveats. If the iPhone 5 turns out to be a throw back to the 1980's brick phones, or if it causes your sphincter to leak, those 35% won't buy it.
One key element of communication is shared context. If you chose to ignore that context then that's your problem.
Are you sure it's the consumers that are stupid? Maybe it's the pollsters asking the wrong questions. When I buy a computer, I don't buy it in order to run windows, or run linux, or run mac osx, or run solaris, I buy it to run world of warcraft, or to run ms office. The underlying technology is relevant, but not the point and for the most part I don't need to know the details. Whether my OS uses a unified VM subsystem, COW pages, or ZFOD just isn't that important to me. In the same fashion, what the wireless technologies my phone uses are far from the most important attributes of my phone. I want to know whether it's a smart phone or not, whether it supports the features I desire.
I personally know that my iPhone 4 isn't a 4G device. But I really don't care and I certainly wouldn't expect people to know these sorts of details if they aren't just phone nerds.
The railroads have right-of-way's along their track. The "SPR" in Sprint stands for Southern Pacific Railroad.
The US budget problem won't go away until people stop thinking that the government should be in the business of redistribution. Particularly people expecting to get more out of SS and medicare than they put in by a factor of three or more.
Um, the PI they hired to do the this work is already in jail because of it.
Somehow I don't think you realize that this is about Microsoft's equivalent of the Google StreetView car and nothing at all to do with the phone. You're not intended to run this code, ever. It's for them to run. What they are doing is, is showing that they're doing it "right" as compared to Google's way of doing it "wrong."
And the funny thing is that in the Google threads there are tons of people who do all sorts of speculation in order to absolve Google, and in the summary of this story they go to all sorts of speculation to incriminate microsoft. Way to go people.
I think the EU would have a hard time cutting any US subsidies. WTF? You can't even get past the first word of the subject line of the article?
Helloooo!!! You're on /.?
Everybody who keeps saying "you'll get picture or you won't" should really be saying "you'll get signal or you won't." As in you'll either get the correct data or you will get very incorrect data. Crap like "better reds, sharper picture, clearer audio" are all bullshit in this area. It's either going to be perfect or very fucked up. And the range of cables (for your normal consumer who installs their gear in close proximity) that will deliver perfect is very large. A cable that would be unacceptable in the analog world could be perfectly fine in the digital world because all you needs is to be able to accurately discern your ones and zeros.
8b/10b isn't used for error correction. It's used for balancing the signal (not too many zeros or ones.)
Why would I have to weed out "legit" domains? I'd only be hitting his page once a day. He's going to detect that as a scraper? Twenty or thirty site admins, hitting the mailinator front page at random, but realistic, times once every one to two days, sending proper headers, requesting all the linked material from the page -- that's going to show up as scraping? In a month you could feasibly burn 300 - 450 domains.
Maintaining this kind of blacklist is part of running the site. And Mr. Tyma lives on sunshine and fresh air? He doesn't have to work? He gets free hosting, bandwidth and domain registration?
And ultimately why do you think people who might find this sort of service objectionable are stupid? You think they don't know about MX records? That they couldn't take each alternate site presented and check the DNS entries and see where it's mail is delivered. And if you want to get really clever, see who owns the IP address space involved. And the obvious thing: send a trial email. It's not that hard, eh?
If I cared this is the scenario I envision:
Seems like he's on the losing side here.
How many of them come with high-gain antennas, more than 12db? Because the street-view cars weren't just out there rolling with POTS wifi gear. A normal person could reasonably put their AP in their house and expect that the signal isn't available in the street due to the power levels, distance and obstructions involved. All that changes when some wanker comes along with specialized gear.
I think that's only effective when you are calling the BIOS for disk access (int 19 or int 13, i forget specifically.) If you have your own device driver that accesses the hardware directly that kind of protection doesn't work.