304 karma · joined February 17, 2008
So it's hard to judge how big or meaningful this story is. But anecdotally, I too am in Canada and I have definitely been hearing a lot recently from American friends who are finding US citizenship to be a PITA because of taxes.
Found this blog post with court documents and background: http://www.skepticalabyss.com/?p=291
EDIT: Found this old blog post by Brian Dunning: http://skeptoid.com/blog/2011/10/05/a-partial-explanation/
"Cookie stuffing refers to a web site writing a cookie to your browser without your knowledge or permission. ... It’s a scary-sounding term, but it’s fundamental to the way Internet advertising works. ... Cookie stuffing is more than just a standard practice; it’s an essential component of the mechanics of serving ads effectively."
The way a lot of bugs are eventually solved is not by asking what caused them, but when they started. It's often the regression testers who find the source. You keep going back through the nightly releases until you find one that doesn't exhibit the bug. At that point you go to the commit logs and there is your problem.
But in something like wordpress, a lot of what gets displayed to the end user is in a database. Aside from page content, widgets and other configuration often ends up in a database. It's not unusual for themes to keep css, javascript or php in the database. (Every time I use a theme that allows me to put PHP into a database I feel like I've failed as a programmer and the gods of MVC will smite me.)
So developer X adds content to his dev copy. Developer Y adds content to his copy. Meanwhile, the client or end users are adding content to the production copy. Using a shared development/staging server somewhat mitigates this, but not totally. You can't just git merge the sql together. (Can you? I mean, sure you can merge two sql files. But is the end product actually usable?) Is this a solved problem?
Anyone know anything about this side of Microsoft? I assume the actual fab is done by anonymous Asian companies. How much of the design (nuts and bolts engineering, I mean) is done in-house and how much is contracted to established hardware manufacturers. (i.e. Does Samsung or the like have a piece of this pie?)
Maybe people just don't like Gnome. (viz. http://tinyurl.com/834bn2j)
For those looking for a distraction while email is temporarily gone, why not contemplate the lighter side of the singularity: http://www.cracked.com/video_18400_why-scariest-sci-fi-robot...
The bootstrap code makes assumptions about the future of the js spec and browser implementations that aren't safe. Young people don't remember the dark days of people writing js to leverage IE/Netscape specific bugs which then had to be turned into features because so much code existed in the wild that could be broken.
Crockford is a scarred veteran of the spec wars. I'm sure that when he sees young people trying to game spec/implementation ambiguities, he thinks, "Never again! Not on my watch!"
I think best practice is explicit, future-proofed code that doesn't tie the hands of spec authors or browser vendors. I know that Crockford's tool doesn't accept the current spec or browser behaviour, but his choice is informed by past experience and concern for the future. It's not just some random bug that he's too stupid or stubborn to fix.
Wire article on haptic compasses: http://www.wired.com/wired/archive/15.04/esp.html
"The U.S.-South Korea status of forces agreement allows servicemembers to be turned over to South Korean custody if servicemembers are suspected of heinous crimes and law enforcement officials request it" (http://1.usa.gov/yrzicW)
I don't know what status of forces agreement exists in Afghanistan.
Is that even true? The advantage of Oauth over the "password anti-pattern" is that you can grant limited rights. i.e. sharing my address book with Facebook. That's personal information, but it's not my entire email archive.
I believe this list is the scope of possible Oauth permissions: http://code.google.com/apis/gdata/faq.html#AuthScopes
It looks like granting access the Gmail Atom feed allows access to new Inbox emails (but not the entire email body, I think.) But if you haven't granted that permission, your emails should be safe. (I think. Any expert opinions?)
Not all animals are pre-programmed for an early death. I wonder if curve for these animals looks like the lightening bolt curve?