Maybe they don't but they have realized that their spam profiles on drupal.org are too short-lived to get them much traffic. As a result of this, the number of new spam profiles seems to be down.

As a side note: In part due to the spam profiles and the google traffic that they generated drupal.org served more than 30 Mio pages in March. This is an increase of about 38% compared to February with 22 Mio viewed pages.

The bigger part of this surge can probably be attributed to DrupalCon at the beginning of March.

Here's a table of the number of 403 pages by month:

After amazon and wikimedia the Drupal association has decided to opt out of the Phorm webtraffic snooping scheme. It is quite scandalous that one has to opt-out instead of having the option ot opt-in, but we did it anyway. We got the same auto-reply that wikimedia got, let's see if we get any more detailed response later.

I've recently been looking into the spam that hits drupal.org and yesterday I've finally found out why they do that and that it actually works. Until I block the accounts at least.

A blocked a account will give any visitor a "403 access denied" message. Drupal logs these incidents. It also logs the referer of these requests, so I am able to see which page the visitor was looking at when he clicked on the link to the blocked account. Most of these pages are search resulte of google and other search engines. And of course the visitor was looking for porn of all different flavours.

Last week I blogged about the spammers on drupal.org and how we remove their accounts. This week I've again looked at the newly created accounts and also added some other domains to the access rules (mainly aliases of mailinator.com).

There is one new player on the mail provider list. Apparently somebody created a domain to use for mail in order to be able to register at sites like drupal.org. And that they did: they created almost 500 accounts on d.o during the last week. They are of course all blocked now.

It is now several weeks after the upgrade of drupal.org to Drupal 6 and I've taken a look at google's crawling statistics for drupal.org.

This is the most interesting graph for me as infrastructure manasger, it shows the average time that googlebot needs to download a html page from drupal.org. We apparently had a bit of a rough ride in January, but recently this has smoothed out. About 600ms per page seems quite a good value to me.

So, after I claaimed we'd have less spammers than others, I wanted to find out how many spammers we've actually had.

mysql> select EXTRACT(YEAR_MONTH FROM from_unixtime(created)) as yearmonth, count(*) as count from users where status = 0 and login != 0 group by yearmonth order by yearmonth desc ;

On drupal.org we have much less spammers than other websites. One reason is the fact that we do not allow anonymous users to post anything and that every user needs a valid mail address in order to use his account.

This poses the question: Which email providers to our spammers use?

Luckily, this is rather easy to answer:

mysql> select substring_index(substring_index(init, '@', -1), '.', 1) as provider, count(substring_index(substring_index(init, '@', -1), '.', 1)) as count from users where status = 0 and login != 0 group by provider order by count;

Narayan Newton and I gave a talk at Drupalcon on the state of the http://drupal.org infrastructure. Narayan, Gerhard, David, and myself are currently working on a infrastructure budget proposal for the Drupal association. This proposal will give you some insight into the challenges of running Drupal.org and why it is not just another Drupal site. In fact, our use of Drupal as a web application platform for Drupal.org pushes the Drupal project in many directions that lead to innovation.

The Drupal association has been using CiviCRM for a couple of years now. As part of the redesign effort we upgraded the Drupal association site to Drupal 6 and CiviCRM 2.1.

With the help from the Donald Lobo of the CiviCRM team and David Strauss we now have automatic membership renewal notices working in CiviCRM 2.1. With previous versions we had technical difficulties with membership renewal notices and would send renewal reminders out in batches.

For the last several years, Angie Byron (aka webchick) has done an outstanding job coordinating Drupal's participation in the Google Summer of Code program. This year, however, Angie has the additional responsibility of being a core maintainer for Drupal 7.

Earlier this year, Angie put out a post asking for help in the Summer of Code 2009. Alex Urevick-Ackelsberg responded, and has been working with other members of the community to prepare for SoC 2009.

So this year, Alex will be Drupal's "organization administrator," or point person within the community for the SoC. In this role, Alex will have a number of duties, and will need your help!