From c54189357209b56930d0e1fd6fe689fcdfb70974 Mon Sep 17 00:00:00 2001 From: mitteneer Date: Sat, 30 Nov 2024 23:59:59 -0500 Subject: [PATCH] Add to todo list --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4947ca5..68e41fd 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,11 @@ Licensed under MIT. - [ ] From Last.fm (authentication) - [ ] From Spotify (.json file) - [ ] From other streaming services[^4] + - [ ] Import rules + - [ ] Simple find/replace + - [ ] User-defined regex - [ ] Tags + - [ ] Genres - [ ] MusicBrainz integration - [ ] Concerts - [ ] Import from Setlist.fm[^5] @@ -36,7 +40,7 @@ Licensed under MIT. [^2]: I do not intend to provide the level of granularity that Discogs provides, but a simple toggle that means "I own some version of this release" is all that is necessary. -[^3]: I have not investigated any other service for downloading your listening history from Last.fm, but providing the listening history as a JSOn rather than a CSV is highly preferred. I may eventually provide my own way of downloading Last.fm data as a JSON, but I would prefer to allow users to enter their username, or authenticate, and avoid needing to upload a file altogether. +[^3]: I have not investigated any other service for downloading your listening history from Last.fm, but providing the listening history as a JSON rather than a CSV is highly preferred. I may eventually provide my own way of downloading Last.fm data as a JSON, but I would prefer to allow users to enter their username, or authenticate, and avoid needing to upload a file altogether. [^4]: I only intend to allow imports from Last.fm and Spotify at the moment because those are the only data sources I currently rely on. To that extent, I imagine I could import from other sources as well fairly easily, although I do not know what their data dumps look like.