I wonder how many more services will pop up in the future, it would be good to enable plugin developers to add services as desired, or perhaps even users if the API's URL format is exposed to a user preference. Currently, adding player services involves modifying the core see #1541

The API is the same as on the old one last.fm. the difference is that you need to enter the domain libre.fm http://turtle.libre.fm/, for this reason, in many applications, you can use the old plugin for last.fm, which went before when last.fm has changed its API.

This is interesting, do you know if these use the "RESTful" protocol standard? Perhaps it would provide more benefit to allow a custom URL text entry in the Preferences, rather than hard-coding the URL's.

This is interesting, do you know if these use the "RESTful" protocol standard? Perhaps it would provide more benefit to allow a custom URL text entry in the Preferences, rather than hard-coding the URL's.

you can see how this is done in the DeaDBeef last.fm scrobbler plugin

I wonder if it would be time to finally bite the bullet, break backward compatibility and move the whole now playing feature (and the other now playing-related plugins) to a single pre-installed plugin. A rather unfortunate decision was made to use a single config option for the username/api key/command in all now playing providers, which complicates future additions to the current system. I'd also like to avoid code for external network services in the core, and the feature feels like something that belongs in a plugin.