Scrobble when direct Last.fm access is unavailable

The setting Use Cloud relay for scrobbles when direct delivery is unavailable means exactly that: YM Bridge still tries the Last.fm API from Chrome first. The relay is contacted for scrobble delivery only after a direct network failure that qualifies for fallback.

When direct access is healthy, the panel shows Delivery target: direct to Last.fm and the relay is not used for those scrobbles.

1. Open Extension settings and find Cloud relay.
2. Turn on Use Cloud relay for scrobbles when direct delivery is unavailable.
3. On first use, read the data-use notice and press Accept and keep relay fallback. Until that review is accepted, fallback delivery does not start.

You can turn the option off at any time to require direct delivery only.

Only when direct delivery is unavailable, completed track metadata and the Last.fm session key are sent over HTTPS to the developer-operated Cloudflare Worker and forwarded to Last.fm.

The relay does not intentionally persist listening history, session keys or request bodies. Cloudflare may process the IP address and technical request metadata as the infrastructure provider. The complete disclosure is in the Privacy Policy.

Fallback scrobbles are queued and normally sent as a batch after 10 tracks or 30 minutes. This reduces traffic through the Worker. The panel labels these items as Relay and keeps them visible in the scrobble queue.

YM Bridge periodically checks direct Last.fm availability. New delivery returns to the direct path automatically when access recovers, without requiring you to clear the relay setting.

• Open the side panel and read Delivery target.
• Open View queue to see Relay, Retry or Failed states.
• If a batch remains after it is due, press Retry once and inspect the updated error.
• A connected Last.fm label confirms the saved session. It does not by itself prove that the direct Last.fm API is reachable from the current network.