Just in case some people here are not aware of the same discussion going on in the bug reports thread, Secret Squirrel already wrote there that he wasn't able to patch the problem and we have to wait for Blah to restart the service once he's back from is business trip: http://vgmdb.net/forums/showpost.php...postcount=1012

I'd like to use this cddb endpoint with XLD. It doesn't work! The reason it doesn't work is that XLD uses libcddb. libcddb makes a lot of assumptions that are not true when using VGMdb. Here are some of those assumptions, in the order I encountered them:

The category will be letters only

The category will be one of "data", "folk", "jazz", "misc", "rock", "country", blues", "newage", "reggae", "classical", "soundtrack", or "invalid". And maybe not "invalid".

The successful result of a "cddb read" command will include the disc revision number.

After fixing libcddb to not do these things, I was able to use it to query and read one CD from VGMdb.

Because the libcddb project seems dead and I don't want to be too much of a bother, I will be making a cddb server that returns libcddb-friendly results based on results found in VGMdb.

More recently, I fixed the underlying issue libcddb, the library used by XLD: https://github.com/sharpobject/libcddb. I have tried to get this merged into upstream libcddb but the project seems abandoned.

XLD is not abandoned, and the developer is very helpful, even when I ask stupid questions. Soon there should be an XLD release that incorporates this fix. So at that point maybe everyone will be able to download the new XLD and use vgmdb and I can avoid running a public proxy.