Take a look at this screenshot:
The 4th fastest growing blog shown there is a spam blog. I thought wordpress.com was having troubles with spam blogs soon after they launched. And I thought they devised a way to prevent it for the most part. I wonder if the spammers have come up with a new method to do their trickery…
Isn’t it about time for Beta 1 of Slackware 11 to be released? I’d surely think so, especially with all the updates being made to the slackware-current changelog lately. I was thinking that Patrick would take a chance and make 2.6 the default kernel in Slackware 11, I don’t think that’ll happen now. 2.4.32 or 2.4.33 will most likely be the default kernel found in Slackware 11. I say this due to the changes that have been made to the kernel 2.4.32 packages in -current.
I’ll continue waiting patiently for Slackware 11 Beta 1…
WordPress.com, the free blog hosting site based off WordPress, is getting ready to allow users to use their own domain names in conjunction with the wordpress.com service. What’s that mean? You will be able to setup a domain to point to your wordpress.com blog.
For example, I blog at http://slackware.wordpress.com. If I bought the slackwareblog.com domain, I could point it to slackware.wordpress.com. So, slackwareblog.com would essentially be running on top of WordPress.com. It’s a lot like gmail for your domain.
Right now, WordPress.com is only testing this feature out, offering it to the first 8 people to comment on the WordPress.com blog post discussing the new feature. I’ve been wishing for this feature since I started using wordpress.com, glad it’s finally on the horizon.
On a related note, “92.63% of the traffic to WordPress.com is for blogs outside of the top 25.” I figured it’d be lower than that, but that’s pretty impressive for those outside the top 25.
Wombats don’t like to fight. Some guy in Toledo had a bunch of Wombats in an attempt to start a wombat-fighting ring. Apparently he was pretty upset when his Wombats didn’t exhibit any violent behavior:
“The bastard who sold them to me said they were vicious killers,” said Kensington. “I paid $300 bucks for a pair of eucalyptus-leaf eating retards who just stare at each other with a dull glare.”
Kensington tried many techniques to get the wombats to fight, but all they would do is “eat and breed.”
“Yeah, I tried poking ‘em with sticks, yelling at ‘em, and dumping acid on their heads, but nothing seemed to work,” he said. “They just sit there and stare at you, drooling and grunting.”
The animals, said Kensington, have been a bad investment, and he was “relieved” when police arrived.
“Not only will they not fight, but they dig their way out of every kennel I’ve built,” he said. “Good riddance, I say about the smelly bastards.”
Dumb ass.
WordPress 2.0.4 has been released.
WordPress 2.0.4, the latest stable release in our Duke series, is available for immediate download. This release contains several important security fixes, so it’s highly recommended for all users. We’ve also rolled in a number of bug fixes (over 50!), so it’s a pretty solid release across the board.
I can’t find any documentation stating the user registration vulnerability has been fixed, but Kelson is reporting it has been taken care of in WordPress 2.0.4. I believe this WordPress release was pushed out quickly due to some information revealed by Dr. Dave earlier in the week.
I’m still not 100% sure that the problems pointed out by Dr. Dave have been fixed. Can anyone confirm that it has been? For those interested, here’s a list of bugs that have been closed as of the 2.0.4 release [via Dougal Campbell].
UPDATE: WordPress 2.0.4 does indeed fix the user registration vulnerability. Dr. Dave has done some testing of his own and seems pretty sure this vuln is fixed. It’s still probably a good idea to disable user registration just to be safe:
As for the “users can register” option: enabling it back should be OK.
I personally will leave it off on my blogs, as I just don’t feel like entrusting strangers with access to wp-admin in the current state of the code (I insist that the aforementioned exploit has been fixed now, I am only being paranoid here).
