The reading-list engine will use FxA Auth for authentication, so needs to do whatever dances are necessary for this. Most of the core functionality has already landed in the FxA modules, but we still need to hook them up with the reading-list engine. At a minimum, this will involve: * fetching and storing the oauth token, and flagging an appropriate error state when necessary. * listening to the FxA notifications to notice when the user logs out or a different user logs in and act accordingly. * Putting together the necessary headers for the requests and noticing any error states.

You'll want to take a look at the bugs I linked to in See Also.

Mass change of ReadingList bugs, moving to their own component. Filter bugspam on the following quote: “Reading is to the mind what exercise is to the body.” ― Joseph Addison

This is fixed, while bug 1139743 remains as an improvement