{"id":633,"date":"2007-09-26T08:01:21","date_gmt":"2007-09-26T15:01:21","guid":{"rendered":"http:\/\/montaraventures.com\/blog\/2007\/09\/26\/blogrush-update-update\/"},"modified":"2007-09-26T08:04:33","modified_gmt":"2007-09-26T15:04:33","slug":"blogrush-update-update","status":"publish","type":"post","link":"https:\/\/montaraventures.com\/blog\/2007\/09\/26\/blogrush-update-update\/","title":{"rendered":"Blogrush Update, Update"},"content":{"rendered":"

Guess I should have waited a day before posting the Blogrush<\/a> update. In the mail this morning, I received a missive from the Blogrush<\/a> team. I’ll post excerpts below with some commentary.<\/p>\n

\nThe BlogRush team has been hard at work making major improvements
\nfor you and we won’t rest until BlogRush is running 100% smoothly and
\nsending you tons of targeted traffic! This is OUR MISSION. Please
\nknow that our entire team is working around-the-clock to make
\nimprovements and fix any problems AS FAST AS HUMANLY POSSIBLE.\n<\/p><\/blockquote>\n

Given that this has been released a little over a week, I’d say they’re pretty darned responsive thus far.<\/p>\n

\nWe’ve encountered some problems since our historic launch just over a
\nweek ago, and we fully recognize that we’ve made some real ‘goofs’
\nwith the system for our Public Beta release…<\/p>\n

For example, our data center provider (one of the largest in the
\nworld) had a short, temporary outage (they had to replace a network
\nswitch) two days after our launch. We had no control over this
\noutage but want to SINCERELY APOLOGIZE to those that saw this
\nmessage on their blogs (where the widget should have been):<\/p>\n

“We are currently experiencing some technical issues and the site
\nwill be back online shortly. Please come back in a few minutes.”\n<\/p><\/blockquote>\n

This is a problem. I saw the message and was irritated by it. Glad to know it’s now fixed. <\/p>\n

\nWe also realize that we completely underestimated the number of
\nunethical people that would sign up and proceed to CHEAT and try to
\n‘game’ the BlogRush system. These cheaters ruined the click-rates of
\nmany of our members (and burned through a lot of their credits using
\nautomated ‘exploit’ methods) and hurt BlogRush’s ability to send
\nmaximum traffic to our honest members’ blogs.\n<\/p><\/blockquote>\n

It was very clear to me from the outset that the very first thing people would do is try to game the system. It’s human nature on the interenet (unfortunately.) Since there was no money changing hands, I was comfortable with the risk of early adoption. The worst outcome that could happen is that traffic wouldn’t be referred and crappy links would show up in the widget. Unfortunately, thus far that’s what we’ve seen. But, it’s early days yet.<\/p>\n

\n100% MANUAL BLOG REVIEW.<\/p>\n

Our team is going to be manually reviewing every single new blog that
\nregisters to participate in the BlogRush Network.<\/p>\n

…<\/p>\n

Our members, like YOU, made it LOUD AND CLEAR to us… BlogRush
\nneeds to only have members that have quality blog content — not blogs
\nfilled primarily with ads and other spammy looking JUNK.\n<\/p><\/blockquote>\n

Glad you realize this Blogrush<\/a>, the service will fail if it’s content light. Real bloggers who write real content that people read can actually use your service. When the signal to noise ratio is low, no one will ever click a link from the widget. 100% manual review sounds very expensive though, I hope you can maintain throughput whilst making the human touch.<\/p>\n

\n**** A LOT MORE CATEGORIES! ****<\/p>\n

…<\/p>\n

**** IMPROVED REPORTING! ****<\/p>\n

The current Dashboard stats are being under-reported for all users
\nright now. This is the reason that users show discrepancies when
\nlooking at Google Analytics data (or other stats packages). We’re
\ncurrently sending more traffic to our users than we’re reporting in
\nthe Dashboard because we are giving all users bonus credits
\neveryday. We’ll soon be reporting all bonus credit activity so all
\nthe numbers will be accurate.<\/p>\n

…<\/p>\n

**** IMPROVED NETWORK DISTRIBUTION ****<\/p>\n

A few of our users have noticed that they’re building up credits
\nfaster than the system is using them.<\/p>\n

…<\/p>\n

**** BLOGRUSH “FLAVORS” ARE NOW ACTIVE!<\/p>\n

You can go login to your account, click the “Settings” tab and then
\nselect “Flavors.”<\/p>\n

You can choose from (13) different widget colors. You no longer have
\nto only use our original “black” widget design that many users
\nthought was ugly! (Hey, just don’t let our lead designer hear
\nthat… he thought his black design was “really cool.”)<\/p>\n

…<\/p>\n

***** BLOG POST CONTROLS *****<\/p>\n

Under the “Settings” tab you’ll also find a new option called, “My
\nPost Control.” Here’s what this awesome new feature does…<\/p>\n

You can create POST FILTERS for your blog posts…<\/p>\n

For example, you can add a keyword or phrase and create a new post
\nfilter. If you ever create a post on your blog (while you have that
\nfilter active — and you can add\/delete them at anytime) that
\ncontains one of those keywords in the TITLE of your blog post, that
\npost…\n<\/p><\/blockquote>\n

These are all needed improvements to help the experience along. Thus far, while disappointed with the performance of the Blogrush<\/a> service, I am impressed with the commitment and speed of the improvements. There’s a long way to go, but this tool just might prove to be as useful as I thought when deciding to give it a whirl…We’ll see how all this shakes out and I’ll write another update in a couple of weeks with my experience to date. Blogrush<\/a>, I salute your vigor and enthusiasm!<\/p>\n","protected":false},"excerpt":{"rendered":"

Guess I should have waited a day before posting the Blogrush update. In the mail this morning, I received a missive from the Blogrush team. I’ll post excerpts below with some commentary. The BlogRush team has been hard at work making major improvements for you and we won’t rest until BlogRush is running 100% smoothly […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/posts\/633"}],"collection":[{"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/comments?post=633"}],"version-history":[{"count":0,"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/posts\/633\/revisions"}],"wp:attachment":[{"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/media?parent=633"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/categories?post=633"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/montaraventures.com\/blog\/wp-json\/wp\/v2\/tags?post=633"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}