[Discussion] Direction of the project

[Kernald]

Hi! This is more of a discussion with a few questions than an issue, apologies if this isn't welcome. For a bit of background, I just started writing a tool to download generated playlists from ListenBrainz - kind of the reverse of this tool.

First and foremost, do you have any thoughts around expanding the scope of this tool as a broader ListenBrainz utilities kind of tool? I.e. should I redirect my efforts towards contributing to this project rather than writing my own. If yes, what kind of scope would you be happy with?

Second, and more out of curiosity - is there any reason you didn't use the listenbrainz-rs crate? I know that not all of the endpoints are implemented there, but the maintainers seem happy to accept PRs adding new endpoints (e.g. https://github.com/InputUsername/listenbrainz-rs/pull/19).

[Serene-Arc]

Hi! I'm more than happy to expand the tool (even if that means changing the name) and I'm very happy if you'd like to make a lot of contributions to this project.

As for the other crate, part of it was that I wanted to make this tool fairly quickly. Literally none of the endpoints used in this project are actually implemented in that crate, at least according to their docs. I did look at it, and I did use the musicbrainz crate for some stuff, but the listenbrainz-rs would have required me to write most of the code anyway. They've only done listening API endpoints, which is fine and useful, just not for this tool.

[RustyNova016]

Sorry for hijaking this too, but I am also in the process of making a cli listenbrainz tool app, along side a higher level Musicbrainz + Listenbrainz library. So, if it ever expends out, I won't mind contributing to it.

[Serene-Arc]

I'd love to expand it!