3 ms·

The default privacy permissions are a bit loose for my taste, but I'm not big into sharing photos except with my direct family. Can anybody compare them with f

The default privacy permissions are a bit loose for my taste, but I'm not big into sharing photos except with my direct family. Can anybody compare them with facebook's or picasa / google+'s default privacy settings ? Edit: I've made a bunch of comments as replies to this one. My conclusion is that New Flickr's privacy-friendliness is just barely above Facebook's. However, they haven't yet demonstrated _continuing_ willingness (as Facebook has) to default to lower-privacy options as they iterate. If they notice that I've locked down most of my privacy / sharing settings and then take an educated guess at what I want the default to be when they launch a new feature with a privacy slider ("we've set this to 'only family' for you based off your choices for settings X, Y, and Z."), that would be sweet.

philsnow 13y ago
I was concerned for a moment just now because it looked like one particular setting wasn't sticking: "Hide me from site-wide searches on flickr.com and on 3rd party sites that use the API?" I checked the box and hit "save", but when I went back and looked, it wasn't checked. I tried again and it worked. I wonder if they're using one or more caching layers and not being careful about fetching important bits from the authoritative layer.
philsnow 13y ago
Also, lots of the settings are inconsistent: the more-conservative setting is variously "yes" or "no". I think it's widely-known that structuring your questionnaire this way leads to confusion. One of the settings (geo preferences / "who can see where your photos were taken?") had a weird state to begin with, "no preference set". This is the only one that I saw that had no default. What would have the geo privacy been for photos that I uploaded without setting this?
philsnow 13y ago
It looks like the android app uses a custom browser to render the third-party login pages, putting them in a position to trivially grab your password. I can't think of a reason to have done this. Sure, I would have liked for the "log in with Google" button to pop up the system account chooser, but at the very least, just fire off an intent and let the user's browser of choice take care of it.
- randallu 13y ago
  That's a rough flow though. Assuming the external browser finishes itself when the auth page calls window.close you still have a bunch of ugly activity launches in between; you probably see the last thing you were browsing for a few hundred milliseconds, etc. Not very polished.

philsnow 13y ago

I was concerned for a moment just now because it looked like one particular setting wasn't sticking: "Hide me from site-wide searches on flickr.com and on 3rd party sites that use the API?" I checked the box and hit "save", but when I went back and looked, it wasn't checked. I tried again and it worked. I wonder if they're using one or more caching layers and not being careful about fetching important bits from the authoritative layer.

philsnow 13y ago

Also, lots of the settings are inconsistent: the more-conservative setting is variously "yes" or "no". I think it's widely-known that structuring your questionnaire this way leads to confusion. One of the settings (geo preferences / "who can see where your photos were taken?") had a weird state to begin with, "no preference set". This is the only one that I saw that had no default. What would have the geo privacy been for photos that I uploaded without setting this?

philsnow 13y ago

It looks like the android app uses a custom browser to render the third-party login pages, putting them in a position to trivially grab your password. I can't think of a reason to have done this. Sure, I would have liked for the "log in with Google" button to pop up the system account chooser, but at the very least, just fire off an intent and let the user's browser of choice take care of it.

randallu 13y ago
That's a rough flow though. Assuming the external browser finishes itself when the auth page calls window.close you still have a bunch of ugly activity launches in between; you probably see the last thing you were browsing for a few hundred milliseconds, etc. Not very polished.