Beta 2026.0.4 (Beta 4)

Listening Post
1

New beta build is out, grab it from the Listening Post product page!

New & Exciting

  • ListenBrainz-compatible scrobblers — You can now scrobble to self-hosted ListenBrainz-compatible services like multi-scrobbler or Koito. Configure your server’s base URL, a display name, and your API token in the Channels settings. Full feature parity with the ListenBrainz channel: scrobbling, Now Playing, likes, and track enrichment.
  • Listening Post now captures and relays track duration (for new tracks). You’ll need to regenerate the CSV and JSONL exports to have them show up.

No Longer Broken

  • Channel menu entries (like “Post to Mastodon”) now appear immediately after authentication instead of requiring an app restart.
  • Mastodon / ActivityPub channel:
    • The server address field now submits when you press Enter.
    • Added a Cancel button to the Mastodon authentication flow.

:construction: The new channel for ListenBrainz-compatible scrobbling is in dire need for some real-life testing! So if you run a self-hosted scrobbler instance, I’d be delighted to hear back from you, good and/or bad! Just give it a spin, and should you run into issues, ping me via the “Contact the author” links in the app (About tab, main menu)—and ideally, send me a diagnostics report :victory_hand:t3:

1 Like
2

Testing Beta 2026.0.4 now and was able to successfully scrobble to Multi-Scrobbler using the Listenbrainz-compatible channel. The track is scrobbled correctly, with duration displayed when reaching its endpoint at Listenbrainz proper. Excellent!

While scrobbling is working as it should, I did notice these WARN messages in my Multi-Scrobbler log:

[2026-02-03 19:36:31.548 -0600] WARN   : [App] [API] [Ingress] [Listenbrainz] Received what looks like a Listenbrainz Endpoint request but it was to an invalid URL route: /1/user/Multi-Scrobbler/listens?count=5&min_ts=1770168768&max_ts=1770168772
Make sure base URL path to MS endpoint is correct.
[2026-02-03 19:35:29.835 -0600] WARN   : [App] [API] [Ingress] [Listenbrainz] Received what looks like a Listenbrainz Endpoint request but it was to an invalid URL route: /1/user/Multi-Scrobbler/listens?count=5&min_ts=1770168768&max_ts=1770168772
Make sure base URL path to MS endpoint is correct.
[2026-02-03 19:34:26.876 -0600] WARN   : [App] [API] [Ingress] [Listenbrainz] Received what looks like a Listenbrainz Endpoint request but it was to an invalid URL route: /1/user/Multi-Scrobbler/listens?max_ts=1770168772&min_ts=1770168768&count=5
Make sure base URL path to MS endpoint is correct.
[2026-02-03 19:33:41.816 -0600] WARN   : [App] [API] [Ingress] [Listenbrainz] Received what looks like a Listenbrainz Endpoint request but it was to an invalid URL route: /1/metadata/lookup/?recording_name=Victim%20Of%20Luck&artist_name=Metric
Make sure base URL path to MS endpoint is correct.
[2026-02-03 19:33:06.238 -0600] WARN   : [App] [API] [Ingress] [Listenbrainz] Received what looks like a Listenbrainz Endpoint request but it was to an invalid URL route: /1/metadata/lookup/?recording_name=Victim%20Of%20Luck&artist_name=Metric
Make sure base URL path to MS endpoint is correct.
[2026-02-03 19:32:55.365 -0600] WARN   : [App] [API] [Ingress] [Listenbrainz] Received what looks like a Listenbrainz Endpoint request but it was to an invalid URL route: /1/metadata/lookup/?artist_name=Metric&recording_name=Victim%20Of%20Luck
Make sure base URL path to MS endpoint is correct.
3

Thanks, @jacksaturn, I knew you’d jump on that right away :wink:

I kind of expected the URL warnings there—these are about fetching metadata from the server, and as I suspected, those endpoints don’t exist. I’ll update the implementation in beta 5.

1 Like