-
Website
http://www.scobleizer.com/ -
Original page
http://scobleizer.com/2007/12/26/google-reader-needs-gpc/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
danja
44 comments · 4 points
-
polizeros
52 comments · 1 points
-
AndyBeard
69 comments · 4 points
-
Zachary Adam Cohen
35 comments · 8 points
-
dbarefoot
40 comments · 3 points
-
-
Popular Threads
-
The best and worst thing Twitter did in 2009: RT
10 hours ago · 19 comments
-
World-brand-building mistakes France’s entrepreneurs make
1 week ago · 181 comments
-
A 2010 real-time app development platform from Kynetx
8 hours ago · 2 comments
-
2010: the year SEO isn’t important anymore
6 days ago · 66 comments
-
iPhone developers abandoning app model for HTML5?
6 days ago · 51 comments
-
The best and worst thing Twitter did in 2009: RT
Thanks for pushing the Google reader team on this granular privacy controls that they need. I hope they do it fast.
Rodney Rumford
The world is becoming more and more transparent, largely due to the Internet. Things marked as highly top-secret are leaked to the mainstream media on a near-daily basis. What exactly would make people think that something marked both "public" and "shared" would be more closely guarded?
Also, what on earth were people sharing in these "top-secret" pubic shared feeds? I subscribe to a little under 750 RSS feeds and I cannot think of a single post I would be ashamed to admit to reading, let alone that I would be ashamed to admit as marking as a Shared Item.
You convinced me on Twitter awhile back to take advantage of the Google Reader Shared Items, and I've since been sharing my feed with my blog readers, on my personal website, and through Facebook. I think it's a great service, and I'm glad you sold me on it. Thanks! (I've been enjoying reading your shared items, too.)
There's no notion of who you're sharing with so long as an RSS feeds exists for those shared items.
Facebook is different because it's a whitelist. These privacy people need to get a life.
Job Title: Chief Complaining Office
;)
I agree, you have to have the choice, if only for the sake of it. But why tweet and have your messages blocked, why "share" and not want it out there? If you want to "keep" things, that's what bookmarking is for. Maybe I could comment here and not have it show up in the thread to protect my privacy? Puh-lease.
And FB's GPC is there because we have our phone numbers and home addresses on there. At least, I have. I understand what "sharing" and "friends" are, on the internet.
Explain, explain, explain! And we bloggers need to do that as well. Want to see something really scary? Go to Google calender. In the search field type username or password. You get results... other peoples results!
If people wanted a private bookmarking service, they should use the Starred items.
The settings do not need to be any more granular.
In the Google Reader case, people with whom you have chatted using Google Talk will "will be automatically subscribed to your shared items when they begin to use Reader", according to the text on the Reader settings page.
The "breach" of privacy, if one occurred, is in Google arbitrarily adding a subscription of your saved item feed to a chat friend's Reader list -- without your permission and without an action by your friend specifically requesting it.
It was this new and unexpected Google Reader "feature" that caused the "How Google Reader Ruined by Christmas" post in the Google Reader forum that started off this controversy.
There is a difference between shared Reader items being "discoverable" and the same items being unexpectedly published to a list of people with whom you are connected through a completely different context.
My enjoyment of Reader has increased since you and I began exchanging shared items. I have discovered blogs I wouldn't have known about otherwise, and on my part, I have started saving things because I think "Scoble should see this".
So the social networking part is fulfilling. It's the arbitrary and involuntary distribution by Google that is unwelcome.
I just shared something yesterday and nowhere did it say this was public. I guess I need to go back and read the fine print on what I was sharing and with whom.
Good or bad, I think the main problem from the complaints I read is many of the unhappy users were coming up with these weird uses for the Shared feed. One guy stated he was "using the shared feed for myself as a way to backup important RSS feeds".
I'm sure the Google Reader team has every intention of making the feature better. I just hope this doesn't end up making it worse or crippling it somehow.
They need to be taken to task just like every other tech company that drops the ball, these companies would be nothing with out the users who make them what they are.
Heck, I've been using both of Google Reader's special feeds for purposes other than perhaps what was originally intended. (For me "starred" items are items I might want to blog about, while "shared" items are just articles that I want to read/review later when I'm not cranking through the few hundred articles waiting for me in GR.)
If Google really wanted to make the article-sharing ability killer, they'd allow folks to have multiple meta-feeds, beyond just "starred" and "shared" (and not counting the ability to do meta-feeds via tagging; I want to be able to share/star/whatever with 2-3 keystrokes), and then granting users the ability to share different feeds with friends.
Also,if your concerned about privacy look back at Internet privacy history - remember the problems DoubleClick ran into back in 2000? Consumers got up in arms but time healed all wounds. If it makes you feel good ask for GPC and Google will comply.
My main concern is that people (in general -- I'm sure no one reading here) suck at ACLs. That's Access Control Lists, and it's the UNIX-y term for granular privacy controls.
If you've ever used UNIX, you've probably heard stories about people who meant to protect files but left them wide open. ACLs solve permissions problem in theory, but UNIX has a very barebones notion of permissions (you, a group, and everyone else). For the most part, manipulating ACLs isn't fun and generally sucks, plus coming up with the right interface/metaphor for access control isn't easy.
Robert, it looks like you can choose people to receive a limited profile on Facebook. Can you configure more than one limited profile or groups (e.g. family sees one view of my profile, friends see another, and work sees a third view)?
you already can create ad hoc feeds. Click Settings > Tags. Every tag you create can be made public or kept private.
When reading a feed you want to tag say "close friends", type gt, and then choose the tag you want. Very quick. Very simple. Very flexible.
One thing that should be mentioned is that we can copy our Reader shared items to a different, obscure tag that behaves the old way. Go to "Manage friends" and click "move or clear your share items" to move them.
I'm also told you can move them right when you see the announcement. Anyone else confirm this?
I like this feature, but I'd like it a lot better if I could choose subsets of friends to share with. Or at least one subset that differs from my Talk contacts.
http://www.spymac.com/details/?2317880
Otherwise we're asking Google to find the lowest common denominator of its user base and go at that speed only.
the "shared" items, which you choose to share is only shared with people on you google TALK and not necessarily with everyone you have in your email contacts correct?
so if you have a problem sharing things with a certain individual why not, uhhhh, remove them from your google TALK contacts (not block, but just remove them).
If you care about your privacy that much in respect to a particular individual or a group of people not finding out the articles in which you are SHARING, you probably don't want them chatting with you anyway, so just remove them.
uhhhh I believe that is their GPC, you just remove them from you chat list. you can still have them in your email list....
I think people, just like to have drama in their lives, this is a non issue, and definitely not a issue to ruin anyones Christmas, thats just childish people.
Kudos for google not giving in... there is always bloglines for the people who are whining.
Another option people can do is to create a new label and set that up as being a shared feed then all they need to do is to add that label to the items that they want to share to be included in that shared label feed.
I'm pretty sure that these items won't show up in the shared friend feeds as google would only be sharing the actually "Shared Feed Items" and not any others.
I did a blog post back in June on how to set this up you can check it out here http://blog.maniacd.net/2007/06/17/using-google...
"This page is accessible to anyone who knows its address, so all that's left to do is to let your friends know about it."
Then there is a URL that the person can share with their friends. There is a "find out more about sharing" link, I clicked on it, and it describes the public PAGE.
I don't see anything about my friends on GTalk getting those feeds automatically. I don't see anything about my friends using Reader automatically getting the updates. It specifically states it will go on a PAGE.
Robert, I'm confused on how users "assumed" something wrong. Google did not do their job by stating specifically on Reader what Shared items would do/does. The user shouldn't have to hunt around for it and if they implemented a new feature the user should have been notified of it when they logged in. Instead of giving me a Tips/Tricks on the Home page give me "We made a major change, this is what this change means to you...".
The interweb is the epitome of transparency and if you don't want it for all to see then don't post it!
Quite simple when you break it down!
In my case I used this feature to share with a handful of trusted colleagues market research and information that was directly relevant to current projects. To suddenly discover months of market research and revealing info about our future initiatives broadcast to competitors in my address book was a shock. Initially the only options were to delete all shares (effectively erasing 700+ items of research) or delete people from gmail's contacts. They've since wisely implemented a feature to allow us to migrate our existing shares to new tags. Admittedly an edge case situation, but judging by the thread on googles help page there are many of those.
This new feature and its clumsy notion of my social graph wouldn't have been such a nuisance if it had been rolled out with some regard for legacy users.
What seems to be lost in all the noise, hyperbole and half-informed opinion on this "controversy" is the more interesting revelation: the gmail address book and users email behaviors seem to be being mined to bootstrap a new social network platform that has no opt-out. The "open-social" future is becoming a ride we're all being herded in line for, like it or not.
http://www.google.com/help/reader/sharing.html
Why are so many people are making up stuff that doesn't exist with regards to Google's sharing feature. To believe that "publicness" means "private enough" takes a leap of logic that seems pretty bizarre.
I kind of like this controversy however, since I think it's past time we had a community involvement in what these terms mean with regards to the biggest services that will be using and interpreting them.
What does "share" or "public" mean? It's clear that it's far from unanimously decided.
My issue was that several people got my shared items feed added to their daily list without any warning. Suddenly a new feed appears that they never subscribed to. When they figured out it was from me, they blamed ME for junking up their feed lists.
My friends tend to be light feed readers. Having a bunch of feeds added without any warning and without subscribing annoyed them. It annoyed me, too. Especially since most of the folks that got my feeds were people I'd never chatted with, contrary to what Google later told us.
I deleted all my contacts then deleted all the feeds in my shared items just for good measure.
I don't mind the "feature". What I mind is the bone-headed way in which it was forced on every user of the Reader. If it had been opt-in, no problem. But not only was it not opt-in, there was no real way to turn it off without disrupting possibly useful OTHER functions. That's bone-headed.
And worse, Google still hasn't fixed it. Utterly bone-headed.
As for the shared tags being an adequate replacement, I think that that is a perfect workaround, for someone that uses Google Reader on a regular basis, or who has an average to more than average amount of experience with computers. I'm not concerned about this for myself, I'm concerned about this for people like my grandmother or my sister or my mother, who while able to use the computer, oddly enough, even after fully reading Google's explanation of the change, might somehow not fully understand the implications thereof. But I guess, what, those n00bs deserve what they get? Right, nerds? Right?! It's THEIR fault for having social lives and other interests that prevented them from chewing themselves into the technoflesh of the internet like a maggot with Asperger's. Right?
"This page is accessible to anyone who knows its address, so all that's left to do is to let your friends know about it."
I can see where the confusion is. They specifically say in this statement, that it is up to you to let your friends know what your feed URL is. They say absolutely nothing about Google intentionally sharing your feed link with everyone in your contacts. I don't know about you all, but some people in my contacts are closer than others. Some are friends, some are business relationships. Some contacts I just emailed once and don't really know. I can definitley picture situations where this could upset people, especially in an election year.
Obviously not. :) It's pretty clear that quite a lot of people did NOT expect privacy from a feature that declared itself "publicly accessible" (see the ZDNet poll or the Mashable poll) and your attempting to dismiss the many, many people who have made the reasonable assumption that public/obscure-equals-public is as incorrect as Google's apparent dismissal of the people who made the leap from "publicly accessible" but obscure to mean "private".
@Modulo Noh - Why won't you acknowledge this? It seems pretty obvious that the issue is divided.
I like this conversation, it seems good to let people better realize the trade-offs when accepting obscurity as security rather than get surprised by it later.
1. Email - click email and type in a name and press send. Best for users you know don't use RSS.
3. "Share" button. Easy. Press share and everyone you gave your private URL to can see.
2. Tag - press tag then type in a name or previously thought of "grouping". Share that out the same way you would have sent a link to the "shared" items.
Clearly #2 is the easiest. Apparently the reader team really meant for use to accomplish granular sharing by #3.
Google. The solution is EASY. People want to share "shared" items by clicking the shared button - and remain private. Here's how you do it. Make the Share button pop open and give a taglike choice: All, group of people, maybe contacts, etc. No one understands what you mean by tags or bother learning what you mean by them in this context. Its hard enough explaining del.icio.us to people. There's your GPC.
We do not have a privacy anymore.