[Apology] Blocking by mistake

As of 1/6/2010, I modified the Blocking Policy, I added

"Failed installation/script removed blogs — Script installed without key or incomplete installation. Blogs have removed the script. (Added on 1/6/2010)"

At beginning of this year, many blogs have reach 3-month reviewing period. So, I started to review those blogs which haven't got accepted or blocked. I found out many of them are not using Key or installed the script incorrectly causing BRPS not working. I don't bother to notify the blogs owners, I don't have that free time to do so. Besides, the error message has been showing up for more than a month, how could a blogger not checking there own posts after publishing?

The second part of the addition, "Blogs have removed the script," it's also true that many blogs have removed the script after installing. I see no harm to block them since they don't use BRPS anymore, by blocking them so they won't show up after 3 month for reviewing.

But I made a huge mistake, because I check HTML source code in home page. If you install the script into your Template, not by adding a new HTML/JavaScript gadget, then the script wouldn't show up, they would only show up in a single post page.

I forgot that part, therefore I must have blocked some. By the time I found out, I had no idea how many had been blocked by that mistake.

So, if you install the code into your Template, just go ahead to ask for unblocking. I will check up as soon as possible. (I will still review first to check your content)

Sincere apology to you.
Sorry, again!

Blocking Policy

(Last updated on 1/6/2010)

BRPS is a free service, it uses free quota of what Google App Engine provided. It wasn't planned to charge, however the quota is limited and lots of blog using BRPS, therefore some blogs may not be using BRPS.

Any blog is having the following

• Copyright infringement (If your blogs have links to any illegal downloads, directly or indirectly, upload by youself or not, please DO NOT use BRPS. Otherwise, your blogs will be BLOCKED for sure),
• Hate against a protected group,
• Adult or pornographic images,
• Promotion of dangerous and illegal activity,
• Content facilitating phishing or account hijacking,
• Impersonated user identity, or
• Abuse this service.

will definitely be blocked.

There are more could be used as blocking reasons:

• Similar contents — There are few blogger (useless content creator) creating lots of blogs with very similar content in each of their blogs. Those contents are useless, the primary purpose is to expose their blogs and get revenues.
• Referral contents ­— Almost all posts have link to Amazon or some online stores with their referral code. Those blogs are just created to make money.
• Few posts — BRPS automatically block blogs only have less than 20 posts. There is no much benefit of using BRPS. Please don't waste server resources. If you got blocked, request a unblocking review once your blog post count reaches 20. (Added on 10/18/2009, updated on 11/17/2009)
  
• Test blog—If you are testing BRPS on your sandbox blog, that blog will be blocked. (Added on 10/18/2009)
• Failed installation/script removed blogs — Script installed without key or incomplete installation. Blogs have removed the script. (Added on 1/6/2010)

The reasons above are not the only ones, your blogs could be blocked for any reason.

If your blogs are blocked and you believe your blogs shouldn't be deserved for that, please report with your blog URL.

You can still host your own BRPS on Google App Engine, you can grab the code and run on your own. Please DO NOT ask for help about self hosting!

Special note to template developer: Please DO NOT activate BRPS if you add it into your template creations. Comment out the script! And write a instruction to guide your user to activate it.Not everyone needs Related Posts in their blog. (Added on 10/18/2009) (Removed on 1/6/2010)