Updated documentation

README.md

@@ -5,9 +5,11 @@ It allows you to access your music using an http(s) web interface.
 
 ## Features
  - Audio transcode for maximum interoperability and low bandwith requirements
- - MusicBrainzID support to handle duplicated artist and release names
- - Filter by genre and/or group
  - User management
+ - Browse your audio collection using tag-based filters
+ - Custom tags scan
+ - MusicBrainzID support to handle duplicated artist and release names
+ - Reverse proxy support
 
 LMS is written entirely in C++. Therefore, it is suitable to run on embedded devices, where space and memory are limited.
 
@@ -28,7 +30,7 @@ mkdir build
 cd build
 ../configure --prefix=/usr --sysconfdir=/etc
 ```
-configure will complain if a mandatory library is missing.
+configure will report any missing library.
 
 ```sh
 make

TODO

@@ -7,11 +7,9 @@
 - Implement a cache to improve speed
 
 [Database]
-- Optim, use SQL query to get the "genre" orphans
 - Use Inotify like system to watch modified/added files?
 - handle access rights problems (instead of aborting)
 - add a global play counter for tracks. This will help people to spot most popular files
-- Make cluster scan configurable as it is very difficult to handle them all?
 - Use albumartist when available (useful for compilations)
 - Add AcousticBrainz support to create new kind of clusters
 
@@ -19,27 +17,23 @@
 - WMA covers: add support
 
 [Playlist]
+- Save/Load playlists
 - Make public playlists so that users can see what other people are listening to
 
 [Users]
 - Handle login lifetime?
 - Use the WServer::post method to kick users already logged in?
+- Or save the current playqueue by session (using a cookie)?
 - Limit multi login from UI and API interfaces (limit per interface is acceptable)
 
 [UI]
-	- Add a download button to get the current playqueue in a streamed zip file
-	- Save user prefs in local storage (volume, loop, shuffle, current playqueue, etc.)
-	- Add keyboard shortcuts
-	- Add a hint for the user to get the nature of tag (created from genre ? created from audio features?)
-	- Implement a play queue
-	- Implement a decent player
-	- Dedicate a color for each tag type
-	- Display only the most popular cluster of each cluster type?
+- Add a download button to get the current playqueue in a streamed zip file
+- Save user prefs in local storage (volume, loop, shuffle, current playqueue, etc.)
+- Add keyboard shortcuts
+- Implement a decent player
 
 [Settings]
-	- Add a user management view
-	- Add multi root directories support
-	- Add a first connection wizard
+- Add multi root directories support
 
 [REST API]
 - Make a dedicated REST API. Maybe use the SubSonic API or Ampache API?