well... at least is not as confusing as having the password be "password"

General:: the deactivation password is "password"
Operator: whats the password...
General: "I Said... the deactivation password is PASSWORD"
Operator: ok but whats the password.......
Genaral: The....."; oops too late

The problem is that the internet has a VERY long memory...not just "nudes", but other items as well. Once its out there.... there really is no way to get it back...

Just a one example.... Many people that used to post on USENET in their "younger" days are now finding that items that they had thought were LONG gone off the USENET "spool" are now coming back to haunt them. This is because when google first started its google groups service, one of the items that they had done was to purchase old backup tapes of USENET posts and indexed all of that into their engines. Google bought Deja-News and other usenet providers to gain access to the data. Suddenly stuff that normally would have been gone in 18months is now available to search/find.

The only way to post nowadays to assume that the information will be seen by the ONE person you may not want to see the info in 5-10-20 years.. So be careful what gets out there...Slashdot included.

Old news. This has been an issue for YEARS.

Microsoft used to use and even advocate .local in many of its articles and educational documentation even after it became used by Multicast DNS / mDNS and other systems (http://en.wikipedia.org/wiki/.local)

It was only recently that they stopped when the SSL registrars will no longer accept .local for certificates.

I have also seen several networks using .int for internal domains even though those were used for international organizations for a LONG time. Same as with .local and SSL is when these companies finally understand that the RFCs are there for a reason... .:-)

I wonder who took the lead from whom?

Apple iDevices. anyone?

I guess it really Depends on your definition of "Prompt" either legally or culturally. In some cultures payment of invoices after 30-120 days is considered normal business practice.

I guess she learned the hard way...

Dont talk to cops....

http://www.youtube.com/watch?feature=player_detailpage&v=i8z7NC5sgik

Well... Time to use facebook system against them. They currently have 881 likes. Time for all those people that "liked" their page to unlike it. This would be one easy way to send them and their advertisers a message.....

California actually has laws governing this if personally identifiable information or medical info is breached. Unfortunately many companies do not know about these laws or do not follow them. Also, by the nature of how the law is worded, it may effectivly affect companies all over the US (anyone that does buisness with CA or a CA resident)...

1798.29
http://www.dmv.ca.gov/pubs/vctop/appndxa/civil/civ1798_29.htm

1798.82
http://www.dmv.ca.gov/pubs/vctop/appndxa/civil/civ1798_82.htm

This seems like a reoccuring theme....

Another account of the issues with the Windows Phone app store is also mentioned by a Developer working for Ceton (though the posts are from his personal blog...)

Blog post detailing the problem: http://www.motzwrit.es/post/33309406053/a-broken-process
Initial thread discussing delays in the process: http://www.thegreenbutton.tv/forums/viewtopic.php?f=63&t=3093

This also can be applied to video games. I tend to stay away from "download only" games and get the physical media versions just for that reason. This is why it annoys me that some of the console game publishers are now going to a model where to play online you need an "online pass" or keycode that can only be used once to enable functionality that in the past would have been considered as part of the package.

Unique accounts should be required. But not "real names". The problem is that many HR departments (I know of at least one that does not admit to doing it but I know for a fact does) will as part of their research/vetting of a potential employee actually check for the name/email/phonenumber on resume on MANY online sources (myspace, facebook, google, and USENET) at the very least.

The problem is that once the information is out there, there is no way to control what it is used for. Many poeple that were active on usenet in the 90s would never have thought that their posts would last longer than the longest USENET retention period of the time. Google ended up purchasing dejanews and all their backup spools (http://googlepress.blogspot.com/2001/02/google-acquires-usenet-discussion.html) to be included in googles archives. [BTW; Google also aquired MANY other backups of USENET spools from other sources as well to round out gaps in their archives]

- An innocent comment about "Apple" now for example may cost someone their job in 3-5 years when Apple buys out the company that they work for which is currently competition...

Another problem that I have with Real Name requirement is that it would make it extremely easy for the crooks to impersonate someone and commit identity theft.....