The Chrome Copresence API is made to empower developers who are part of the Chrome developer channel. The API can be implemented to communicate with nearby devices by using Google's co-presence service. Specifically, the API may be used to execute co-presence operations such as publishing or subscribing programmatically in batch amounts.
The following is a list of historical changes that were made to this asset. Typically,
once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change.
As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset,
we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all
activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb.
If you spot an error in our data and believe that a record needs to be updated in some way,
the ProgrammableWeb team would very much like to hear from you at email@example.com