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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
verizon iphone
2010/06/22 11:23
| computing
Please, just stop with this. It isn't going to happen as long as Verizon is a CDMA carrier and the iPhone uses SIM cards (GSM).
When Verizon starts using SIMs (likely in 2012 or afterward) as they transition to 4G / LTE, then it's possibility.
Until then, let's just give it a rest.
When Verizon starts using SIMs (likely in 2012 or afterward) as they transition to 4G / LTE, then it's possibility.
Until then, let's just give it a rest.
comments
screen
2010/06/18 12:16
| computing
If you haven't checked out the man page for the Unix utility screen lately, you may want to refresh your brain on just how many amazing things it's capable of.
culling the herd
2010/03/20 21:11
| computing
The field of email clients I'm going to evaluate got a lot thinner over the last couple days, due to my decision to set them all up so I could move easily from one to another. Since I use IMAP on my mail server, I can read and send mail from any IMAP client and the view of my mail should be consistent from any other client I choose to use.
I ran into a couple snags immediately, though, with PowerMail, GNUMail, and Zimbra Desktop - all of them failed to authenticate against the server. I don't use terribly complex settings at mail.grapefish.org; the IMAP port is secured with TLS/SSL and runs on the standard encrypted port 993, and the SMTP server for authenticated submission runs on port 587, and requires TLS and user login.
GNUMail was able to read mail from the IMAP port, but couldn't send ("SMTP authentication failed" was the message). Neither PowerMail nor Zimbra Desktop could even manage to get that far; they both failed to even log in to the IMAP server. This is basic stuff. The bare minimum an email client should be able to do is log in and retrieve mail, and log in to send it. Having gone through setting up 10 email clients to do just that in the space of 2 days, I was struck by the bewildering array of options, choices, and errata one is faced with to get mail flowing.
There are, in general, two ways to get email from a server, either via the Post Office Protocol (POP) mechanism, or the mentioned remote mailbox Internet Mail Access Protocol (IMAP). Both have both unencrypted and encrypted methods that typically run on standard, widely recognized ports. There is essentially only one way to send mail, through the Simple Mail Transfer Protocol, or SMTP. It can also be either encrypted or not, and uses one of three ports depending on the server configuration. The server at mail.grapefish.org doesn't deviate from these standards, and a number of mail clients work without issue using it.
So why all the trouble? I was, as I mentioned, struck with just how many ways software managed to present the configuration options necessary to get email working correctly, depending on which type of server you use. IMAP or POP, with SSL, TLS, TLS if available (whatever that means), or No encryption. This was sometimes described as "connect securely", sometimes just with a bunch of checkboxes or radio buttons and a method to customize the port, if necessary. You could provide a username in most cases, a password in some, with the option to save it or not. SMTP setup was similar, but added the wrinkle of having to know what type of user authentication was required, PLAIN, LOGIN, GSSAPI, etc. etc.
I haven't thought much about this in the past, knowing exactly what to set for my server (having set it up) and moving on with my day. Setting up options for this in your mail client is something you do once, and usually never again. But I couldn't get any of these three software packages to work. I didn't spend much time trying, though, because (and here's where we get to the point of this post) I couldn't fathom why I should have to.
The experience brought to mind a recent article from Matt Legend Gemmel entitled Engineer Thinking:
Why didn't those programs just set themselves up? It's programmatically trivial to detect on which ports a mail server is listening, and whether or not encryption is supported. Once you have the user's credentials, it's further trivial to verify that they're working correctly. If they aren't, detecting which of a couple different reasons are most likely the issue. The only information a mail client should require to set up server access are the user's email address, the login name (if different), and the password.
Postbox, a commercial version of Mozilla Thunderbird, once told the user's email address, will attempt to discover the name of the mail server by trying common URLs. When I provided my email address, it tried "smtp.grapefish.org", "imap.grapefish.org", "grapefish.org", and so on. Where it tripped up, though, was that the email server for grapefish.org is mail.grapefish.net, which is in a different domain. This is a little uncommon, I suppose, but it's getting more prevalent as people move personal domains to services like grapefish and Google Apps. What I found interesting about that is, again, it's trivial to discover what the mail server is for any given domain with a simple DNS query. Why didn't Postbox try? You wouldn't have to attempt connections to many different likely URLs, none of which, in this case, existed.
Matt Legend Gemmel:
Updated: Postbox was the mail client that attempted to discover the mail server URL, not Seamonkey/Thunderbird.
I ran into a couple snags immediately, though, with PowerMail, GNUMail, and Zimbra Desktop - all of them failed to authenticate against the server. I don't use terribly complex settings at mail.grapefish.org; the IMAP port is secured with TLS/SSL and runs on the standard encrypted port 993, and the SMTP server for authenticated submission runs on port 587, and requires TLS and user login.
GNUMail was able to read mail from the IMAP port, but couldn't send ("SMTP authentication failed" was the message). Neither PowerMail nor Zimbra Desktop could even manage to get that far; they both failed to even log in to the IMAP server. This is basic stuff. The bare minimum an email client should be able to do is log in and retrieve mail, and log in to send it. Having gone through setting up 10 email clients to do just that in the space of 2 days, I was struck by the bewildering array of options, choices, and errata one is faced with to get mail flowing.
There are, in general, two ways to get email from a server, either via the Post Office Protocol (POP) mechanism, or the mentioned remote mailbox Internet Mail Access Protocol (IMAP). Both have both unencrypted and encrypted methods that typically run on standard, widely recognized ports. There is essentially only one way to send mail, through the Simple Mail Transfer Protocol, or SMTP. It can also be either encrypted or not, and uses one of three ports depending on the server configuration. The server at mail.grapefish.org doesn't deviate from these standards, and a number of mail clients work without issue using it.
So why all the trouble? I was, as I mentioned, struck with just how many ways software managed to present the configuration options necessary to get email working correctly, depending on which type of server you use. IMAP or POP, with SSL, TLS, TLS if available (whatever that means), or No encryption. This was sometimes described as "connect securely", sometimes just with a bunch of checkboxes or radio buttons and a method to customize the port, if necessary. You could provide a username in most cases, a password in some, with the option to save it or not. SMTP setup was similar, but added the wrinkle of having to know what type of user authentication was required, PLAIN, LOGIN, GSSAPI, etc. etc.
I haven't thought much about this in the past, knowing exactly what to set for my server (having set it up) and moving on with my day. Setting up options for this in your mail client is something you do once, and usually never again. But I couldn't get any of these three software packages to work. I didn't spend much time trying, though, because (and here's where we get to the point of this post) I couldn't fathom why I should have to.
The experience brought to mind a recent article from Matt Legend Gemmel entitled Engineer Thinking:
Software cannot just wash its hands of issues of technical complexity or uncertainty; it’s not remotely OK to simply offload that work to the user. Software intended to help with a given task has an implicit expertise; we assume that our photo-editing software knows more about photo-editing than we do. Expertise carries a duty of care whereby the expert is expected to provide the benefits of expertise without the full cost of knowledge. That’s why experts are useful! The same holds for software.
Why didn't those programs just set themselves up? It's programmatically trivial to detect on which ports a mail server is listening, and whether or not encryption is supported. Once you have the user's credentials, it's further trivial to verify that they're working correctly. If they aren't, detecting which of a couple different reasons are most likely the issue. The only information a mail client should require to set up server access are the user's email address, the login name (if different), and the password.
Postbox, a commercial version of Mozilla Thunderbird, once told the user's email address, will attempt to discover the name of the mail server by trying common URLs. When I provided my email address, it tried "smtp.grapefish.org", "imap.grapefish.org", "grapefish.org", and so on. Where it tripped up, though, was that the email server for grapefish.org is mail.grapefish.net, which is in a different domain. This is a little uncommon, I suppose, but it's getting more prevalent as people move personal domains to services like grapefish and Google Apps. What I found interesting about that is, again, it's trivial to discover what the mail server is for any given domain with a simple DNS query. Why didn't Postbox try? You wouldn't have to attempt connections to many different likely URLs, none of which, in this case, existed.
Matt Legend Gemmel:
The primary expression of expertise is in knowing effortlessly what the right course of action is in a given situation, and carrying it out without micro-management or endless justification. Make your software such an expert, and a guide and assistant to the user. Don’t force the user to make your software’s decisions for it, or to repeatedly bow down before its keen grasp of the vagaries of choice and uncertainty.
Updated: Postbox was the mail client that attempted to discover the mail server URL, not Seamonkey/Thunderbird.
windows 7 rc
2009/07/19 23:25
| computing
The Release Candidate for Microsoft's upcoming version of Windows has been available for a while now, and I have been installing the betas in virtual machines to have a look at what they've come up with.
I fired up the installation of the RC, and was presented with the following choices:
What's interesting is that a choice is given; I suspect this is only true of the RC installer. Since I would plan to use Professional, that's what I selected to install.
The problem is, though, that the product keys that Microsoft delivers to the testers along with these install images is only valid for the Ultimate version. If you select another version at this screen, the install will fail at the product key entry dialog with the vague error "The product key is not valid for the current Windows SKU."
I fired up the installation of the RC, and was presented with the following choices:
What's interesting is that a choice is given; I suspect this is only true of the RC installer. Since I would plan to use Professional, that's what I selected to install.
The problem is, though, that the product keys that Microsoft delivers to the testers along with these install images is only valid for the Ultimate version. If you select another version at this screen, the install will fail at the product key entry dialog with the vague error "The product key is not valid for the current Windows SKU."
hp calculators available for iphone
2009/06/24 19:55
| computing
MacWorld reports that HP classic scientific calculators are now available for the iPhone, including the 12c and 15C.
Nifty, but a bit spendy. I'm tempted to indulge myself anyway, those things were just the business back in the day (and in many ways, they still are). A functional—and useful—anachronism is always a delight.
Nifty, but a bit spendy. I'm tempted to indulge myself anyway, those things were just the business back in the day (and in many ways, they still are). A functional—and useful—anachronism is always a delight.
why apple wins
2009/06/09 17:40
| computing
Steve Gillmor has an article up explaining why Why Apple Wins Every Time.
I think he's right. What's been happening at Apple, from the changes in the Macs to the iPhones and iPods, right down to the Airport Extremes and Apple TVs, is all part of a recipe that adds up to changing the way people live with technology.
I said it a couple years ago, actually, but when people tie it all together, it'll be amazing. Parts of it already are. Apple's competition really should be looking at what they're doing, but not enough of them are, and the ones that do are copying, which isn't going to be good enough.
I think he's right. What's been happening at Apple, from the changes in the Macs to the iPhones and iPods, right down to the Airport Extremes and Apple TVs, is all part of a recipe that adds up to changing the way people live with technology.
I said it a couple years ago, actually, but when people tie it all together, it'll be amazing. Parts of it already are. Apple's competition really should be looking at what they're doing, but not enough of them are, and the ones that do are copying, which isn't going to be good enough.
comments (1)
computers in the media
2009/05/20 14:37
| computing
Starring the Computer is a neat website that details the appearance of computers in movies and television.
It's well detailed, and I'm impressed at the creator's ability to identify some of the more esoteric hardware from the sometimes poor shots that are available.
From TechCrunch.
It's well detailed, and I'm impressed at the creator's ability to identify some of the more esoteric hardware from the sometimes poor shots that are available.
From TechCrunch.
apologists
2009/04/23 18:56
| computing
It's pretty easy to find a Windows or Mac OS "fanboy" - just post an opinion in any well-traveled discussion site on the internet espousing either, and the rallying cry will go out. There's no shortage of fans of either operating environment, and there's no shortage of wool they'll willingly pull over their own eyes in defense of their pet OS.
A more interesting metric, to me, is to consider how easy it is to find a critic of Windows or Mac OS. It would be fascinating to see actual customer satisfaction results for both operating systems, and enough where you could throw out the obvious "such and such SUCKS" crowds that will invariably gather around either bonfire.
My hunch is that it's easier to find someone who dislikes Windows than it is to find someone who dislikes Mac OS. It certainly seems to be true in my own experience, anyway.
A more interesting metric, to me, is to consider how easy it is to find a critic of Windows or Mac OS. It would be fascinating to see actual customer satisfaction results for both operating systems, and enough where you could throw out the obvious "such and such SUCKS" crowds that will invariably gather around either bonfire.
My hunch is that it's easier to find someone who dislikes Windows than it is to find someone who dislikes Mac OS. It certainly seems to be true in my own experience, anyway.
interfaces
2009/04/22 12:40
| computing
Lukas Mathis on Oberon, a quirky operating system from years past, which evolved from Xerox PARC like our more familiar GUI-based interfaces, but took a different path:
This essentially obsoletes concepts like virtual desktops, application switchers or Exposé since you have as much space as you need on your one desktop, and since you don’t need to rearrange windows in order to get an overview of your open stuff. It’s especially cool on netbooks with tiny screens.
pretty is better
2009/04/21 08:35
| computing
A List Apart on why looks are important to interfaces. Rather the corollory to what Steve Jobs once said: "Design is how it works."
encore!
2009/04/21 08:14
| computing
This Vimeo of Radiohead's "Nude", also performed on vintage hardware, is a very high quality reproduction of the complex, oddly timed tune.
It stems from the remix project Radiohead started when they released the individual mix tracks for the song, which is from their latest album In Rainbows.
If you're not quite as familiar with "Nude" as, perhaps, a track like "Bohemian Rhapsody", you can hear it at Amazon.
It stems from the remix project Radiohead started when they released the individual mix tracks for the song, which is from their latest album In Rainbows.
If you're not quite as familiar with "Nude" as, perhaps, a track like "Bohemian Rhapsody", you can hear it at Amazon.
thinking different
2009/04/21 06:51
| computing
for the record
2009/04/06 06:22
| computing
Sullivan's first iPod, which she had set up in her nursery before she was born, was a black first-generation iPod nano, with 2GB of storage.
Since her parents have gone through so many, it makes me wonder how many she'll own over her childhood, or lifetime if she decides to stick with them. Or what they'll be like when she's my age. Or if they'll even exist at all, in a form I'd recognize.
Since her parents have gone through so many, it makes me wonder how many she'll own over her childhood, or lifetime if she decides to stick with them. Or what they'll be like when she's my age. Or if they'll even exist at all, in a form I'd recognize.
desktop linux
2009/04/02 10:37
| computing
on mail
2009/01/23 22:59
| computing
I'm looking for a replacement for OS X's Mail.app. If you've used something that runs on OS X, and like it, toss me a note.
I'm not interested in web apps (like gmail); I need something that runs locally. Another must is IMAP support.
Thanks!
I'm not interested in web apps (like gmail); I need something that runs locally. Another must is IMAP support.
Thanks!
appropriate internet acronym usage
2008/10/30 15:09
| computing
I'll admit, I've typed "lol" when I haven't actually laughed out loud. However, reading one of Gruber's recent comments did in fact cause me to do just that. Except that I didn't actually type it anywhere.
In any event, here's the cause:
From Daring Fireball.
In any event, here's the cause:
Everyone out there with a stiffy for the “rewritten in Cocoa” Snow Leopard Finder needs to get a grip. Cocoa is just an API. It is not some sort of magic technology where you just sprinkle a ton of square brackets in your source code and you instantly get a better UI.
From Daring Fireball.
behind the curve
2008/09/19 06:12
| computing
Mozilla's Mitchell Baker outlines the company's plans to have a mobile browser by 2010.
Perhaps I'm more of a cynic than previously thought, but in what is quite possibly the hottest segment of the web market today, saying you're going to release something in two years sounds a little like saying "the sun will explode someday".
Perhaps I'm more of a cynic than previously thought, but in what is quite possibly the hottest segment of the web market today, saying you're going to release something in two years sounds a little like saying "the sun will explode someday".
agent 119
2008/09/11 05:41
| computing
Google's new browser Chrome uses this as it's agent string:
That's 119 characters, and as far as I can tell, claims to be every browser on the planet except Internet Explorer.
But, this is what we've come to, amusingly recapped by Aaron Andersen on his blog.
From Daring Fireball.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.29 Safari/525.13That's 119 characters, and as far as I can tell, claims to be every browser on the planet except Internet Explorer.
But, this is what we've come to, amusingly recapped by Aaron Andersen on his blog.
From Daring Fireball.
comments (1)
don't pollute user space
2008/08/26 10:29
| computing
From Apple's documentation for development of software to be published on Mac OS X:
Bioware/LucasArts *
Eidos *
EA
Flip Video
HP
Logitech
Microsoft
Roxio
* via software ports to OS X by Aspyr. I'm not sure who's really to blame.
I hear tell Adobe breaks this rule, too. There are some pretty big names there. I was initially surprised at this, and at the lack of any smaller publishers in the list (I do use a lot of small-house software, also); but I suppose I shouldn't be.
Logitech gets special mention by not actually putting anything in ~/Documents. They drop stuff in the user's home itself, which to me is actually worse.
It is important to remember that the user domain (/Users) is intended for files created by the user. With the exception of the ~/Library directory, your application should never install files into the user’s home directory. In particular, you should never install files into a user’s Documents directory or into the /Users/Shared directory. These directories should only be modified by the user.So far, the software vendors that violate this on just one of my Macs:
Bioware/LucasArts *
Eidos *
EA
Flip Video
HP
Logitech
Microsoft
Roxio
* via software ports to OS X by Aspyr. I'm not sure who's really to blame.
I hear tell Adobe breaks this rule, too. There are some pretty big names there. I was initially surprised at this, and at the lack of any smaller publishers in the list (I do use a lot of small-house software, also); but I suppose I shouldn't be.
Logitech gets special mention by not actually putting anything in ~/Documents. They drop stuff in the user's home itself, which to me is actually worse.
mobile movies
2008/08/14 05:47
| computing
More than one of my iPhone-toting comrades lamented the removal of the iPhone application "Box Office" from the App Store on August 4th. The happy news today is that it's back, and available for download. Before you go looking, though, be aware that the application is now titled Now Playing [opens in iTunes].
The developer of the application, which allows iPhone users to see what's playing in local movie theaters, view ratings from the popular Rotten Tomatoes website via its syndicated feed, and even purchase tickets through Fandango, was unable to reveal why the application was pulled in the first place, citing the NDA that is in force for all iPhone application developers.
There's a pretty good clue, though, in the name change, I'd say.
The developer of the application, which allows iPhone users to see what's playing in local movie theaters, view ratings from the popular Rotten Tomatoes website via its syndicated feed, and even purchase tickets through Fandango, was unable to reveal why the application was pulled in the first place, citing the NDA that is in force for all iPhone application developers.
There's a pretty good clue, though, in the name change, I'd say.
picking strong passwords
2008/07/21 10:06
| computing
I've had a to-do burning a hole in my ... well, my to-do box, regarding how I pick strong passwords that are also easy to remember. So much of our lives are now internet-enabled, or take place wholly on the internet, that having a bunch of passwords to remember is an inevitability. Actually selecting good passwords, though, without having to resort to writing them down, can be pretty tricky.
The Password Chart is an online utility that can help you create very strong passwords indeed, and all you need remember is a phrase and a word. All of the calculations take place in your browser, and you can print the chart (or capture the image) for use when you're not connected.
Clever idea, and I can think of a lot of ways to make use of it.
The Password Chart is an online utility that can help you create very strong passwords indeed, and all you need remember is a phrase and a word. All of the calculations take place in your browser, and you can print the chart (or capture the image) for use when you're not connected.
Clever idea, and I can think of a lot of ways to make use of it.
private notes
2008/07/18 13:35
| computing
os x desktop apps video
2008/07/10 09:08
| computing
While we're on the subject of videos, here's one that was created for The Bird and the Bee's Again and Again using Mac OS X desktop apps - but not as you might expect.
37signals follows my lead
2008/07/06 16:34
| computing
It appears that hot on the heels of my own admittedly bold annoucement to drop support for Internet Explorer 6, 37signals has given IE6 the hook as well.
Just remember folks, you heard it here first.
Just remember folks, you heard it here first.
stating the obvious
2008/07/03 11:35
| computing
You wouldn't think you'd have to tell anyone, but lately is seems like everyone's got their head in the sand, so just as a reminder:
If you have information or behavior that you would consider an invasion of privacy if other people could know about it or search for it, don't put it / do it on the friggin' internet.
If you have information or behavior that you would consider an invasion of privacy if other people could know about it or search for it, don't put it / do it on the friggin' internet.
doin' the iphone shuffle
2008/07/02 18:18
| computing
Recently my iPhone started shuffling all the songs played on its iPod application, even though I hadn't asked it to. No matter what I tried, it shuffled everything by song. There isn't a setting in the iPod section of the Settings app, nor did there appear to be a way to disable the shuffling from the iPod interface itself - at first.
I discovered that while a song is playing and the album cover is visible, tapping the album cover itself brings up a control bar at the top of the display with a time scale and scrubber, and two buttons for toggling repeat and shuffle.
You learn something every day, I suppose, but sometimes learning things through a "discoverable" interface isn't an everyday occurrence. I'm just glad it took me less than a day to figure out.
I discovered that while a song is playing and the album cover is visible, tapping the album cover itself brings up a control bar at the top of the display with a time scale and scrubber, and two buttons for toggling repeat and shuffle.
You learn something every day, I suppose, but sometimes learning things through a "discoverable" interface isn't an everyday occurrence. I'm just glad it took me less than a day to figure out.
firefox 3 optimized for os x
2008/06/23 10:32
| computing
Neil Bruce Lee at BeatnikPad has released his arch-optimized builds of Firefox 3 for Mac OS X.
So far they are available for Intel and PPC G5, with G4 coming soon.
The builds are called Minefield and use a tweaked icon to comply with Firefox branding license restrictions.
So far they are available for Intel and PPC G5, with G4 coming soon.
The builds are called Minefield and use a tweaked icon to comply with Firefox branding license restrictions.
ie 6 now dead to me
2008/06/22 10:25
| computing
Internet Explorer 6 is dead. Dead as in dead and gone, irrelevant, defunct, obsolete. IE7, its replacement, has been out now for 8 months, and if you use IE and haven't yet upgraded, you should. Download IE 7 here.
grapefish.org won't be supporting IE6 any longer. I'm not going to go so far as to remove all the CSS hacks that it takes to make it function, but I'm not going to add any more, and I stopped looking at the site in IE6 a few months ago. It's just too ugly that way, it makes me sad.
If you're on Windows and not using IE at all, or don't want to use IE7, or just want to investigate the alternatives, I'll suggest a few. Firefox just released version 3.0 of their browser. Firefox is a popular open-source browser from the Mozilla project. Firefox supports a robust plugin system that can alter its appearance, behavior, and security features.
Also available for Windows is Opera, a fast, lightweight browser with many of the same features as Firefox. The newest version is 9.5, also released recently.
That's pretty much it for Windows, but on the Mac side of the aisle, there are a few more choices. Firefox and Opera are also available for OS X, and Apple ships their own excellent Safari browser with the operating system.
Other choices include Camino, which uses the same under-the-hood bits as Firefox, but sports a user interface which is designed to be more Mac-like.
OmniWeb is a Mac-only browser from the Omni Group, who specialize in producing applications for the Mac platform. Unique among the options for browsing in that it is a licensed application which costs $14.95 (all the others are free), it includes additional features that no other browser can match.
Its tab bar shows a thumbnail image of the page as it appears (even supporting refreshes and indicating a page has changed with a small badge), which makes it much easier to select a particular tab for much the same reason that Exposé is better than meta-TAB.
The Workspaces feature allows you to save your current browser state, including tabs, history, and window sizes and location, and lets you save and update more than one of those states.
Lastly, OmniWeb supports per-site preferences, which allows you to custom-tailor options on each domain you regularly visit.
A couple other Mac browsers that are available are Shiira, an open-source Safari competitor that also has thumbnail tabs (but doesn't indicate updated sites); and iCab, a shareware ($25.00) browser based on Apple's WebKit, with a robust download manager and site archiving capability.
grapefish.org won't be supporting IE6 any longer. I'm not going to go so far as to remove all the CSS hacks that it takes to make it function, but I'm not going to add any more, and I stopped looking at the site in IE6 a few months ago. It's just too ugly that way, it makes me sad.
If you're on Windows and not using IE at all, or don't want to use IE7, or just want to investigate the alternatives, I'll suggest a few. Firefox just released version 3.0 of their browser. Firefox is a popular open-source browser from the Mozilla project. Firefox supports a robust plugin system that can alter its appearance, behavior, and security features.
Also available for Windows is Opera, a fast, lightweight browser with many of the same features as Firefox. The newest version is 9.5, also released recently.
That's pretty much it for Windows, but on the Mac side of the aisle, there are a few more choices. Firefox and Opera are also available for OS X, and Apple ships their own excellent Safari browser with the operating system.
Other choices include Camino, which uses the same under-the-hood bits as Firefox, but sports a user interface which is designed to be more Mac-like.
OmniWeb is a Mac-only browser from the Omni Group, who specialize in producing applications for the Mac platform. Unique among the options for browsing in that it is a licensed application which costs $14.95 (all the others are free), it includes additional features that no other browser can match.
Its tab bar shows a thumbnail image of the page as it appears (even supporting refreshes and indicating a page has changed with a small badge), which makes it much easier to select a particular tab for much the same reason that Exposé is better than meta-TAB.
The Workspaces feature allows you to save your current browser state, including tabs, history, and window sizes and location, and lets you save and update more than one of those states.
Lastly, OmniWeb supports per-site preferences, which allows you to custom-tailor options on each domain you regularly visit.
A couple other Mac browsers that are available are Shiira, an open-source Safari competitor that also has thumbnail tabs (but doesn't indicate updated sites); and iCab, a shareware ($25.00) browser based on Apple's WebKit, with a robust download manager and site archiving capability.
the new hotness
2008/06/09 14:11
| computing
iPhone software version 2.0 is announced for release in early July, offering Exchange support, VPN, and other business functions, as well as the App Store for 3rd party applications.
Also early in July, the next iPhone hardware version will be available in a 3G handset. An 8GB version is $199, and 16GB will set you back $299, but you get your choice of colors (as long as your choice is one of black or white). New features include high-speed "3G" data (HSDPA), assisted-GPS, and "dramatically improved audio".
Considering the $399 current price (and $599 introductory) of the current model, the new prices are an absolute steal. A 32GB model would have been a slam-dunk for my upgrade, although it's really tough not to swap for the new features alone.
Also early in July, the next iPhone hardware version will be available in a 3G handset. An 8GB version is $199, and 16GB will set you back $299, but you get your choice of colors (as long as your choice is one of black or white). New features include high-speed "3G" data (HSDPA), assisted-GPS, and "dramatically improved audio".
Considering the $399 current price (and $599 introductory) of the current model, the new prices are an absolute steal. A 32GB model would have been a slam-dunk for my upgrade, although it's really tough not to swap for the new features alone.
itunes u
2008/02/24 08:01
| computing
I recently sent this off to a teacher friend, but I've been finding a lot of interesting stuff here, too. It's iTunes U [opens in iTunes], which has resources for educators, almost all of which are available free of charge. WGBH [opens in iTunes] has a bunch of episode snippets from NOVA available, for example. Full episodes of the science show are also available from iTunes via a season pass.
apple in the server space
2008/02/24 07:56
| computing
MacTech with their take on Apple's recent Xserve RAID being discontinued. The upshot is that Apple is thinking more about enterprise, not less.
Dropping the RAID is simply Apple saying to itself “we can’t add value here, and there are other good solutions.”
a little perspective
2008/02/24 07:47
| computing
Fake Steve Jobs posting about Microsoft's recent announcement about their plans to interoperate with open source software. No, really this time. The most striking paragraph to me was this one, which shows just how much of a lead Microsoft has in the OS arena:
Red Hat isn't the only company in the Linux sphere, but the only other one with any enterprise penetration is SuSE (part of Novell), and they're smaller yet.
Red Hat, the single company freetards always point to when they want to prove that open source can make money, has turned into an inept clusterfuck, with nothing but bluster and bravado and a deluded belief that they're actually a thorn in Microsoft's paw. Bottom line: they're the new Borland. They're 15 years old and have been publicly traded since 1999 and last year they did all of $400 million a year in sales. Microsoft does more than $1 billion a week. That's right. Red Hat's entire fiscal year is a good three days for Microsoft. Last quarter the Borg added $2.6 billion in revenues -- that's six entire Red Hats. In a quarter.
Red Hat isn't the only company in the Linux sphere, but the only other one with any enterprise penetration is SuSE (part of Novell), and they're smaller yet.
easy storage solution
2008/02/19 08:46
| computing
Data Robotics produces a nifty storage unit for home networks called the Drobo. You can just slide in SATA disk drives, any size or speed, even while it's running live, and it just does it all for you. A review from Andy Ihnatko has more, including information on an add-on which shares the device over a network.
From Daring Fireball.
From Daring Fireball.
the skinny on that fat pipe
2008/02/14 07:15
| computing
Comcast files with the FCC [PDF] in response to the investigation the regulator launched, detailing the methods used to manage network bandwidth. The cable provider has also updated its terms of service.
Commentary at Ars Technica. Turns out Comcast is doing exactly what everyone suspected; sending RST packets to both sides of a connection to delay peer-to-peer connections, but they say only when there's more upload traffic than download.
Commentary at Ars Technica. Turns out Comcast is doing exactly what everyone suspected; sending RST packets to both sides of a connection to delay peer-to-peer connections, but they say only when there's more upload traffic than download.
hd-dvd all but dead
2008/02/11 15:54
| computing
Reuters has a story on Best Buy's decision to back Blu-ray, one of the major competing formats for a high-definition version of the DVD-Video standard. Earlier today, Netflix also announced it would phase out HD-DVD in favor of Blu-ray.
With several major studios also having dropped HD-DVD for Blu-ray in the past weeks, it seems like there are an awful lot of nails in the coffin.
With several major studios also having dropped HD-DVD for Blu-ray in the past weeks, it seems like there are an awful lot of nails in the coffin.
cross-platform encryption
2008/02/07 16:59
| computing
TrueCrypt 5.0 has been released, an open-source encryption utility which now has support for Mac OS X and Linux (older versions supported only Windows). Other new features include whole disk encryption, which is excellent for laptops. I like Traveler Mode, also, which lets you run the utility and mount encrypted virtual drives from a USB drive or the like, even if the application isn't installed on the computer you're using.
Give it a look if there are things you should be encrypting but aren't (and I'll bet there are).
Give it a look if there are things you should be encrypting but aren't (and I'll bet there are).
help for windows vista... box
2008/02/01 08:48
| computing
Spotted this on Daring Fireball. Microsoft has a help page for opening the Windows Vista packaging.
I don't have anything to say about that.
I don't have anything to say about that.
iphone speed dial url
2008/01/24 11:51
| computing
Thanks to helpful tips posted at MacNN and Lee Fernandes' blog, grapefish.org now sports a fancy new PHP script you can use to create speed dial icons for your iPhone. The URL is here:
http://www.grapefish.org/call.php?n=[phone]&i=[icon].png
Type this into Safari's URL bar, and insert the number to dial in place of "[phone]" and one of "wrk", "hom", or "mob" in place of "[icon]"to get a custom icon for Work, Home, and Mobile numbers. When you tap Go, Safari will ask if you want to dial the number. Tap Cancel, and then the "+" icon at the bottom of the screen. Select Add to Home Screen, and then give the shortcut a name.
Voilà. You do still have to tap twice to actually make the call, but this can be handier than going through the Phone app itself.
http://www.grapefish.org/call.php?n=[phone]&i=[icon].png
Type this into Safari's URL bar, and insert the number to dial in place of "[phone]" and one of "wrk", "hom", or "mob" in place of "[icon]"to get a custom icon for Work, Home, and Mobile numbers. When you tap Go, Safari will ask if you want to dial the number. Tap Cancel, and then the "+" icon at the bottom of the screen. Select Add to Home Screen, and then give the shortcut a name.
Voilà. You do still have to tap twice to actually make the call, but this can be handier than going through the Phone app itself.
more leopard dock tricks
2008/01/23 00:13
| computing
One of the little tricks I've been using pretty much every day in OS X 10.5 ("Leopard") is a "Recent Items" stack in my dock. By default, it shows a grid of recently used applications, but a Ctrl-Click gives you a list of options; you can have the stack contain any of recent Applications, Documents, Servers, Volumes, or a list of Favorites. The following command enables this little gem:
defaults write com.apple.dock persistent-others -array-add '{ "tile-data" = { "list-type" = 1; }; "tile-type" = "recents-tile"; }'rogue amobea's live disc
2008/01/03 18:45
| computing
A neat idea from Rogue Amoeba, a CD that contains an application link to their software. Launching the program from icon (either on the Live Disc or after dragging to your Finder) results in one of two things happening - you run the currently installed version on the local drive, or download the latest and run that instead.
quicktime rstp flaw patched
2007/12/15 09:27
| computing
putting a leash on the leopard
2007/12/01 10:03
| computing
allows Mac OS X Leopard users to--not surprisingly--schedule Time Machine backups. Ordinarily running once per hour, the utility allows a Mac admin to adjust the timing to up to 12 hours via a launchd item which replaces the default Time Machine scheduler.
mac software deals for x-mas
2007/12/01 09:17
| computing
of two different holiday season software promotions for Macs. There's
for a daily rotating promotion at
, and European software developers have another site offering discounts at
. If anyone wants to buy me presents, I can offer suggestions!
ack: a perl-powered alternative to grep
2007/11/27 11:22
| computing
Targeted mostly at developers with large source code trees; also useful for using perl-like regular expressions in grep-like searches. Vist the
for more information, downloads, and installation instructions.
