MyBlogLog Spam Getting Worse? I’d Say So.
This morning, I checked my email to see that I was invited to be a coauthor the “Blogmeme_Belgium” MyBlogLog page (I won’t link directly to the page because the load time is horrendous with all the authors who have signed up — there are at least 300 of them and their avatars ALL load on the sidebar). Beyond the number of authors, there are 188 members in the community.
Since I have no involvement with this site, I didn’t accept the invitation. Apparently, I wasn’t the only one:
The strange thing is that this is the only rejection that I was able to visibly acknowledge (though I am sure that most people did not accept the invitation — those 300 people who did are a small chunk of the people who appeared to have been invited!). Sadly, a good amount of my blogging buddies actually blindly joined this spammy community!
One of the smarter “coauthors” made sure to label the community appropriately:
The gamethis.com URL links to an ebay auction, where someone was looking to sell the domain name (and did for $1200). What it comes down to is this: this was certainly unwanted spam.
I know that Scott and Eric (and even Jeremy) are aware of the easy ways people can game MyBlogLog for personal gain. I know this problem is being “addressed” and I’ve been relatively impressed by their promptness in answering these concerns in various blog comments. But I think there are some major issues that need to not just be “addressed” at this point — they need to be fixed.
Here’s something else I noticed. This screenshot was taken no more than 10 minutes ago on one of the community pages:
With the absence of registered author for Boing Boing on MyBlogLog, there’s absolutely nobody to police the comments that are being posted to its wall. I’m not particularly sure that boingboing.net would condone advertising for the “top nude babes.”
My requests for today are hopefully very simple to implement:
- Kill that Belgian community and do something about the person who started it. It’s hogging resources on the client-side (and probably on the server side too).
- Either ban URLs from being posted to the “community messages” or prevent people from posting on boards that lack a proper owner. A better option would be to email the assigned owner every time a new comment gets sent. Since I have my own personal page and four blog pages to check and no way of being notified when anyone posts to either, every time I log on, I end up manually having to check these five pages to see if something new came up.
- Instead of having a “report spam” message as a mailto: link, embed a proper mail form on your website. I actually don’t have any mail application set up on this computer and Outlook always asks me to configure it whenever I click on that link.
I know that MyBlogLog has a lot of potential, but if it’s not able to properly deal with a slew of problems, it may just end up ostracizing its most loyal users. I hope that I could see prompt fixes to all aforementioned problems.
Update: This is what I call great customer service. Thanks, Scott and Eric!
Update 2: Here’s the official reply from the MyBlogLog team. These are welcome measures for sure. Thanks again for reading, commenting, and best of all, listening.