Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I suppose 'lock in' was the wrong choice of words to use. I understand that the data is only there because I chose to auto-upload it, and I also understand that I can easily re-upload the photo to facebook, but my point was that Google themselves are actively preventing me from doing something like that through the Picasa interface.

I think you understood the meaning behind my point, but I'd argue that they shouldn't even be in that space in the first place. The very first thing that any photo-storage/sharing site should be looking at, after the service itself is working, is social sharing and interaction. Google are restricting the interaction on their platform (understandably, I might add) because they have built a competitor to Facebook.

that is what I have a problem with.



"Actively preventing"? How?


By not allowing users to share directly from their plus.google.com interface, to twitter/facebook.


That's passively preventing. (YouTube lets you share to Facebook and Twitter, so the lack of this ability from G+ is a lack of a feature, not one of Google's design goals. Code takes a long time to write and everyone wants a different feature. Eventually we will have them all, but right now, not enough code has been written :)


Prioritizing G+ over an open API (and a "Chinese wall" between the apps and the platform) is still preferential treatment, and is the sort of thing that got Microsoft consent-decreed.

I am not saying Facebook is better, but you can't say Google is better, either.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: