Back to work

Summer is gone. No more pictures or travelling, lack of time for much opensource... that's life.

I will also be moving soon, and that will make my spare time even shorter. Lets hope there will still be some spare time during the weekends!

In the mean time, I'm seeing that many photographer applications and code are being added hideously to svn. I really wish those projects got more attention and advertising (and thus help), since, given the skills required for coding them, they require quite a few resources. I hope to be able to help those myself with some code, now and then.

That said, I'm pondering what to do with the photo tutorial series. planetkde is eating too much bandwidth off my server, by showing the whole blog body on each hit. That makes for 12GiB transfer per day (around 6-7k hits, I think) and it's unnacceptable for me, so I will have to stop them for some (short) time and try finding a proper workaround.

[o ] click!


I assume you mean the pictures are causing the bandwidth problems? I use flickr when I want to add heavy images to my Planet KDE posts.

By Mike Arthur at Mon, 09/01/2008 - 19:18

Yes, it's the pictures that eat the bandwidth. The pictures shouldn't have been posted to the RSS feed, since I had split a summary. But kdedevelopers pastes the full body in it.

I'm now setting up my own blog posts here: , which seems like it will be the solution to avoid that much bandwidth waste. I did consider posting to flickr, although they have a bandwidth limitation too, which I don't know how much it is.

About flickr, I'm reluctant to use it and accept their end user license myself, for certain lines in it that claim they can change the license whenever they please, in any manner, and not let you know (you are responsible to check for license updates yourself they say. Why don't they have a stupid e-mail service for warning their users?).

In theory they could just change the license in any moment to copyright all the pictures to them, and not even warn you, while you keep uploading new pics (and thus accept the new license). Not funny.

By uga at Thu, 09/04/2008 - 23:54

I justed wanted to say that I've been enjoying the tutorials, and really hope that you figure out a way to keep them coming. Starting out with a less than ideal picture, and demonstrating different tools by improving it is a great way to keep the readers' attention.

Also, could you tell me the names/webpages of the photo apps you mentioned? I would love to contribute towards making open source photography tools better. Maybe making a blog post where you give a brief summary of each app is a good idea to get people to notice them.

By knutert at Tue, 09/02/2008 - 22:22

"Also, could you tell me the names/webpages of the photo apps you mentioned?"
I wasn't referring to any in particular, but rather all of the many efforts. Other than the known (very public and visible) efforts that happen in digikam, there's for example works on improving dcraw for multithreading and multiprocessing, there's also new apps like Cyrill Berger's darkroom, also his OpenGTL libs...

Those apps, rather than being targetted at the average point and shooter, they target more advanced camera users. And the problem is they get less testing for that same reason. They support multiple proprietary file formats, complex demosaicing algorithms, color management, high cpu consuming processes that can benefit from threading, image processing that heavily depends on the camera model (and thus requires updating each time a new camera is on the market)...

All that work and many others seem so hard to me that I can't do other than praise them.

Btw, one thing I find missing is proper software for color calibration. Lets hope for something soon ;)

By uga at Thu, 09/04/2008 - 23:46