*We*, the systems@ people were making decisions in realtime to combat
the load.
Don't give me crap about unilateral decision making; we spent a lot of
time on this yesterday, trying many different approaches to make things
work, different server software configurations, bandwidth throttling,
content compression etc. etc. etc. etc!
So I am one poor guy alone, who probably has no ideas, and anyway you always better know what's good for the server and for our users. Should I be happy to left out of the decision making? I was one guy who replied most of the support mails sent because of strange things happening on php.net (which were sometimes caused by me, sometimes caused by others).
In the end, at 3am (my time) *we* decided that we would go for
the current search engine redirection because not enough mirrors
supported the ht://dig system and too much load was still evident and
too many people were using these inefficient magic URLs.
Heh, it seems that the load on php.net was very high these days. Does that mean that the recent PHP events were a big success and now everybody is interested in PHP? Cause we had no major change on php.net to affect the search usage or the shortcut usage in months. Your words seem to suggest that the machine was on it's edges, and very quick measure needed to put in without any *open discussion*.
Now, if all the mirror maintainers all set up ht://dig, we can still make
use of it and not have to rely on google; I don't care how it looks to
people outside; I care about having the box running.
As I've tried to emphasize several times now *this is a temporary
measure*, taken after trying a whole range of different techniques to
avoid the hardware blowing up.
I am not convinced that having postponed this stuff some hours, a better temprorary measure would not be good. As *you* [the systems@ people] have shut down the public stats of php.net months ago, the "outsiders" [me for example] have no cluce if the server was on it's edges in the last hours. I was only able to see that the situation was probably the same for months now, and a discussion for a few hours would not hurt much for the server. But that is how I see the things from *outside*.
Sure, we can revert, but then we won't have a machine left alive to run
the site.
I have not requested a revert. I have requested a discussion and a possily better decision. I have not requested a revert.
Now, lets stop bitching and start fixing the phpweb so it plays nice on
the hardware?
As said, I don't know *The Way* to solve the problem, I think discussion is needed. You keep on saying that instead of any discussion, we need to fix it. I am not going to call Rasmus on myself, to let him say "this is not the way things are done here" [without discussion].
I am going to go offline now, and let those who know the holy things do the right thing without intervention.
Goba