v0.1.2: Securing the convenience
Pre-release
Pre-release
This is actually a quite small release that mostly just addresses some issues I've had during the times using lrcsnc v0.1.1 this couple of months. But this time I'm also updating the AUR version the same day this releases, so... I really hope to be better.
Added
- Ability to remove cached data for currently playing song by signaling USR2 at the lrcsnc process.
Changed
- LrcLib provider now only sends one
searchrequest instead of multiple tries ofgetandsearchwith different queries. Now, to get the best pick out of received data, there is an scoring algorithm inside lrcsnc itself that gives points for specific advantages (e.g. matching all artists or having exact duration match). Of course, that's not perfect, but it's actually better than LrcLib'sgetresults sometimes, and on par otherwise. - A fatal log should now allow a graceful shutdown to proceed (e.g. deleting the UNIX socket during shutdown if launched as server with UNIX specified as protocol).
- The default value for
cache.life-spanwas changed from 168 (hours, so 1 week) to 720 (hours, so 1 month).
Fixed
- The connection to LrcLib was insecure (using http) all this time (and I didn't notice T_T). That was changed (now it uses https properly).
- Fatal log was always duplicated due to a duplicated print inside the method.
- A proper error message for UNIX socket being busy during server's start-up that was introduced in v0.1.1 now works as intended.
Removed
- Japanese romanization was removed due to being inconsistent and difficult to implement properly. Until I find a way to do so (preferrably not depending on outside binaries like
kakasi), I will not try again. As such, the mention ofkakasirequired as optional dependency was removed as well.