Could it be that the metal back on the HTC One interfered with the NFC? That would be strange, given that the spec sheet over at gdgt.com says that it does do NFC payments.
Regarding the EWG's suggested Aggregated RDS model, are there additional advantages and disadvantages that should be considered? In such a model, which data repository (ARDS or Registry) should be considered authoritative?
Regarding the EWG's suggested Aggregated RDS model, are there additional advantages and disadvantages that should be considered? In such a model, which data repository (ARDS or Registry) should be considered authoritative?
Could the EWG's recommendations for purpose-driven authenticated Gated Access to validated registration data satisfy identified RDS users and their needs? In such a model, how would requestors be identified, authorized and issued RDS access credentials? In particular, who would accredit law enforcement agents, based on what criteria?
Could the EWG's recommendations for purpose-driven authenticated Gated Access to validated registration data satisfy identified RDS users and their needs? In such a model, how would requestors be identified, authorized and issued RDS access credentials? In particular, who would accredit law enforcement agents, based on what criteria?
Could the EWG's recommendations for addressing maximum protected registration satisfy both accountability needs and the privacy needs of at-risk individuals? How might a suitable solution be identified and funded?
Could the EWG's recommendations for addressing maximum protected registration satisfy both accountability needs and the privacy needs of at-risk individuals? How might a suitable solution be identified and funded?
Are the users and purposes identified by the EWG thus far sufficiently representative? Are there any significant gaps in users and purposes that must be addressed? Are the users and purposes identified by the EWG thus far sufficiently representative? Are there any significant gaps in users and purposes that must be addressed?
Given the desire for an extensible next-generation RDS that might accommodate the needs of a rapidly-evolving global Internet, how could future new users and purposes be accommodated? Who would decide on permitted purposes, using what criteria?
Given the desire for an extensible next-generation RDS that might accommodate the needs of a rapidly-evolving global Internet, how could future new users and purposes be accommodated? Who would decide on permitted purposes, using what criteria?
Are the registration data elements identified by the EWG thus far sufficiently representative of the data required for each identified purpose? Are there any significant gaps in data elements that must be addressed?
Are the registration data elements identified by the EWG thus far sufficiently representative of the data required for each identified purpose? Are there any significant gaps in data elements that must be addressed?
How should public and gated data elements be classified? What criteria should the EWG apply to make initial recommendations in this area?
How should public and gated data elements be classified? What criteria should the EWG apply to make initial recommendations in this area?
What community needs should be considered during the EWG's discussion of registration data storage duration, escrow and access log requirements?
What community needs should be considered during the EWG's discussion of registration data storage duration, escrow and access log requirements?
The EWG acknowledges that deploying and operating the suggested RDS will incur costs. In such a system, how could or should those costs be borne?
The EWG acknowledges that deploying and operating the suggested RDS will incur costs. In such a system, how could or should those costs be borne?
End quote
Tripod, mate, Tripod
And yes, I apologize.
Unreservedly.
But it was a long time ago. And besides, the bitch is dead.
marquee
nested inside
blink
. And I did it because the client's kid thought it was cool. I bet he's sorry to see it go, I know I am.
Reprising the comment I posted over on TFA:
Disclaimer: "This ITWorld page contains at least eighteen trackers, including eight of the top ten listed in the article. Dan's eSarcasm site loads at least 5 trackers including three of the top five."
There, fixed that for you.
--
He had me until he praised the Wall Street Journal series. While the goal of informing non-technical people about tracking on the web is a good one, the series has been full of inaccuracies, omissions and sensationalism. WSJ seems to actively avoid telling people how easy it is to avoid/minimize tracking and AFAIK has never broached the obvious conflict of interest issue raised by their reporting.
Like most Slashdot readers am no fan of tracking and targeted advertising and I run the usual suite of blockers you would expect (Ghostery, AdBlock Plus, NoScript, FlashBlock, Better Privacy, etc etc. But intellectual rigor is even more important to me. It has been missing from the WSJ reporting.
This experience taught me: 1) Cell phone makers simply don't care about software. They have almost zero incentive to put effort into it and often have incentive NOT to invest in software. 2) Never run the stock install from the phone maker. Root it and install a custom mod that is much closer to vanilla Android as possible.
3) Buy a handset with vanilla Android on it to start with.
There, fixed that for ya.
Seconded.
One plain vanilla phone on every carrier with every radio.
For all other phones: On starting the phone for the first time pop a dialog box:
Would you like to use plain vanilla android (with no enhancements for this particular device)?
OR
Would you like to use TouchWizSenseBlur a beautiful-finger-paint-like-buble-gum-super-duper-extras-which-will-love-you-all-night-long-and-cook-you-breakfast-in-the-morning-full-of-win-enhancements-for-your-personal-phone-and-life?
At the start of 2010 it looked like Google was going to try to go down this road with google.com/phone but then Verizon came calling and said "we don;t think so". Google got into bed with VZW on the issue of net neutrality for wireless networks and one of the victims was their project to change the way phones are bought and sold in the US. Perhaps Larry Page will revisit this in the future, but it's difficult to see how it fits into his "focusing" strategy. I'm not holding my breath that all this changes in the US any time soon.
And yes, I vote with my money. I bought an unlocked Nexus One through Google.com/phone on the very first day it went live and replaced it last month with an imported unlocked Galaxy Nexus GSM. And yes, it is a fine phone. When I showed it to the folks at the local Verizon store they were salivating. And then they offered to sell me cases and sleeves for it. They had those in stock, even if they still don't have a release date for the Verizon Galaxy Nexus phone itself.
As an American, I feel sure these speeds must be mis-types by an order of magnitude. Right?
This. Many times over. It's just soooo frustrating sitting here in USA seeing the UK complain about speed and caps and prices. I'd *love* to have that problem. Of course Brits probably look at our US discussions of petrol/gas prices or taxes and have much the same reaction! Swings and roundabouts, I guess.
I would love a MythTV plugin for this... I've been slowly amassing hi-res images to put on our livingroom TV as a slow slideshow for when we have people over... I'd been looking for a trove of good resolution fine 'art'
http://www.haltadefinizione.com/home.jsp?lingua=en from http://tech.slashdot.org/story/10/10/02/1415229/Masterpieces-Online-mdash-High-Culture-At-High-Resolution but I dunno how easily you'll be able to grab the images. Or, indeed, remove the watermarking
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
