Site Update: Community Blogs patches *incoming*   |   Report a bug

  From our Community Blogs

Papa Niero says:

Welcome to Destructoid's new server! Also, cocks filter testing

// Submitted @ 5:01 PM on 01.06.2009


As promised we've migrated to new server hardware as of last night. We moved the site from a cluster of overpriced Pentium 4 computers to mo' betta Quad-core Xeon systems to keep up with the ever-growing number of Tyra Banks photos uploaded daily. Seriously though, Destructoid serves over 100 gigs of bandwidth a day and its been a real mission to maintain that from preventing the site from grinding to halt. The fix also appears to have resolved the issue where the page stopped loading halfway randomly. Most of the other patches were for things the editors needed, not worth mentioning. While its an improvement we're still making various changes that will continue to speed page load. Its an uphill battle.

I'd also like to thank Necros for the epic post yesterday and wanted to respond to point 9 addressed to me. Did you know that "cocks" was actually not supposed to be filtered from the page page? It was intended to only filter the singular "cock" as to not interfere with the tradition. So what happened? Previously it might have written "Lobster Milkshakess", clipping the root word because (a) I suck at programming and (b) didn't notice until someone pointed it out to me. I changed it to "cock " with a space, that should fix it. I also wanted to note that we don't actually filter on the cblogs pages or wordswap them in the editorial at all -- its primarily so that Google doesn't flag Destructoid as an adult site. We're happy to be your best source for beast and location otherwise.
Photo

FIRST YOU GET THE BABY
Then you get the power: Popular blogs may get homepage'd




Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.