5 comments on “Leaving Flickr Behind: Why You Should Host Your Own Photos and Why Linux Makes It so Damn Easy

  1. Thanks for the info! Yes, I had previously been aware of the B3 and it looks like a very nice home server; as for hosting your own web site and sharing it with the rest of the web, I’ve understood the ISVs service contracts generally contain language to prohibit this, so that’s the major reason I’ve not gone this route.

  2. I think this may be more viable in the future. Once ipv6 finally really and truly hits it would be quite profitable for ISPs to allow people to run servers and then just charge them for bandwidth and IP addresses. You could rent a VPS like I do, but that’s WAY more expensive than flickr and I don’t host my photos on there because the bandwidth costs would kill me.

    Another thing this will allow is that when everyone has servers, there will be more federated services. When there’s a status.net-like flickr then you don’t even have to lose the social aspect – which is what I love the most about flickr.

    Finally, there’s the problem of the inundation of content. How do people find your photos, podcasts, etc? By being on flickr you give people a central place to search for and find your photos. On your own server you’ll only get your friends and family looking at them. I enjoy as many people as possible seeing my photos, so that’s not for me.

  3. Thank you Dmitri for this blog post. I’m Piwigo founder and I also think hosting your own photos is a good solution. Hosting them “at home” is still a challenge today but it’s possible.

    Dmitri and Eric Mesa, you have written about something important when leaving Flickr for a “personal hosting” solution: you loose a big part of the social aspect. Of course, this is not a big deal for those who share photos for friends and family but when you want your photos to be seen by “as many people as possible”, then it’s a key feature.

    One of the big project in 2011 related to Piwigo is a “Piwigo Network” or “Social Piwigo”. The idea is to be able to connect several Piwigo to create a network. For example, a “master” Piwigo would be able to display a chosen list of photos from another Piwigo “slaves”. This is just a specification draft for the moment, but Piwigo already has the plugin architecture and the web API (for communication between softwares) which are the required technical features before implementing this kind of high level functionality.

  4. I’ve just started building websites, and have much to learn. Someone just suggested that I use pictures and host them on my own server, so this article was definitely helpful. Right now, my internet connection is too iffy, so this plan will have to wait a while to be implemented!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s