Discussion: players.fullinfo Relationship Bug?

The setup: I am Accompli's contact, but Accompli is not my contact.

With these params:
player_tsid=PHVHMS5GPOA2AD2 (Accompli)
viewer_tsid=PIF6RN35T3D1DT2 (Ping=Me)

players.fullinfo returns:

"relationship": {
    "is_me": false,
    "is_contact": true,
    "is_rev_contact": false,
    "can_contact": true
}

It could be a matter of me misunderstanding the terminology, but if I'm the viewer, shouldn't relationship.is_contact be false when getting the info for Accomplis? Similar for is_rev_contact.

The problem is at least consistent.

With these params:
player_tsid=PIF6RN35T3D1DT2 (Ping=Me)
viewer_tsid=PHVHMS5GPOA2AD2 (Accompli)

"relationship": {
    "is_me": false,
    "is_contact": false,
    "is_rev_contact": true,
    "can_contact": true
}
I think it's vague terminology... if you add "viewer_" to the start of each variable, you get

"relationship": {
    "viewer_is_me": false,
    "viewer_is_contact": true,
    "viewer_is_rev_contact": false,
    "viewer_can_contact": true
}

Admittedly, the "viewer_is_rev_contact" doesn't really make sense, either way. Personally, this is why I have variable names long enough to accurately describe themselves... and to hell with the RSI!
The thing is, viewer_tsid is an optional parameter. It doesn't really make sense then to append viewer_ to the variables.
I'm saying that if you assume there's an implied "viewer_" that they didn't bother to add, it reads better. Mostly. And explains your disconnect.

The viewer_tsid doesn't designate which direction the relationship variables are intended to point... just defines one side of the relationship. I'm not sure why the relationship key is returned without the viewer_tsid, honestly... without viewer_tsid or a authentication that the method doesn't require, those values are always going to be false.
Actually, I can't get the relationship key to return any useful info without viewer_tsid, period. It occurred to me that if you sent it with identity authentication, it might default to viewer_tsid=your_tsid, which would make sense (to me). It does not appear to.
@Wounder, I get what you're saying. Either way, it will be best if one of the devs can clarify this for everyone.