08:02:18 <alanpoe>  [Global Notice] Hello. Due to ongoing services abuse, services account registrations have been temporarily suspended; the NickServ REGISTER command will not be available until further notice. Is this related to ccs.getmonero.org registrations?
08:03:00 <sech1> This is IRC registrations
08:03:19 <sech1> Libera chat announcement, not even Monero related
08:03:45 <alanpoe> Ok. Do you know where I can get help with a ccs.getmonero.org registration? thanks ...
08:04:20 <sech1> Did you read https://ccs.getmonero.org/how-to-ccs/ ?
08:05:30 <alanpoe> yes. I have a proposal ready to submit but I'm unable to cos I'm not registered on the EE Gitlab and the ccs.getmonero.org site for the reasons posted above (if you are able to see those (?)) ...
08:08:39 <alanpoe> how-to-ccs states: Quickstart Guide    Register for an account on Monero's Gitlab instance. Sounds straightforward, and usually is ... but it's simply not sending me a confirmation email ...
08:11:24 <alanpoe> i just tried again with a gmail address. no confirmation email ...
08:12:07 <alanpoe> they have not gone to spam
08:12:52 <sech1> I just checked logs, and gitlab registrations shouldn't be closed, but they were broken a few days ago. plowsof - you fixed it back then, can you check again?
08:13:08 <moneromooo> Google rejects emails from getmonero.org, it wants special DNS setup.
08:13:43 <moneromooo> If you give me your account name, I can allow it manually.
08:13:55 <alanpoe> do you know about tutanota, my other provider?
08:14:15 <moneromooo> I will look at logs if you PM me the email addresses used.
08:14:16 <alanpoe> freeross
08:16:38 <alanpoe> Ok, I sent PM
09:28:32 <plowsof> Thanks for ping sech1, and mooo for resolving. In these cases its moat helpful to just state the username for manual verification 
09:28:42 <plowsof> most*
16:11:58 <selsta> Boog900 posted a proposal on tx broadcast https://github.com/monero-project/monero/issues/9334
16:14:45 <sech1> huh
16:14:53 <sech1> p2pool uses similar method since forever
16:14:59 <sech1> Monero didn't use it?
16:16:07 <selsta> monero uses something similar for blocks but not transactions
16:16:17 <sech1> yeap, implemented it a year ago in p2pool https://github.com/SChernykh/p2pool/commit/d6cb0ee8a052f866d7f5e78eb8dab5cc77c02966 and it works great
16:17:10 <sech1> For blocks, Monero uses fluffy blocks, i.e. just block headers + transaction IDs, right?
16:17:16 <selsta> yes
16:19:28 <m-relay> <r​ucknium:monero.social> Is this related? https://github.com/Arch222/BAR_GOSSIP_FOR_DLTs
16:25:12 <m-relay> <r​ucknium:monero.social> By the way, my node data collection project records which peers are sending which transactions, and when. Probably you don't need mainnet empirical data to show that the current method is inefficient, but I have it if it could be useful.
16:28:52 <sech1> I left some comments there
16:29:14 <sech1> P2Pool uses a bit more conservative algorithm (it only eliminates duplicate broadcasts on the same connection)
16:29:21 <sech1> to keep the latency low
17:03:23 <m-relay> <b​oog900:monero.social> Thanks, I'll keep that in mind
17:03:35 <m-relay> <b​oog900:monero.social> I don't think so
23:23:08 <UkoeHB> Big PR (new threadpool + async tools): https://github.com/monero-project/monero/pull/9337. I expect this will take a while to review.