05:20:25 <m-relay> <j​hendrix:imagisphe.re> You must be using some advanced methods. I've noticed IPs in your ban list that belong to Hetzner or DO, but Maldo Map only classifies spies in a simple way by checking if an IP pretends to be a unique peer too often. This is how I identified spies from Lionlink and Peg Tech Inc., but I haven't seen any other spies from any other ASN. There were very few false positives where an I<clipped message>
05:20:26 <m-relay> <j​hendrix:imagisphe.re> P address belonging to a VPN service was marked as a spy, but that's rare.
05:20:37 <m-relay> <j​hendrix:imagisphe.re> No.
10:24:31 <m-relay> <e​longated:matrix.org> Asn map would be nice to have in monerod
14:48:56 <moneromooo> Someone made a patch for this a while back. Maybe it did not get merged though.
14:49:11 <m-relay> <s​yntheticbird:monero.social> There is so much improvements PR that didn't get merged
15:07:08 <plowsof> https://github.com/monero-project/monero/pull/7935
15:12:35 <m-relay> <r​ucknium:monero.social> Probably what will be done instead of ASN Map in Monero is grouping of `/24` subnets. It would have a similar effect, but is less complicated. No need to trust the provider of ASN data, no packaging ASN data with the node, no need to update the data.
15:13:21 <m-relay> <o​frnxmr:xmr.mx> https://github.com/bitcoin/bitcoin/pull/18573