Photo sharing is hype, we know it. Open source is cool. So a match between both should be fantastic. Open Photo would like to be this great player, able to put together some freedom to what has been so far a proprietary thing.
I like very much the idea to split where you are storing your pictures from the presentation itself, where you publish them, and done through an open source code, that’s just great. But actually many people are already doing it sometimes, not in an open source way. For instance, I am using Google to store my pictures, and I publish them through many channels (FB, Flickr, Tumblr, Google+, …).I don’t publish one picture through many channels because I must, but because I like. Don’t mix up “to store” with “to share”. You don’t do the same things with these different photo sharing websites. There are overlaps, fair enough, but I need all of them. So to make a long story short, you can store images on photo sharing websites, but you are not obliged to and, personally, I don’t recommend doing so!
My first point: the very unique idea of Open Photo seems to make not proprietary all tags & comments of your pictures and to let you store them where you want. If my understanding is correct, I don’t find the story not so much appealing.
Conversely, tools like Pictarine can be much more helpful, acting like a “Pictures hub”, storing nothing but curating your published images.
I think there is a confusion somewhere, and we should get back to the basics of “Digital Asset Management“, something not as hype and recent than photo sharing. You must make a difference between:
- How I am taking digital pictures
- How I am doing the post-processing
- How I am managing the versionning of each picture
- Where and how I am storing them
- Indeed, I will publish them through many channels and with different formats, so publishing channels processes are the next thing to take care of
- Last and not least, how I am managing the social experience with my pictures
I have the feelings that Open Photo is going to be “one more photo sharing experience”. Of course they will pretend the opposite! But frankly with have already rather too many photo sharing options than too few. And I know the Open Photo’s team knows it. On a side note, flaming Smugmug and Flickr, like the are doing, looks weird to me. They have their defaults, limitations and weaknesses but, I mean, they are quite good at doing what they are supposed to do! And they are actually quite unique. Photobucket and the other Instagram are not evil per se, they are proposing a social experience of their own. Yes, photo sharing is broken and must be fixed, but that’s more because of its immaturity, not because of its lack of open-sourceness.
Open source is more for improving interoperability and standards, as every vendor try to lock-in its customers, and open source must act against this evil. But again, open source is for technology, not for end users experience – even if some open source teams will often try to pretend the contrary.
So yes, you should not store your pictures with the same provider than where you are publishing them. And you certainly don’t need Open Photo to do it. But do you really need to own the comments and tags of your pictures? That’s arguable.
Maybe Open photo could be a kind of competitor of Pictarine, they are both dealing with curation limits of photo sharing services, even with a very different philosophy, or maybe even work closer if not together, but so far Open Photo looks more like again reinventing the wheel, like too many open source projects, instead of focusing at real innovation, like some do, with so much success. As far as I know, one should remember open source is mainly if not only attractive for geeks, developpers and techies. End users, the mainstream, don’t care or/and don’t understand what it means to be LGPL / Apache licenced and don’t want to belong to the great Github community! I don’t think Apple can be known as an open source company – no kidding! – but they are very much liked by end-users. So do many Flickr and Smugmug users, even if they can criticize these services.
So, what do we need?
I need one and only one tool which will let me storing my pictures “anywhere” (I could switch from Dropbox to let’s say Google drive! – or the opposite if you think Google is evil), manage the versions of my pictures, and will let me publish them every where, and which will let me enjoying and handling well the social experience I am developping with them. And I need it by picture (the asset is “one picture, several versions, many published items, its comments and tags”).
Simple, but not easy at all.
For the record, Lightroom could make it, but so far does not really. It is indeed the Swiss tool of pictures’ management, not the real “pictures hub” I need. It does not manage at all the social experience, that’s more for Pictarine which, conversely, does not handle the assets themselves. They provide a time-display, but no per asset display like Lightroom, which is still unable to show what-the-hell you are doing with you assets. Something Pictarine is very capable of.
Should this software be open source, that would rock. Should it not be, too bad but I may use it nevertheless. That’s how open source works: it is better with them but it works without.
1 thought on “Open Photo: a good idea but may be just a missed opportunity”
Pingback: Open Source and photo sharing | Qlakk
Comments are closed.