Yeah... I had *numerous friends duped by the various varieties of apps that claim to allow your phone to charge off of solar via the screen... You don't have to grow up without technology to not understand what it is (currently) capable of.
The meat of this answer is good... with more detail that answers some of the rebukes:
The corollary I would make is to my other life in the Sound Engineering business. My golden rule is I never tell an engineer what's wrong with their mix during a show (and only after if they specifically ask for my feedback) and similarly wish others would follow the same rule. This is because: 1) If we can't hear it we're probably not going to do a good job of fixing it. and 2) Chances are we actually already know about it and are either working on fixing it OR it's something fully broken that we're currently incapable of doing anything about.
How this ties: Terminology aside, users *should report issues. Feedback is important and a stream of information (provided you have the processes / resources to get useful information out of it) is a good thing. BUT any "work order" that goes to the devs shouldn't come from that stream of consciousness. Any "bug"/"feature request" should be verified by QA / product management (for features) before change work moves forward. For what are really "Feature Requests" this is fairly straight forward. Whomever is responsible for controlling feature creep and project scope needs to gatekeep those. For what are truly "Bugs" you similarly need to be able to triage what gets fixed and when PLUS if no one in house (QA/etc) can verify or reproduce the bug then just like my above example how are the devs expected to properly fix it. This is essentially TDD: QA creates a reproducible test that confirms the bug and the devs fix the problem until it passes the test.
SO with a proper "intake" process your devs aren't working off of some user bug that the user needs to validate. They are working on a fully qualified bug report that QA has created and verified so that once fixed QA is fully capable of validating the fix is in (and in conjunction with a proper regression suite also that it didn't break anything else along the way).
In a small shop where there aren't separate layers of QA / Prod Mgmt / etc the above functions may be consolidated into what may be a single "dev" BUT the process is the same. You can't fix what you can't see (reproduce) so go through that work first and the rest sorts itself out.
The studios are complaining because they aren't maintaining their DVD revenue in *addition to their streaming / licensing revenue. To be completely blunt I don't fucking care. They will always whine when they don't think they are making the maximum possible money. The truth is we can't tell the real economic impact with the data in the article. The only math that matters is this: If $DVD + $NETFLIX >= $DVD-ONLY then the model is working. If $DVD + $NETFLIX $DVD-ONLY then the studios have an argument for harm. We don't have enough information (right now.. I'm sure it's out there) to fill in those equations at the moment but I have a strong feeling (backed by the opening line "Studios are making millions off of streaming services" that the Studios are doing just fine they are just bitching because their DVD-specific revenue is showing a decline.
Ya.. the "sea of a billion drivers to support" issue is also just as good on a Dell where they work closely enough with MS to have the same universal driver support. There are some aspects of Mac Hardware I would like better (weight and battery life being the biggest) but that is secondary to the flexibility / upgradability / ports / "real" docking station / etc that I get with my Dell hardware.
Not necessarily out of scope but not nearly as friendly... with Tesla's current superchargers (as described in TFS) you would need to do that trip in 3 legs with a half hour stop each to recharge. With a 15% reduction you may need to make that 4 legs.
That vs your average IC care these days that could do that trip easy in one leg.
The features of Samsung's new battery brings EVs WAY closer to practical for a long-distance driver.. not on par with the range of an IC car but back to the old standard of "300 miles / tank of gas" we had before Hybrids and fuel efficiency gains bosted that number much higher. Think of it like SSD vs. Spinning Disc. Early on the price / capacity was unaffordable for most. As manufacturing and tech improved Disk Drives still have significantly more capacity / $ but not quite the gap there used to be. Hybrid cars will have better time-to-fill vs. range for the foreseeable future just because batteries take longer to charge than it takes to shove liquid into a tank but the EV cars are at least approaching "good enough" for most people to be able to make the trade-off.
My only hitch with Samsung is that 5 years off is a long time in the tech world.. I would hope such specs would be available sooner than that (purely in terms of the batter gains we've made in the past 5 years)
Not even "pilot"... look behind the scenes at any given McDonalds and they are automating processes all over the place. There is plenty of human interaction still but they are slowly squeezing the humans into the smallest space in the process they can.
Honestly I see all of this as a "Good Thing". The problem lies in how our society is slowly degrading the safety net that makes this "Good Thing" work for all. If we automate away all of the jobs that machines can do you *should end up with workers heading in 3 directions: 1) The people who make the machines. 2) The people who service / run the machines. 3) People who are not skilled enough to do either. In a society with a proper safety net that third category can survive on their (low but adequate) safety net and don't need to do some menial task to justify their sustenance pay. If they want more out of life they can strive to better themselves but I don't really care if someone instead chooses to sit around and do squat. It's their life to waste.
Their comparison between what Spotify has paid them and what YouTube is paying them is a pretty poor comparison. On Spotify, the vast majority of the music played incurs some for of royalty. On YouTube, although there is a lot of copywritten material out there for sure, the bulk of the content does not necessarily incur royalty costs.
The comparison maybe would have been valid if they had qualified it with "For the same about of copywritten material viewed on YouTube vs played on Spotify, Spotify paid us double the royalties."
It's loosely equivalent to some Minneapolis politician complaining about how much less toll revenue they get compared to Chicago when a large number of Chicago's freeways are tollways and Minneapolis only charges for express lanes (when you're not a carpool).(I know the analogy is a bit of a stretch but it's been a long day.. gimme a break!!;)
You realize that most of the 240Hz TVs that were sold were designed for 3D capability? 120Hz for a mono image is a nice round number because it can support both primary content frame rates evenly. For a stereo image (how most 3D TVs work) you get half of the available frame rate per eye so to get that optimal 120Hz per eye you need a 240Hz TV.
PS. To answer the original question: No. In the sense of how the question was asked, I have never produced any software that I'm ashamed of what it is used *for.
BUT there is plenty of code I wrote when I was younger / less experienced that I'm kinda ashamed I wrote... I could write it SO much better today:)
One of the biggest conspiracy theories around 911 (Please not getting into that argument just an example) is that the building were *designed to withstand an airliner impact and so should not have collapsed. Lawsuits after the fact take such things into consideration: If your building is not designed to such standards and a plane flies into it it is expected to fall and liability fall almost entirely with the terrorist. (I know there are exceptions... just in a "sanish" world.) BUT if your building is designed to withstand an airline impact and the building still falls because of faulty design then chances are more likely you'll win a lawsuit against the design firm and maybe the construction firm, etc.
Here in MN we had another excellent example: The 35W bridge that collapsed. There were *tons of lawsuits after that one and culpability fell on many groups. The bridge was designed to withstand a certain amount of weight but was also many decades old. It was a poor design in-general which is called "fracture critical" where a single failure can lead to total collapse. At the time it fell there were 100s of tons worth of construction trucks all being parked on the bridge along side regular rush hour traffic (think of these trucks much like the terrorist in the first example). You also had state inspectors who had been (or maybe not so much as they should have) regularly checking the bridge to validate its safety. *ALL of these groups were found liable to some extent and had to pay out settlements.
If you sell software or a service that has a contractual promise of a certain level of security or stability and that software doesn't live up to that spec there are all sorts of lawsuits involved. If you are in a software business where lives are on the line (Health Care, Weapons / Aerospace Tech / etc) then you can be damned sure they'll be coming after you if someone's life is lost. There isn't some magical bubble that keeps us developers from liability for the tools that we produce. The IS however a more acceptable level of lack of perfection given the natore of how complex the systems we create are and, frankly, how much did you pay us to build it right.. what promises did you pay me to live up to.
"citing a poll commissioned by London & Partners, the mayor's economic promotional company"
As Slashvertisements go this one is a bit more like news BUT it's still PR. Of course the Mayoral commissioned poll is going to show whatever the Mayor needs it to show. And of course the papers are going to let the Mayor get in all of his sound bites as he scrambles to lessen the impact Brexit will have on his people (bottom line).
So, on topic, it seems to me that the great improvement here isn't necessarily the reheating but the fact they do so on vaporized milk (dispersed/whatever preemptively blocking pedant reason why what they are doing is different from actual "vaporization")
My question: Have they tried doing this during the initial round of pasteurization to see if the resulting once-baked milk is significantly 'cleaner' and possibly closer in taste/nutritional value to unpasteurized milk? The science makes a lot of sense to me as your heating will be more effective with more exposed surface area but I'm not clear on why this needs to be a secondary process instead of a modification of the primary process.. ?
Personally I'm making the assumption that our genetic ancestors survived by eating all of the species who didn't. Even a meat eating dinosaur would need a LOT of meat at its disposal BUT a small mammal can live for a long time on the meat of a single massive dino. The conditions post-impact might even be just about perfect to naturally preserve them.. ?
Get out the smoker, honey! We're making dino-jerky!!!
I'm extremely conflicted on this issue. I strive to not be a hypocrite as much as possible so in this try to constrain my activities to a set of rules that I would be comfortable with everyone else following. SO here's where I'm at:
I go to a LOT of concerts. I believe the vast majority of people don't understand the depth of this statement. 5-7 nights a week. 250-300 days out of the year I'm seeing live music. There are many different kinds of shows and each one has slightly different rules. Clubs are very different from Theaters are very different from Stadiums are very different from Festivals. You really need to respect the environment you're in. I really hate how a lot of people use their phones during a show BUT at the same time my favorite hobby, aside from seeing the music in the first place, is capturing it for the many many people who live vicariously through my concert experiences. This is not vanity. I get thanks on the daily from people who don't have the time or money to go see what I do and truly appreciate the photos and videos I capture and share. SO, I need to find a balance between getting that done and not being "that guy" at a show either. Here are the rules I try to follow:
1) Turn off your flash. *Period. Cell phone flashes suck. You will get better photos with the light that is being provided by the stage light engineer. The *only time you need your phone flash is if you are taking pictures of your friends in the audience and then only if they are in the dark (see #2). Your friends look cooler if you take a photo away from the stage so they are illuminated by the stage lighting anyway. 2) I don't take selfies or group shots during shows: This is not only obnoxious for the flash that is often used (necessary or no) but also for the "sorry we're going to expand and shove you all out of the way so we can get an unobstructed shot". I'm not going to say I've never been in such a shot nor taken one but I avoid it to the max because I hate it when it happens. 3) Keep video to a minimum: I love having videos but hate taking them and it's really hard not to be "that guy" while doing so. Aside from the above *never use flash while recording because goddammit why are you blinding me for that long! but also: a) Video is better horizontal than vertical. b) try to not hold the phone blocking everyone else's view. This is prime if you can be close enough that you can hold your phone over someone's shoulder so only you and maybe the couple people immediately behind you can see it. c) Phone video only looks good when you hold the phone extremely still. If you can't do this then don't record video. d) (Personally) since I want this to be worthwhile to the general public I always record a entire song. I don't want to watch some crappy minute long shaky video of whatever so if I'm going to go through the hassle and aggravation of recording one then its going to be steady, quiet and a complete song. I also shoot for no more than 1 video per show or set if any. 4) Do your work quick and go away. Block people's view for as little time as possible and put your phone away. I've had shows where I took literally hundreds of photos and the people around me were like "dude I rarely saw your phone in the air". Look for a good shot, get your settings configured when the phone is out of view, pop it up and take a few quick shots (this is faster when the flash is off and any HDR is off as well!) and put the phone away. ALSO you're not going to capture the whole show. Don't try. Take a bunch of (near most) songs off and just enjoy them. I've been behind people who were shooting constantly and it's annoying. 5) Don't do a bunch of other stuff with your phone. If it's a really major show I might do a single FB update with a photo but else my phone is in my pocket unless it's being a camera or watch. *exception: for really large shows (festivals / stadiums) people may need to find where I am / vice versa so texting is a necessary evil sometimes BUT I'm not sitting there chatting about other crap. Purely lo
Not surprised at all since I helped build the system.
DoS has been matching Passport and Visa photos for a long long time. The only news here is that the FBI, only somewhat recently, added Face and Iris to their NGIS Fingerprint system. The fact they can search all 3 databases from one source was a fairly easy piece of middleware since all the databases are running the same Biometric software.
The world rotates based on a careful balance of the illusion of security and the illusion of privacy... people still enjoy their delusions tho.
PS. DNS-and-BIND apparently read a completely different post than yours. Reactionary response to something I'm pretty sure you didn't say..
Slashdot Mirror
It's how you use it.
That's (a small) part of why I don't employ them.
Next question?
My estimates are always perfectly accurate!
Yeah... I had *numerous friends duped by the various varieties of apps that claim to allow your phone to charge off of solar via the screen... You don't have to grow up without technology to not understand what it is (currently) capable of.
The meat of this answer is good... with more detail that answers some of the rebukes:
The corollary I would make is to my other life in the Sound Engineering business. My golden rule is I never tell an engineer what's wrong with their mix during a show (and only after if they specifically ask for my feedback) and similarly wish others would follow the same rule. This is because: 1) If we can't hear it we're probably not going to do a good job of fixing it. and 2) Chances are we actually already know about it and are either working on fixing it OR it's something fully broken that we're currently incapable of doing anything about.
How this ties: Terminology aside, users *should report issues. Feedback is important and a stream of information (provided you have the processes / resources to get useful information out of it) is a good thing. BUT any "work order" that goes to the devs shouldn't come from that stream of consciousness. Any "bug"/"feature request" should be verified by QA / product management (for features) before change work moves forward. For what are really "Feature Requests" this is fairly straight forward. Whomever is responsible for controlling feature creep and project scope needs to gatekeep those. For what are truly "Bugs" you similarly need to be able to triage what gets fixed and when PLUS if no one in house (QA/etc) can verify or reproduce the bug then just like my above example how are the devs expected to properly fix it. This is essentially TDD: QA creates a reproducible test that confirms the bug and the devs fix the problem until it passes the test.
SO with a proper "intake" process your devs aren't working off of some user bug that the user needs to validate. They are working on a fully qualified bug report that QA has created and verified so that once fixed QA is fully capable of validating the fix is in (and in conjunction with a proper regression suite also that it didn't break anything else along the way).
In a small shop where there aren't separate layers of QA / Prod Mgmt / etc the above functions may be consolidated into what may be a single "dev" BUT the process is the same. You can't fix what you can't see (reproduce) so go through that work first and the rest sorts itself out.
Wait... you shut down your laptop??
I haven't fully shutdown my laptop in 2.5 years. Problem solved.
The studios are complaining because they aren't maintaining their DVD revenue in *addition to their streaming / licensing revenue. To be completely blunt I don't fucking care. They will always whine when they don't think they are making the maximum possible money. The truth is we can't tell the real economic impact with the data in the article. The only math that matters is this: If $DVD + $NETFLIX >= $DVD-ONLY then the model is working. If $DVD + $NETFLIX $DVD-ONLY then the studios have an argument for harm. We don't have enough information (right now.. I'm sure it's out there) to fill in those equations at the moment but I have a strong feeling (backed by the opening line "Studios are making millions off of streaming services" that the Studios are doing just fine they are just bitching because their DVD-specific revenue is showing a decline.
Ya.. the "sea of a billion drivers to support" issue is also just as good on a Dell where they work closely enough with MS to have the same universal driver support. There are some aspects of Mac Hardware I would like better (weight and battery life being the biggest) but that is secondary to the flexibility / upgradability / ports / "real" docking station / etc that I get with my Dell hardware.
Not necessarily out of scope but not nearly as friendly... with Tesla's current superchargers (as described in TFS) you would need to do that trip in 3 legs with a half hour stop each to recharge. With a 15% reduction you may need to make that 4 legs.
That vs your average IC care these days that could do that trip easy in one leg.
The features of Samsung's new battery brings EVs WAY closer to practical for a long-distance driver.. not on par with the range of an IC car but back to the old standard of "300 miles / tank of gas" we had before Hybrids and fuel efficiency gains bosted that number much higher. Think of it like SSD vs. Spinning Disc. Early on the price / capacity was unaffordable for most. As manufacturing and tech improved Disk Drives still have significantly more capacity / $ but not quite the gap there used to be. Hybrid cars will have better time-to-fill vs. range for the foreseeable future just because batteries take longer to charge than it takes to shove liquid into a tank but the EV cars are at least approaching "good enough" for most people to be able to make the trade-off.
My only hitch with Samsung is that 5 years off is a long time in the tech world.. I would hope such specs would be available sooner than that (purely in terms of the batter gains we've made in the past 5 years)
Not even "pilot" ... look behind the scenes at any given McDonalds and they are automating processes all over the place. There is plenty of human interaction still but they are slowly squeezing the humans into the smallest space in the process they can.
Honestly I see all of this as a "Good Thing". The problem lies in how our society is slowly degrading the safety net that makes this "Good Thing" work for all. If we automate away all of the jobs that machines can do you *should end up with workers heading in 3 directions: 1) The people who make the machines. 2) The people who service / run the machines. 3) People who are not skilled enough to do either. In a society with a proper safety net that third category can survive on their (low but adequate) safety net and don't need to do some menial task to justify their sustenance pay. If they want more out of life they can strive to better themselves but I don't really care if someone instead chooses to sit around and do squat. It's their life to waste.
Their comparison between what Spotify has paid them and what YouTube is paying them is a pretty poor comparison. On Spotify, the vast majority of the music played incurs some for of royalty. On YouTube, although there is a lot of copywritten material out there for sure, the bulk of the content does not necessarily incur royalty costs.
The comparison maybe would have been valid if they had qualified it with "For the same about of copywritten material viewed on YouTube vs played on Spotify, Spotify paid us double the royalties."
It's loosely equivalent to some Minneapolis politician complaining about how much less toll revenue they get compared to Chicago when a large number of Chicago's freeways are tollways and Minneapolis only charges for express lanes (when you're not a carpool).(I know the analogy is a bit of a stretch but it's been a long day.. gimme a break!! ;)
You realize that most of the 240Hz TVs that were sold were designed for 3D capability? 120Hz for a mono image is a nice round number because it can support both primary content frame rates evenly. For a stereo image (how most 3D TVs work) you get half of the available frame rate per eye so to get that optimal 120Hz per eye you need a 240Hz TV.
PS. To answer the original question: No.
In the sense of how the question was asked, I have never produced any software that I'm ashamed of what it is used *for.
BUT there is plenty of code I wrote when I was younger / less experienced that I'm kinda ashamed I wrote... I could write it SO much better today :)
Your example isn't as far off as you think:
One of the biggest conspiracy theories around 911 (Please not getting into that argument just an example) is that the building were *designed to withstand an airliner impact and so should not have collapsed. Lawsuits after the fact take such things into consideration:
If your building is not designed to such standards and a plane flies into it it is expected to fall and liability fall almost entirely with the terrorist. (I know there are exceptions... just in a "sanish" world.) BUT if your building is designed to withstand an airline impact and the building still falls because of faulty design then chances are more likely you'll win a lawsuit against the design firm and maybe the construction firm, etc.
Here in MN we had another excellent example: The 35W bridge that collapsed. There were *tons of lawsuits after that one and culpability fell on many groups. The bridge was designed to withstand a certain amount of weight but was also many decades old. It was a poor design in-general which is called "fracture critical" where a single failure can lead to total collapse. At the time it fell there were 100s of tons worth of construction trucks all being parked on the bridge along side regular rush hour traffic (think of these trucks much like the terrorist in the first example). You also had state inspectors who had been (or maybe not so much as they should have) regularly checking the bridge to validate its safety. *ALL of these groups were found liable to some extent and had to pay out settlements.
If you sell software or a service that has a contractual promise of a certain level of security or stability and that software doesn't live up to that spec there are all sorts of lawsuits involved. If you are in a software business where lives are on the line (Health Care, Weapons / Aerospace Tech / etc) then you can be damned sure they'll be coming after you if someone's life is lost. There isn't some magical bubble that keeps us developers from liability for the tools that we produce. The IS however a more acceptable level of lack of perfection given the natore of how complex the systems we create are and, frankly, how much did you pay us to build it right.. what promises did you pay me to live up to.
Punctuation is overrated...
"citing a poll commissioned by London & Partners, the mayor's economic promotional company"
As Slashvertisements go this one is a bit more like news BUT it's still PR. Of course the Mayoral commissioned poll is going to show whatever the Mayor needs it to show. And of course the papers are going to let the Mayor get in all of his sound bites as he scrambles to lessen the impact Brexit will have on his people (bottom line).
Meh...
Vi. We've managed to take something meant for editing text and figured out how to embed fucking operating systems into it.
What's the problem?? :)
Soylent Green has to come from somewhere...
So, on topic, it seems to me that the great improvement here isn't necessarily the reheating but the fact they do so on vaporized milk (dispersed/whatever preemptively blocking pedant reason why what they are doing is different from actual "vaporization")
My question: Have they tried doing this during the initial round of pasteurization to see if the resulting once-baked milk is significantly 'cleaner' and possibly closer in taste/nutritional value to unpasteurized milk? The science makes a lot of sense to me as your heating will be more effective with more exposed surface area but I'm not clear on why this needs to be a secondary process instead of a modification of the primary process.. ?
Personally I'm making the assumption that our genetic ancestors survived by eating all of the species who didn't. Even a meat eating dinosaur would need a LOT of meat at its disposal BUT a small mammal can live for a long time on the meat of a single massive dino. The conditions post-impact might even be just about perfect to naturally preserve them.. ?
Get out the smoker, honey! We're making dino-jerky!!!
How can /. be expected to have meaningful and even remotely accurate titles and summaries when there are SO many mines to craft!?!
It'll always be good ole Byzantium to me!
I'm extremely conflicted on this issue. I strive to not be a hypocrite as much as possible so in this try to constrain my activities to a set of rules that I would be comfortable with everyone else following. SO here's where I'm at:
I go to a LOT of concerts. I believe the vast majority of people don't understand the depth of this statement. 5-7 nights a week. 250-300 days out of the year I'm seeing live music. There are many different kinds of shows and each one has slightly different rules. Clubs are very different from Theaters are very different from Stadiums are very different from Festivals. You really need to respect the environment you're in. I really hate how a lot of people use their phones during a show BUT at the same time my favorite hobby, aside from seeing the music in the first place, is capturing it for the many many people who live vicariously through my concert experiences. This is not vanity. I get thanks on the daily from people who don't have the time or money to go see what I do and truly appreciate the photos and videos I capture and share. SO, I need to find a balance between getting that done and not being "that guy" at a show either. Here are the rules I try to follow:
1) Turn off your flash. *Period. Cell phone flashes suck. You will get better photos with the light that is being provided by the stage light engineer. The *only time you need your phone flash is if you are taking pictures of your friends in the audience and then only if they are in the dark (see #2). Your friends look cooler if you take a photo away from the stage so they are illuminated by the stage lighting anyway.
2) I don't take selfies or group shots during shows: This is not only obnoxious for the flash that is often used (necessary or no) but also for the "sorry we're going to expand and shove you all out of the way so we can get an unobstructed shot". I'm not going to say I've never been in such a shot nor taken one but I avoid it to the max because I hate it when it happens.
3) Keep video to a minimum: I love having videos but hate taking them and it's really hard not to be "that guy" while doing so. Aside from the above *never use flash while recording because goddammit why are you blinding me for that long! but also: a) Video is better horizontal than vertical. b) try to not hold the phone blocking everyone else's view. This is prime if you can be close enough that you can hold your phone over someone's shoulder so only you and maybe the couple people immediately behind you can see it. c) Phone video only looks good when you hold the phone extremely still. If you can't do this then don't record video. d) (Personally) since I want this to be worthwhile to the general public I always record a entire song. I don't want to watch some crappy minute long shaky video of whatever so if I'm going to go through the hassle and aggravation of recording one then its going to be steady, quiet and a complete song. I also shoot for no more than 1 video per show or set if any.
4) Do your work quick and go away. Block people's view for as little time as possible and put your phone away. I've had shows where I took literally hundreds of photos and the people around me were like "dude I rarely saw your phone in the air". Look for a good shot, get your settings configured when the phone is out of view, pop it up and take a few quick shots (this is faster when the flash is off and any HDR is off as well!) and put the phone away. ALSO you're not going to capture the whole show. Don't try. Take a bunch of (near most) songs off and just enjoy them. I've been behind people who were shooting constantly and it's annoying.
5) Don't do a bunch of other stuff with your phone. If it's a really major show I might do a single FB update with a photo but else my phone is in my pocket unless it's being a camera or watch. *exception: for really large shows (festivals / stadiums) people may need to find where I am / vice versa so texting is a necessary evil sometimes BUT I'm not sitting there chatting about other crap. Purely lo
Here's a fine read... yes there are both and yes sometimes the exhaust side is useful.
Great Vietnam era story on page 2 as well.
http://forums.off-road.com/jee...
Not surprised at all since I helped build the system.
DoS has been matching Passport and Visa photos for a long long time. The only news here is that the FBI, only somewhat recently, added Face and Iris to their NGIS Fingerprint system. The fact they can search all 3 databases from one source was a fairly easy piece of middleware since all the databases are running the same Biometric software.
The world rotates based on a careful balance of the illusion of security and the illusion of privacy... people still enjoy their delusions tho.
PS. DNS-and-BIND apparently read a completely different post than yours. Reactionary response to something I'm pretty sure you didn't say..