[Feature Request]: OpenSubsonic support

Tolriq commented 1 year ago

Is your feature request related to a problem? Please describe.

You already more or less said no and ignored it, but this is an official request to be part of OpenSubsonic.

Describe the solution you'd like

Due to limitations in Subsonic API after months of effort a group of Subsonic servers and clients are trying to build an extension to the Subsonic API to fix some issues and add the missing features to have a complete and more modern API.

See: https://github.com/opensubsonic/open-subsonic-api and https://opensubsonic.netlify.app/

Any server and clients are free to join and contribute to this project.

tesshucom commented 1 year ago

If a better client app comes along in the future, it will be taken into consideration.

A number of similar attempts at APIs, both proprietary and open source, have emerged over the last few decades. There doesn't seem to be any distinguishing features compared to them.

As an engineer, I find it strange to recommend bulk imports more than necessary. (Caching is fine. Caching and bulk are completely different things.)　Sorting and searching running on the service is more advanced than the client app. Just because server evolution is slow doesn't mean such bulk imports features doesn't exist. It's just not made because it's not useful. (By the way, Jpsonic's UPnP is designed to be able to respond to Microsoft-style bulk requests in order to support WMP.... Although WMP's sorting and indexing is garbage for people in Japan, China, etc. )
Many of the challenges in much-requested areas are rooted in server design and implementation. It is questionable whether extending the API alone will drive innovation. So Jpsonic is a descendant of Subsonic, but it doesn't just stick to the REST protocol.
- In all honesty, even if we limit to the 1: vanilla Subsonic APIs and 2: UPnP , we can still cover a good portion of your needs. (Of course, including extensions that will be implemented in the future).
- For users, perhaps the next protocol will be 3: Chromecast. This is not a bad transmission standard either. Or maybe 4: New version of Sonos. Or maybe there are other candidates.
- Rather than supporting multiple APIs with similarity, It is useful to support multiple protocols with different viewpoints to accommodate many devices.

I think the community-driven approach is great. But without an expert, it seems impossible to create something flawless. So It's good that all extensions are announced as optional.

If a good client app comes along that's worth mentioning, it's possible that OpenSubsonic will be used to support it.
Of course you don't need full support in that case. All you have to do is unsupport the API methods you are concerned about.

I think we have to come to this view. For coexistence and co-prosperity.

Tolriq commented 1 year ago

As an engineer, I find it strange to recommend bulk imports more than necessary. (Caching is fine. Caching and bulk are completely different things.)　

Well again you still have not understood the need of some apps to be offline first .... Sync is necessary, to sync we need access to the full data, there's no API other that search3 for that in current API end of story. The fact that you do not see or understand the need does not make it not existing.

You are mixing access to the server data as a client and renderers protocols so I know you love to repeat that you are an engineer but you have no idea what I am and my experience nor the one of any of the participant of that project .... (But for the record I was first a system architect building complex infrastructure for large clients datacenters with dozens of Citrix/VMware and MS certifications, so maybe I know a thing or two about engineering)

Sorting and searching running on the service is more advanced than the client app.

This is also obviously wrong, Symfonium for example can sort by any field and support complex smart filters. So you can have a list of all your songs with a rating between 3 and 5, that have not been played in the last month and are from genre X or Y or Z and not by the artist Z or W. And even much more complex ones, limit is the imagination... Something that your own app can't do and that the Subsonic API can't do either... (https://support.symfonium.app/t/wiki-smart-filters/326)

But I get it you are an engineer, and you know better than me and the dozen other participant of that project. And the needs that you do not currently support are non existing. And yes 14 years of dealing with all major media centers APIs absolutely does not make me an expert. But I still may have some little useful knowledge ;)

If a good client app comes along that's worth mentioning

Thanks for free taunt ;)

So have a nice day, closing the request feel free to change your mind and find us.

tesshucom / jpsonic