Why is FB's "Use FB as a page" feature so completely UNRELIABLE???

3 replies
First it start quirking out on me by doing things like...

I'm using FB "as" a page -- all indications are that I truly AM using it as a certain page, then I click on a notification to check it out. FB informs me I must be logged in as my original/root/personal identity to view the notification -- so I do that (not sure WHY, makes no sense) -- then it SOMETIMES asks me to switch to using fb as that same page I WAS using before any way -- or SOMETIMES it will (only) let me look at the notification as my personal page --- this all makes no sense, of course.

If I am using fb as a certain page, then it should ALL behave that way, logically.

NOW it's doing something even more crazy!!...

When I use fb as a certain page, then try to post a pic on someone's wall (which I've successfully done dozens of times), now SOMETIMES it will behave properly/logically (properly saying the posted photo is posted by [the page I was using fb "as" while I was posting the photo)... but now, SOMETIMES fb will post the photo as if it was posted by my perosnla/root identity --- EVEN THOUGH, while I am posting the photo I can CLEARLY SEE that I am (at that moment) using fb "as" the "other" page (ie: NOT "me").

It seems to be very unstable + unreliabe as to whether I am TRULY using fb (TOTALLY) "as" a page, when I switch to doing so, using fb's own method for doing that.

Any ideas!?!?!!?

This is driving me nuts. FB works properly sometimes, and other times not! How can this be -- if it's programmed to do one thing, how can it ALTER its behavior seemingly on a whim, form moment to moment!?!!?

Please adivse!

Thanks!

-- TW
#completely #feature #unreliable #use fb as a page
  • Profile picture of the author TimothyW
    update -- just happened again!

    Ok, I "switched" to be using FB "AS" a page.
    Then I visited someone's page (a page who's wall I have posted on many time -- every time "AS" my alternate page).

    Then I (as usual) posted a photo on that page's wall. Went fine. Photo says that the page that posted the photo (credit) is the page I was using FB "as." Ok, so far so good.

    Then I post another photo -- NOT CHANGING ANY PARAMETER OR IDENTITY -- and THAT (2nd) photo suddenly, for NO REASON, says the page that posted the photo is *ME* (my personal/root page/identity)!!!

    This switch makes NO sense. Then to PROVE that I am indeed STILL using fb "as" the alternate page, in order to REMOVE the posted pic, I must first "switch" to my personal/root page/identity, in order to remove the pic!!!

    In other words, I start off as page-A (personal/root page), then I SWITCH to page-B,
    post a pic ("as" page-B) on anthoer person's wall --- fine.

    Then, STILL using fb "as" page-B (no changes!!!), I post a 2nd photo onto that same other person's wall, and SOMEHOW that 2nd photo gets "credited" as if it was posted by page-A (!!).

    Then, if I want to remove the pic, I must SWITCH to use fb as page-A (proving that I was indeed using fb "as" page-*B* when I posted the 2nd pic).

    Then I switch to using fb as page-A, then I remove the photo.

    Then I switch to using fb as page-B, then try to post the 2nd pic again.

    Sometimes that works, sometimes it doesn't. Seems to be completely random as to when it works properly, and when it doesn't!!

    Kew Kew!

    -- TW
    {{ DiscussionBoard.errors[5005875].message }}
    • Profile picture of the author rosetrees
      Why is FB's "Use FB as a page" feature so completely UNRELIABLE???
      Because it's Facebook. I hate FB- too complicated, too public and they are always changing things .
      {{ DiscussionBoard.errors[5005945].message }}
  • Profile picture of the author TimothyW
    I agree -- but this isn't about how they change things -- this is about how one thing that hasn't changed doesn't even behave logically from one moment to the next!!

    Unstable + unreliable. That makes no sense, even from just a programming point of view. Can fb really be THAT buggy?!!?
    {{ DiscussionBoard.errors[5006006].message }}

Trending Topics