-
selstahyc: are you aware if Windows filesystem compression and lmdb cause issues? If yes, could code to detect this be added to lmdb directly or should it be added to monerod?
-
selsta
-
selsta.merge+ 9593 9592 9590 9589 9585 9584 9583 9581 9580 9565 9560 9556 9554 9549 9548 9543 9542 9541 9540 9537 9536 9535 9533 9532 9531 9530 9529 9527 9525 9518 9515 9512 9511 9510 9507 9506 9505 9504 9502 9501 9490 9481 9475
-
xmr-prAdded
-
sech1wow, that's a lot of merges. v0.18.3.5 soon?
-
jberman.merge+ 9380
-
jbermancan we get that one added too
-
jbermanoh it's already in^^ nice nevermind
-
jbermancan I get a follow-up review on 9381 also, I just removed the RPC version conflict (ping @xFFFC0000)
-
rbrunnerWhile reviewing 9381 I saw, more or less by chance, a reference to `m_rpc_payment` in (unmodified-by-your-PR) code - I thought all RPC payment stuff is gone longtime already in master?
-
m-relay<jeffro256:monero.social> It wasn't removed on the daemon side, just the wallet side
-
m-relay<jeffro256:monero.social> I'm open to removing it from the daemon side, but others weren't, so it stayed in
-
rbrunnerOk, thanks, that clears it up.
-
ofrnxmrI think we should revive primo, so i also think we should not remove from daemon
-
m-relay<0xfffc:monero.social> jberman: Approved.
-
m-relay<jeffro256:monero.social> I think it makes way more sense to pay by time or pay by bandwidth instead of the insanely fine-grained relatively-arbitrary cost per value in request
-
m-relay<jeffro256:monero.social> Both of the former payment methods could be implemented in a reverse proxy outside of the core codebase
-
jbermanty
-
jberman.merge+ 9381
-
ofrnxmr.merges
-
xmr-pr8929 9336 9380 9475 9481 9490 9501 9502 9504 9505 9506 9507 9510 9511 9512 9515 9518 9525 9527 9529 9530 9531 9532 9533 9535 9536 9537 9540 9541 9542 9543 9548 9549 9554 9556 9560 9565 9580 9581 9583 9584 9585 9589 9590 9592 9593
-
ofrnxmrJeffro, primo is for pay for other services, like ddos protection