You know I'm going to keep nagging, er commenting. Like a buzzing mosquito ... When I'm miserable, here's what I try (a) go for a walk and cry (b) get something good to eat (c) have some hot tea (d) take a hot bath (e) write down horrible things about everyone who has hurt me and everyone I am angry with or (f) watch a favorite movie. Do as many on the list as I need to do, and then repeat.
But Facebook says: Warning: This Message Contains Blocked Content - Some content in this message has been reported as abusive by Facebook users.
I know, it must be the hot tea.
Seriously, I tried leaving out miserable and horrible and hurt me, and Facebook still blocked me. It won't give me a clue which words are the troublesome ones. Angry? cry?
Okay, I finally figured it out, from trial and error. It was nagging. Facebook considers the word nagging to be abusive.

10 comments:
I am not as surprised as I should be! Just the other day I too got the same warning!
Seems the title of my book is offensive.
I raised my eyebrow and shook my head. :)g
I wonder how they came up with that??? I would not have guessed that. And I've seen a lot worse than "nagging" on facebook. Or are you kidding? It's way early in the morning for me (can't sleep due to the chemo anti-nausea steroids!).
I'm not kidding! They even booted me off and changed my password for "suspicious activity" - but the email telling me that didn't arrive for several hours. Meanwhile I was frantically trying to get back on 'cause I was worried about my friend.
Cat, now I know what you mean about Facebook's "help" - when you try to report a problem with getting to your site, they ask for your URL. Who knows their Facebook URL?! I didn't know I had one! But that I did find by Googling myself and Facebook.
Guess you should have known better than call your book Killerbyte!
Teresa, hope this round of chemo goes well - as well as chemo can go!
Hey, Weronika - very cool that you are going to do an interview with a publishing house editor!
"Nagging?" Really? Ai.
I just ran across the same problem with a seemingly innocuous comment-post attempt, and am playing the same silly elimination game trying to figure out the source of the objection.
It would be *much* more helpful if the silly FaceBook message gave me some sort of hint as to what had triggered the "abusive" filter. :-/
Heh. I finally figured out the "abusive" portion of my blocked FaceBook comment post. After quite a number of eliminative test-posts, it appears that their filter was objecting to the inclusion of "shorter in" in my comment. I can only speculate as to why...
Why is it that I have the urg to go to my FaceBook page and write "nagging, nagging, nagging shorter in Killerbyte"
OH and I just found your blog and it is great fun reading it
I'm getting the same thing, trying to post a link to this article:
http://pictureyear.blogspot.com/2010/02/gender-bender.html
Which is a review of a scientific study. Is it 'gender' that's the problem? Mysterious... and frustrating.
I'm getting the same thing, trying to post a link to this article:
http://pictureyear.blogspot.com/2010/02/gender-bender.html
Which is a review of a scientific study. Is it 'gender' that's the problem? Mysterious... and frustrating.
I found the culprit in mine today - a tiny url link. You know, what you use to shorten a url so that it's not a million characters long. Apparently it didn't like seeing tiny & url together. I've used tinyurl in the past, but today - no dice. It worked when I used the bit.ly shortner instead.
Post a Comment