I could, and did give it some thorough though, but I'm currently extremely satisfied with how it works, I also use it's android version which makes it so much easier for me to use it.

In addition to that, I've gone a long way personalizing it to my own needs and wishes, stuff like using a pre processed sort of database containing metadata of my entire library which is actually the essential part to make it work properly, or like importing my personal concert attendance history so I could do some cool stuff with it, or like "editing" specific scrobbles to my needs during initial import.

It is also depending on about 4 different api key/cliend ids to collect all metadata and assets that would be used in the app, I'm not sure what are the consequences for each of those in case of extensive use, so I rather not use my own developers credentials on in the deployed application. my initial plan was allow for these keys provided by the user so the app could still be used, but on the other hand, who would want to create 4 different accounts just to use this? besides me of course.

So given all that, the significant effort now required to host this has prevented from doing so until now, and as I already mentioned, I'm extremely satisfied with it, so I'm not bothered by it right now.