Author of memreserver (one of the mentioned userspace workarounds) here. I've debugged this a few years back, only public comment I can quickly find is [1]. I also remember some mailing list discussions, but it basically came down to the isuse that Linux didn't have staggered suspend hooks that reliably ran before disks and parts of the memory subsystem were frozen. Apparently this is now possible. Sadly the Freedesktop Gitlab doesn't seem indexable so this knowledge seems to have gotten lost.
It downloads and continually updates from the upstream database while serving the identical API. On a fast link it can download the entire thing in a few hours.
It just uses a giant BoltDB file to store compressed chunks.
It asynchronously pushes all info so that you can view everything as soon as the server gets it. It keeps the connections open because new requests also use WebSockets.
Author here, it's actually only JSdeliver and Google (analytics.dolansoft.org is mine). I wrote the tool a long time ago (like 2 years), there is a new version available internally which minifies all resources into static files delivered from my own server.
Author here, I only include a static map, no JS from Google. But I'll look into it, I'm also not a huge fan of Google being able to log all visits.
Abuse mails get parsed from the RIR WHOIS data, this involves lots of regexes, which can be wrong sometimes. In your specific case it is the fact that it can't yet parse the remarks statement.
[1] https://gitlab.freedesktop.org/drm/amd/-/issues/2125#note_17...