00:00:36 <m-relay> <o​frnxmr:xmr.mx> Pong
00:01:15 <m-relay> <o​frnxmr:xmr.mx> You dont need 18.0.0 to solve this issue
00:02:20 <m-relay> <d​ependency_inversion_principle:matrix.org> How to debug this issue then? Is there a well known approach to fix it or what should I do?
00:02:30 <m-relay> <o​frnxmr:xmr.mx> 1 sec
00:05:02 <m-relay> <o​frnxmr:xmr.mx> Come to Monero Support
05:31:45 <m-relay> <f​ineopal:nope.chat> Is there a rate limit on monero-wallet-rpc by default? After doing concurrent 100 get_transfer method calls, it gave me a 401 error.
05:31:54 <m-relay> <f​ineopal:nope.chat> Is there a rate limit on monero-wallet-rpc by default? After doing concurrent 100 get\_transfers method calls, it gave me a 401 error.
05:33:32 <m-relay> <f​ineopal:nope.chat> Is there a rate limit on monero-wallet-rpc by default? After doing concurrent 100+ get\_transfers method calls, it gave me a 401 error.
09:15:23 <plowsof> local or remote node. restricted or unrestricted. are you polling get_transfers instead of using --tx-notify <script> like every other payment processor? 
10:30:32 <sech1> tobtoht_ were you the one who worked on the bootstrappable builds? Can you TLDR on how the macOS builds work on Linux (i.e. where to get the SDK, what compiler to use). I'm trying to set up my own build scripts and just found out that it's not so easy for macOS builds.
10:31:32 <m-relay> <f​ineopal:nope.chat> remote node, unrestricted, not using --tx-notify
10:36:29 <plowsof> use --tx-notify 
10:37:29 <m-relay> <f​ineopal:nope.chat> How would I relay that information back to a program I am running?
10:38:13 <m-relay> <f​ineopal:nope.chat> Is there a hook for it?
10:38:18 <m-relay> <o​frnxmr:xmr.mx> Tx-notify will run a program or script
10:38:30 <plowsof> lmgtfy 
10:38:48 <m-relay> <f​ineopal:nope.chat> What?
10:39:18 <m-relay> <o​frnxmr:xmr.mx> "Let me google that for you" ^
10:39:50 <m-relay> <f​ineopal:nope.chat> DDG
10:40:15 <plowsof> https://docs.getmonero.org/interacting/monero-wallet-rpc-reference/#other-useful -> https://docs.getmonero.org/rpc-library/wallet-rpc/#get_transfer_by_txid
10:40:29 <m-relay> <o​frnxmr:xmr.mx> https://docs.getmonero.org/interacting/monero-wallet-rpc-reference/#other-useful
10:40:54 <m-relay> <f​ineopal:nope.chat> I would have to check the entire logic for the web server, can I not just call get_transfers without crashing?
10:43:37 <plowsof> of course , but as stated 9 days ago: https://libera.monerologs.net/monero-dev/20250620#c535689 
10:43:52 <m-relay> <o​frnxmr:xmr.mx> Why not use tx-notify + get_transfer_by_txid instead of dos-ing your wallet-rpc
10:44:15 <m-relay> <f​ineopal:nope.chat> Fine. I am stupid, thanks.
12:19:04 <m-relay> <t​ritonn:matrix.org> jeffro256: is the 30th the last day where they're accepted, or is the 29th the last where you can actually be added as collaborator?
12:44:44 <m-relay> <t​ritonn:matrix.org> I've hit the target, but now need to plan out how much cleanup I should let myself do
12:46:26 <m-relay> <o​frnxmr:xmr.mx> Rucknium @rbrunner7:monero.social
13:10:16 <m-relay> <j​effro256:monero.social> You must form your submission and notify us of it before Monday, June 30th at 17:00 UTC. If one of us isn't added as a collaborator by then, we by nature can't determine if you did that or not.
13:11:03 <m-relay> <t​ritonn:matrix.org> sounds good