Confirm
192
edits
Changes
→Presence
The project will be a success if an application registered with Mozilla Cloud Services is able to reach out to users that are "online" (active on their phone or desktop but with the app not running) via Mozilla Presence.
== Terminology ==
AppDeveloper - A developer that creates applications which may or may not have server-backed resources.
AppService - An Internet-accessible server that an application talks to. For example, Facebook's locally installed application talks to Facebook's API server to get data. The Facebook API server in that case is the AppService as it acts as a service to the application.
==Use Cases==
XXX See with Lloyd about the user story there (sumo experts summoned etc)
==FAQ==
To help people get up to speed faster and prevent backtracking, commonly asked questions by those getting involved are listed here with an answer.
=== Why not use XMPP? ===
XMPP provides some components that are similar to what Presence needs, however there's several parts that don't mesh well requiring either a rewrite or a fairly large layer on top. This is generally because XMPP uses a Federated globally unique ID system with domain prefixing. Due to privacy concerns, we don't want Presence to maintain a list of a users 'contacts', nor should any AppService see the same underlying user with and their FxA ID. That is why Mozilla Presence assigns a different UID for every AppService that a user allows to see their presence.
It is entirely possible though that we might implement the channel between Presence and AppServices using XMPP which would make it easier for alternate presence providers (ie, if Google decided Chrome should have Presence in a similar manner).
==Requirements==
* <i>List of requirements</i>
==Get Involved==
