Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
1–10 of 26 posts
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#2I only thought once.
The del.icio.us API would allow them to grab pretty much all of it anyway. I've already migrated mine out to a couchdb-based clone: http://xlson.com/2011/01/13/out-off-delicious-and-into-your-...
This has the nice benefits of always being local and being impossible to take away from me. :)
(well, I did break my couchdb build with an experimental branch on an experimental OS, but I'll sort that out later)
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#3Sounds like fear mongering. There aren't any terms in there that you won't find on other sites that allow users to post content. The company is protecting itself from misuse in a way that might not have been necessary when the Delicious service first launched in the early days of Web 2.0.
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#4[deleted]
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#5[deleted]
Those are the old terms.
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#6Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#7Sounds like fear mongering. There aren't any terms in there that you won't find on other sites that allow users to post content. The company is protecting itself from misuse in a way that might not have been necessary when the Delicious service first launched in the early days of Web 2.0.
I don't think so. I had my flickr account deleted without warning for posting pictures of Abu ghraib abuses, and they weren't the worst pictures either.
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#8Sounds like fear mongering. There aren't any terms in there that you won't find on other sites that allow users to post content. The company is protecting itself from misuse in a way that might not have been necessary when the Delicious service first launched in the early days of Web 2.0.
> The company is protecting itself from misuse
Also, this is the same argument that gets used by large tech companies like Microsoft for building their patent portfolios. It's 'only for defense,' so long as there is no reason to use if offensively.
Would you allow the government to put CCTV cameras inside of your home so long as their promised to only use them in case someone breaks into your home (as evidence in a trial)? Once they were installed, and their 'foot is in the door,' how long do you think it will be before that usage is expanded beyond the original promise through a series a baby steps?
Overly broad legal wording as a 'defensive' move is a cancer on our society.
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#9Sounds like fear mongering. There aren't any terms in there that you won't find on other sites that allow users to post content. The company is protecting itself from misuse in a way that might not have been necessary when the Delicious service first launched in the early days of Web 2.0.
> The company is protecting itself from misuse No. They are re-defining what the term 'misuse' means (from one agreement to the next). If posting 'obscene' links is not forbidden, then how is it a 'misuse' of the system? Also, this is the same argument that gets used by large tech companies like Microsoft for building their patent portfolios. It's 'only for defense,' so long as there is no reason to use if offensivel…
No, I agree with the fear-mongering. I guess the author needed to fill article space, this week.
I'm a privacy-nut type of person and I hate restrictive and absurd licenses. I'm a fan of telling the man to eat it. Note that I'm not justifying restrictive or broad legal agreements, either. I think it's stupid. I just don't think it's any more stupid than similar agreements for similar sites that provide similar services that most of you (including the author of that article) already use every day.
However, I don't see anything in the agreement that you wouldn't normally see on any other social networking site. Unlike some other online bookmarking services, Delicious is a social-networking/bookmarking service, which would explain the concern over content and age and so on. It would perturb me if I was having to agree with something like that for a service which was only me saving bookmarks with comments and tags for my own use that only I would see or access via my own account for myself, but that isn't what Delicious has turned into. Very possibly, they may have even bigger "social networking" ambitions for the service after the purchase, which may further necessitate such stringent clauses.
Besides, if one cared much about that sort of thing, chances are that they wouldn't stop using Delicious now, because they would have already stopped using Delicious when Yahoo! bought them, for similar concerns over privacy and agreements.
Re: Why You Should Think Twice About Opting-In to the Delicious-AVOS Transfer
#10I only thought once. The del.icio.us API would allow them to grab pretty much all of it anyway. I've already migrated mine out to a couchdb-based clone: http://xlson.com/2011/01/13/out-off-delicious-and-into-your-... This has the nice benefits of always being local and being impossible to take away from me. :) (well, I did break my couchdb build with an experimental branch on an experimental OS, but I'll sort that ou…
The API does not give access to other people's accounts.