Accident or censorship? Spicy title gets blocked at Namebee

While we consciously try to use post titles that are short, effective and PG-13 there are times that certain words have to be used. πŸ˜‰

Hence the post about Rick Schwartz’s adult domains from earlier today; the title contained the word “porno“.

The post does not appear in the RSS feed timeline of Namebee – the domain news aggregator that gains popularity on the rare occasions that Domaining.com is slow or down.

However, on December 10th another post that contained the word “porn” made it without any problems.

An accident or selective censorship?


Copyright © 2024 DomainGang.com · All Rights Reserved.

Comments

6 Responses to “Accident or censorship? Spicy title gets blocked at Namebee”
  1. Randall says:

    -NameBee is kinda crappy in itelf. Ya it looks good but if you try to contact them and get your domain added to the feeds then you better just forget it. I have emailed them more then once and never received emails back to even acknowledge me.

  2. Lucius "Guns" Fabrice says:

    Randall – It’s no big deal. Actually, Namebee loads quite fast. I was just curious about the censoring logic behind “porno” versus “porn”.

  3. Andrew says:

    It is a bad word filter. It did not match β€œporn” or β€œporno” but the word β€œshit” instead. There are very few words in our blacklist whereby we don’t post articles, shit happens be one of those words. We did change so that an article with a bad word farther down will be pulled in – as long as the bad word is not showing up on NameBee.

  4. Lucius "Guns" Fabrice says:

    hi Andrew – thanks for the clarification, but does that mean that Namebee scans the entire article? The content you’re referring to was “pigeonshit” and it was not in the title. Either way, I’m glad it caught your eye πŸ˜‰ Namebee is good to have and it’s definitely fast and clean.

  5. Andrew says:

    Correct – prior to today it was scanning the entire article or as much of the article that is published in the RSS feed. We are now scanning just the title and top of the article – the part would be published on NameBee. This keyword is questionable for being in the blacklist, but overall we prefer keeping NameBee more professional and profanity clean.

  6. Lucius "Guns" Fabrice says:

    Andrew – Not a problem, glad to see that you keep Namebee sweet on the honey πŸ˜€ It’s the industry that makes use of the term a bit too often lately, that’s all.

Leave a Reply

Your email address will not be published. Required fields are marked *

 characters available