Frequently Asked Questions

Simon Weber edited this page Nov 23, 2016 · 9 revisions

Here are answers to some common questions about the extension:

Syncing

When does syncing happen?

Syncing happens in the background whenever you have a Google Music tab open, even if you haven't clicked the page action recently. Playlist updates will be available in the web ui without refreshing the page. There's no need to have the extension tab open to sync.

Behind the scenes, sync is triggered whenever you update or create a playlist definition, as well as periodically. You can disable periodic syncing or sync less often through the settings menu, which can be helpful if you find syncing is slowing down the web interface.

What happens if I use the extension from more than one place?

If you're logged in to Chrome, your autoplaylist definitions will be synced across computers.

Try to avoid running multiple copies of the extension at once, though. This can cause autoplaylists to update slowly or incorrectly.

Can I sync while I'm away from my computer?

Yes, but you'll need to leave Chrome running and a tab open.

This limitation is on Google's end -- there's not currently a safe way for one of my servers to access your library.

Versions and Upgrading

What are the differences between the versions?

There are two versions:

  • free: limited to a single autoplaylist, but otherwise fully functional.
  • full: supports unlimited autoplaylists.

There's also a special version given to open source contributors that lets them toggle between the full and free version. This is partly practical (so they can test their changes), and partly a gift for their contribution.

How do I get the full version?

There are two steps:

What happens if I downgrade from the full version?

If you have more than one autoplaylist, all but the first will become "locked". Locked autoplaylists will not sync to Google Music and cannot be edited, but can be deleted if you choose. They can still be listened to on Google Music despite them not syncing.

If you choose to upgrade again, any locked autoplaylists will become unlocked and immediately begin syncing again.

Privacy and Security

What am I authorizing the extension to do when I install it?

The extension manifest will prompt you for access to:

  • your Google Play Music library, play.google.com/music and googleapis.com: to update playlists on your behalf.
  • your Chrome Extensions: to tell if you're a paying user.
  • your Google id and email: to group error reports by user. I will never use this for anything but grouping errors.
  • store data on your computer: to persist your playlist definitions and settings, as well as cache your library locally.
  • google-analytics.com: to report anonymous usage information. This is explained in detail below.
How do you access my Google Music library?

In two different ways:

  • through the Chrome Cross-Origin XMLHttpRequest extension api, which you are prompted to allow during installation. Your Google authorization cookies cannot be read by the extension; Chrome attaches them automatically.
  • through OAuth2, which you are prompted for when first running the extension.

Your library is only ever accessed by your own computers. On Google's end, it appears as though you are maintaining your autoplaylists manually.

Do you send any of my information to third parties?

Yes. Here's what's sent to whom:

  • when errors occur: your Google identity, the version of the extension, and details on the error are sent to Sentry.
  • when various app events (like syncing) occur: a non-identifying id and the version of the extension are sent to Google Analytics.

As required by the Google Analytics Policy, you may opt out of app event reporting by visiting chrome-extension://blbompphddfibggfmmfcgjjoadebinem/html/privacy.html after installation. I urge you to leave reporting enabled: it's very difficult for me to find and resolve bugs without it.