Closed JanPokorny closed 7 years ago
Currently, web version (this repo) doesn't use pagination, it only shows the first page. Count of songs returned by each page varies in 10-20, I think. Filtering out them in UI will reduce result count very much.
My choices now:
Imho, 3rd option sounds better.
What do you think?
I think that the 3rd option sounds reasonable, but the sorting should be done on the client (this way, you can have a checkbox to instantly enable/disable sorting). And I have a UI suggestion: Putting a horizontal line between the non-matching and matching results, so they are visually divided. One downside is that when the pagination is implemented, it would be hard to come up with non-confusing UI (so users understand that new songs will appear in the upper section).
Why not just make it always sorted? There will be no need for visual separation. Usually, users need original songs. If the query matches the regex, disable sorting.
That makes sense, I like it.
@JanPokorny This feature is live now at https://datmusic.xyz.
https://datmusic.xyz/?q=Mumford https://datmusic.xyz/?q=Mumford%20Cover
Hi, I once wrote a VK.com downloader too, but it broke down after the API change. Yours is better, anyway. But there is one feature I had that is missing here: automatic filtering of remixes. VK.com is cluttered with remixed versions of songs, and it is sometimes almost impossible to find the original one. My solution was using this regex (it's huge, I know, it had gained weight over time..):
If you could implement the functionality as an option, it would be awesome.