00:21:01 Hi all, plowsof: GitLab user apeir on repo.getmonero.org has been waiting for account approval since 10-12. It's for a CCS proposal for github.com/apeirs/xmrpool (a get_transaction_pool fallback for restricted nodes). Could an admin approve it when there's a moment? Thanks. 00:35:12 how is this a CCS worthy project? 00:37:41 this can be reverted in regular monero code, I disabled it because it had some downsides I don't fully remember right now and I asked around at the time and it seemed fine to disable 02:00:33 bwgh0 opened pull request #2730: downloads: add Monero One [beta] 02:00:34 > https://github.com/monero-project/monero-site/pull/2730 05:07:00 selsta: fair question, thanks. On its own xmrpool is a small client-side workaround (hashes + get_transactions in batches), so I agree it's thin for a CCS. If it's more useful upstream I'd rather do the monerod side: a restricted-safe get_transaction_pool (capped by count/bytes, or paged). Do you recall if the downside was response size / DoS? If 05:07:01 so a cap might cover it, and I'd open a PR instead of a proposal. 05:07:35 (cut off, the middle part:) I'd rather do the monerod side: a restricted-safe get_transaction_pool, capped by count/bytes or paged. Do you recall if the downside was response size / DoS? 16:31:10 Yes, the issue was that at large pool sizes the function is quite inefficient, and having it available for public RPC was risky. 16:31:27 inefficient in both RAM usage and response size. 21:15:33 Ap4sh opened issue #2731: versioned source update url redirects to a different release 21:15:34 > https://github.com/monero-project/monero-site/issues/2731