We are planning to put a CDN in front of our Drupal install. This CDN is not fancy and is not able to deal with cookies (but it's very cheap). So every anon visitor is going to be served from ANON DOMAIN (the CDN) and every logged in visitor is going to be served from LOGGEDIN DOMAIN (our servers).

This surfaces some questions, such us:

• what will happen to those visitors who are visiting the wrong domains? For example: an anon visitor visits a url from the LOGGEDIN DOMAIN or vice versa, a logged in user visits a url from the ANON DOMAIN.

This is more a comment to Nedjo's recent post than anything else. Currently http://drupal.org/node/271216 blocks a lot of work -- it is indented to lessen the hardwiredness mentioned in the article and also further testing.drupal.org . It'd be great if people would help with testing the patch -- I admit, not easy but the Drupal.org Testing profile helps you. As the functionalit is mostly API, we need code reviews and coders to write some PHP and see whether they can indeed change the various properties of an issue with a single function call as the patch purports.

If you are coming to Szeged then please don't forget to bring a bar of chocolate for the Awesome Testing Party. Two, do attend the testing party if you can write PHP code. Catch, cwgordon7 and myself have already filed a "couple" issues so noone will be bored... and I will try to hard to make sure there will be pancakes :)

As already mentioned on my twitter, I have sold my apartment in Budapest, threw out or gave away most of my possesions and on September 1 I join the Vancouver Drupal user group for good :)

If you have a development only website then you probably have basic auth over it, just to keep the prying eyes away. It is, however, quite daunting to always OK the many password dialogues. A little rewrite magic helps:

RewriteEngine On
RewriteCond %{HTTP:Authorization} "^Basic dGVzdDp0ZXN0"
RewriteRule ^ - [co=test:test:.development.example.com:1440000:/] [L]

RewriteCond %{HTTP:Authorization} "!^Basic dGVzdDp0ZXN0"
RewriteCond %{HTTP_COOKIE} !(^|\ |;)test=test;
RewriteRule ^ - [R=401,L]
Header always set WWW-Authenticate "Basic realm='development'"

As Drupal, PHP is also moving -- and it moves fast. On June 16 Christian Seiler suggested adding lambda and closures to the language and on August 1 the first alpha of PHP 5.3 containing this and more is out. And we thought the language will never get them...there are other niceties -- just one question remains, how long before Drupal can use this?

So, Moonshine discovered that Drupal 6 supports #pre_render and even #post_render which was so obscure that even I did not remember it off head. So, he documented them in the Monster Form API table. And then went on and blasted the <font> tags too. w00t, w00t! No lines of PHP written -- but still such an awesome contribution. Thanks!

I have no idea how could this slip for three years. Dries said Can't we cool up the throbber a bit? (Make it a rotating Druplicon or something. ;)) in this comment. If you can, please make a throbbing Druplicon (I think that's better than a rotating one) and submit to the issue please. It's very important -- it would make a number of developers very happy :D

The Szeged DrupalCon is up and coming. There will be lots of fun, but the most important is the testing party webchick organizes. Make sure you vote on it. Also make sure that you are attending and helping core. We have lots of tests to write.

This is a tough problem. To watch full HD movies on a computer, you need something which is beefy enough to decode H.264 and VC-1 and yet quiet -- and still, does not cost a fortune. At this moment, you are looking at an Intel Core 2 Duo E7200 CPU at least. Building a whole machine around it will set you back about $5-600 . And then you need an OS. Windows?