03:26:20 <m-relay> <k​ayabanerve:matrix.org> After FCMP++, I believe there are arguments for JAMTIS. I'd more strongly advocate prioritizing a PQ migration scheme, which requires switch commitments in CARROT, confirming CARROT's compatibility, and a new wallet derivation scheme. There isn't anything pressing on-chain though, so flexibility is yielded to off-chain (wallet devs and research).
03:28:10 <m-relay> <k​ayabanerve:matrix.org> I myself may be interested in taking up the work I did for FCMP++, now for a PQ protocol, once Serai launches (or at least once my development contributions to it are ready for it to launch).
03:30:16 <m-relay> <k​ayabanerve:matrix.org> But that's honestly too far out for me to confirm anything on. I've just appreciated the new vitality the discussion has brought recently. I may be working on Serai another year or two straight though (without other projects).
17:15:17 <m-relay> <r​ucknium:monero.social> snowman: IMHO, the ban list should be enabled even if you are not running a public node, but just using your own node to broadcast transactions. The spy nodes could be trying to link your transactions with your home IP address (or the IP address your own node uses).
17:52:47 <m-relay> <s​yntheticbird:monero.social> Challenge: Find a single reason not to enable this ban list.
17:52:47 <m-relay> <s​yntheticbird:monero.social> Difficulty: Impossible
18:11:58 <m-relay> <s​nowman:tetaneutral.net> it could be used in a nefarious way if people are compromised.
18:12:38 <m-relay> <s​nowman:tetaneutral.net> Off topic though.  Move convo to Monero main.
18:35:11 <m-relay> <3​21bob321:monero.social> Look at banlist before you add or look at changes
18:35:24 <m-relay> <3​21bob321:monero.social> Like any dnsbl