Deprecated: Assigning the return value of new by reference is deprecated in /usr/serv/www/blogs/wp-settings.php on line 204

Deprecated: Assigning the return value of new by reference is deprecated in /usr/serv/www/blogs/wp-settings.php on line 206

Deprecated: Assigning the return value of new by reference is deprecated in /usr/serv/www/blogs/wp-settings.php on line 207

Deprecated: Assigning the return value of new by reference is deprecated in /usr/serv/www/blogs/wp-includes/cache.php on line 33
Kirill Ponomarew (krion) blog mess » 2006 » July
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-content/plugins/secureimage.php on line 224

Archive for
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32
July, 2006


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32

Using Firefox 2.0 Beta 1

I’m very curious person, so after FF 2.0 beta1 was released, I’ve downloaded it and tried to compare it to Firefox 1.5

And frankly speaking I’m disappointed. It seems absolutely nothing was done
for memory management, it still requires much memory while having more than 10
tabs opened, and it still runs slowly comparing to Opera.

Only two extensions worked after update: Google Notebook and Lingvo, perhaps developers run out of time to make their old extensions versions compatible with 2.0, dunno.

At last the “X” button was added to every tab, to close it. Extensions and themes are located together in “Tools” -> “Add-ons”. The most sweetest feature I liked is the ability to use Bloglines or Google Reader to subscribe to RSS feeds. I didn’t test any new bookmarks features like “bookmark microsummaries”, since I’ve been using del.icio.us for ages.

FF 2.0 Beta 1 has now “Restore Session” feature (Opera guys would lough), that automatically offers to reopen all tabs if e.g. Firefox crashed.

That’s it, is it worth to release the version with a major number because of all these new features ?  I doubt.


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32

One reason I don’t like flickr.com

flickr.com is great for sharing photos, it’s great to organize the pics, adding tags and run the blogs and slideshows. One feature I’d like to have there, is to secure some picture sets/albums with password. Right now you can protect your photos by pushing your friends and family to create Yahoo account, add them to your friends or family members, so they can browse all your pics.

But is it what people would like ? I can hardly imagine my parents would register at Yahoo to see my new pics. Giving them username and password for some private pics would make life easier.


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 30

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /usr/serv/www/blogs/wp-includes/functions.php on line 32

Gimp scripts

While shooting many pics with new brand IXUS60 and scaling down the pics size afterwards, I had the idea to write the Gimp script which is able to take a bunch of pics, save them with the same filename and reduce the pic quality, eg. to 30 or 50.

To not reinvent the wheel, and spend the hours to learn Gimp scripting, if some of you have that script, it would be good to share it with me :-) Your other ideas about how to optimize such kind of process, are always welcome.

FireStats icon Powered by FireStats