I gotta give props to my buddy John Reese on his decision to shut down BlogRush.

You can get all the details at:

http://www.income.com/blog/2008/10/29/the-death-of-blogrush/

Pardon my crudeness, but it takes balls to risk your own cash and pursue a big project like this.

That being said, it takes MUCH, MUCH bigger balls to make the hard decision to cut your losses and move on.

Only a Grade-A, Status Quo Coward would chastise John or relish in the “failure” of BlogRush, so be on the lookout for “haters” and tell them Ryan Deiss said they’re a “coward”.

Seriously…tell them that.

I’m soooooooo glad someone finally said this:

CLICK HERE to read the “Pansy Report”…

I’ve said it before and I’ll say it again…NOTHING ticks me off more than marketers who get offended by marketing.

And as someone who’s been accused of “aggressive marketing” in the past (as if that’s a bad thing) I’m glad someone finally had the GUTS to stand up and say what the rest of  us have been thinking:

Check it out:

http://www.PansyReport.com

NOTE: I realize this post will irritate some folks. Just remember…we’re all marketers here and as long as you disclose what you’re doing there’s NOTHING unethical about the methods this report talks about.

If you thought membership sites were difficult or complicated to build, this video will prove otherwise…

To say we ran into some “technical difficulties” during the Continuity Blueprint launch would be an understatement…

Here’s a video that describes how we turned a “marketing lemon” into lemonade.

NOTE: Listen for the big announcement at the end of the video…

CLICK HERE To Learn More About Continuity Blueprint…

Despite our best efforts to warn our hosting companies about this launch and our insistence that we get the maximum amount of bandwidth allowable, we still managed to crash not one but TWO SERVERS.

MediaTemple is working to restore our main server, and RackSpace is working to restore our billing server.

We apologize for the inconvenience.

We thought we had covered all our bases by splitting resources and maxing out bandwidth, but apparently we were wrong. Please know we’re doing everything we possibly can to restore service.

Thanks for your patience and understanding,
Ryan

← Previous PageNext Page →