On Apr 17, 2010, at 2:09 PM, Peter Hosey wrote:
>
>
> What I'm proposing is that we continue storing the user's settings for their
> Facebook account(s) the same way we have been doing, rather than storing them
> as an XMPP account would. Basically, store the user's settings according to
> the service the account uses, rather than according to the protocol the
> service uses. This removes the need to “migrate” the user's data from one
> settings format to another.
Doesn't that risk creating confusion for users helping out with
troubleshooting and/or new developers somewhere down the line...?
new developer: can you please tell me how the contact looks like in your
blist.xml file?
user: hhhmmm, this is strange, facebook is supposed to be an xmpp-type account,
but the contact entry doesn't look like such in my blist.xml file, it's
something entirely different...
new developer: that is certainly *is* strange, I don't have any idea why your
facebook contacts wouldn't look like regular xmpp ones...
(some wasted brain cycles later)
vintage developers: you remember eons ago when facebook chat wasn't xmpp
based...? well, that's what's going on here, that's why your contacts look
differently in your blis.xml file.
new developer & user: ooohhhh, right, figures! Now, if you guys had only
migrated *properly* upon the switch....
If my script writing abilities seem to stray ridiculously far from what
the reality could be sometime in the future, then it's because my knowledge of
the Adium/libpurple innards is obviously very small. But I'm just wondering if
something similar could indeed take place... I tend to give an admittedly
somewhat obsessive preponderance to consistency when I (re)organize stuff,
whatever, to precisely avoid problems of this sort down the line when
decision-making-memory starts to fade.
My two cents,...
- jmpp
