Warning: strtotime() [
function.strtotime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
35
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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
35
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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
43
by dbasch — 3 Comments »
We have been keeping track of the public Twitter timeline for a few months now. Until a few days all Twist showed was a 7-day window, but now you can select monthly and historical trends. For example, it seems that in late April people start talking more about the summer than about the spring:
Also, you [...]
Warning: strtotime() [
function.strtotime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
35
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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
35
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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
43
by dbasch — 5 Comments »
Web apps are a lot like TV shows. In particular those that are supported by ads, because their source of revenue is the same and the viewer/user is not really the customer but the product. These days it seems that everyone has some advice for Twitter about possible business models. I really don’t think the [...]
Warning: strtotime() [
function.strtotime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
35
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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
35
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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/dbasch/www/blog/wp-includes/functions.php on line
43
by dbasch — 2 Comments »
When I think of a successful web application, I picture one that has millions of users and runs smoothly (it works fast and it does not crash). Of course, very few are like this. Perhaps the first example that comes to mind is something like Google Search. In the following chart, Google Search is in [...]
