Dr. Christopher Kunz

(EDIT: mod_spdy seems to cause massive issues with mod_php, so I disabled it again. I am seeing lots of PHP segfaults as soon as I enable mod_spdy - these disappear as soon as it is disabled.)

This website (as long as you access it via HTTPS) is now serving pages with SPDY, Google’s still-experimental web acceleration protocol. Since SPDY mandates usage of SSL, I am using a CACert certificate to serve up pages. If you want to know why I didn’t buy a CA-signed certificate, please see this talk for a couple thoughts: SSL and the future of web authentication (PDF)

The reason this posting lands in the PHP category is that I want to have a playground testing PHP applications with mod_spdy. Currently (and probably also in the future), this machine uses mod_php instead of php_(f)cgi(d) - this is not recommended for interoperation with mod_spdy. To test the real-life impact of the possible thread safety issues, I am using my private pages as a sandbox.

 So, please test away. There is a couple of PHP applications here that might or might not work:

• A recent, PHP 5.4-patched Gallery3 installation is under https://gallery.christopher-kunz.de/


• A Wordpress installation is here: https://absynth.de/

If you have any comments, especially if you can share success stories about mod_spdy and PHP, or just want to see how SPDY performs, please comment away!

Update: You can check if you’re using SPDY already by looking into the following little page, iframed for your convenience: SPDY check

During my morning routine, I found this interesting read at Jeremy Shoemaker’s blog (he’s a highly influental, if not guru-like person in the SEO scene): What X-Googlers are saying after leaving. Although I don’t fully get everything said there (the health insurance and wage systems in the US and Germany are very different, or at least use very different terms), it’s a very enlightening piece.

It seems that many of the very, very, very long list of posters (I only read about 1/3 of the whole article which can eat your morning without problems) aren’t really disgruntled with Google, but almost no one fails to mention the relatively low pay that is supposedly made up for with, and I quote,

the conversation piece of ‘working at Google’

. The perks do sound interesting and I guess if you know what you are up to, you can have a very enjoyable time at the Kraken...

For all those who still think a job offer at Google is like a jackpot, this might change a couple of minds. They are, which is not really a surprise if you come to think of it, after all an employer like all others.

(via ShoeMoney Blog, turns out this is already here and here, amongst others.)

Gerade kam eine Mail von Google:

wir bedanken uns für Ihre Teilnahme beim Empfehlungsprogramm von
AdSense. In der letzten Augustwoche werden wir das
AdSense-Empfehlungsprogramm einstellen. Danach werden keine
Anzeigen mit dem AdSense-Empfehlungscode mehr angezeigt.

Ich hatte mal kurzzeitig Empfehlungen auf ein paar Seiten (u.a. auch hier und dort), die Rate war aber unter aller Sau. Das scheint auch der Gugelhupf erkannt zu haben und das komplette Programm wird eingestellt.

Ohne großartige Ursachenforschung betreiben zu wollen (das können andere sicher besser, die sich mehr mit der Thematik beschäftigen): Mir fiel beim ersten Drüberschauen auf, daß die Anzahl der wirklich ordentlichen Werbepartner (die nicht z.B. mit einem Handlexikon ihre englischen Recommendations übersetzt haben) begrenzt war, Targetting auf originär deutsche Angebote schwer fiel (nur mit Kreditkarte bezahlbare englischsprachige Online-SPiele z.b. konvertieren mal so gar nicht) und das gesamte Recommendations-Programm einen eher unfertigen Eindruck machte. Aber das nur von mir als subjektive Meinung.