Nick Steel

Pretty sure there's already an option for this which is documented in the wiki but I'm also pretty sure it's broken and the code ignores the option.

The HTTP frontend seems to be sending empty responses: ``` DEBUG 2024-03-11 15:18:50,969 [10264:HttpServer] mopidy.http.handlers Received WebSocket message from 127.0.0.1: '{"method":"core.tracklist.set_consume","params":{"value":true},"jsonrpc":"2.0","id":24}' DEBUG 2024-03-11 15:18:50,969 [10264:HttpServer] mopidy.http.handlers Sent WebSocket message to...

> The HTTP frontend seems to be sending empty responses: > > ``` > DEBUG 2024-03-11 15:18:50,969 [10264:HttpServer] mopidy.http.handlers > Received WebSocket message from 127.0.0.1: '{"method":"core.tracklist.set_consume","params":{"value":true},"jsonrpc":"2.0","id":24}' > DEBUG 2024-03-11 15:18:50,969...

As discussed on Zulip, the JSON-RPC parameter decoding doesn't work for `dict` type parameters. e.g. * https://docs.mopidy.com/latest/api/core/#mopidy.core.TracklistController.filter * https://docs.mopidy.com/latest/api/core/#mopidy.core.LibraryController.search * https://docs.mopidy.com/latest/api/core/#mopidy.core.LibraryController.get_distinct For example, for `search`: ``` DEBUG 2024-03-13 23:50:37,464 [3220:HttpServer]...

First part sounds good. GstDiscoverer was previously found to be far slower. Is that no longer the case? It also did the wrong thing in some of the complicated cases,...

Don't Facebook accounts already work if you setup a device password ? https://www.spotify.com/us/account/set-device-password/

Recently (few weeks back) Spotify changed the format of some of their responses so that empty lists return 'null' instead of being actual empty lists like they are supposed to...

> Recently (few weeks back) Spotify changed the format of some of their responses so that empty lists return 'null' instead of being actual empty lists like they are supposed...

I don't believe you get any scrobbling by implementing Spotify Connect. ~I don't think you get it by implementing the reporting/event-service stuff either (see https://github.com/librespot-org/librespot/issues/913, https://github.com/librespot-org/librespot/discussions/626), I thought each client-side...

I can't reproduce this. I'm not 100% sure I am doing exactly the same, the above steps are a little vague. A debug log would be useful. I do see...