00:04:46 <bhxmr> plowsof & elibroftw: much friends, huh? smells a corrupted community already...
00:04:46 <bhxmr> keep dreaming with your juvenile hopes that it wasn't a malware issue and that a seed was bruteforced lmao. You M$Windows fanboys never learn.
00:05:09 <plowsof> bhxmr has left the channel 
00:06:20 <m-relay> <1​23bob123:matrix.org> Fifo people
00:09:05 <m-relay> <i​ntr:envs.net> this community never fails to weird me out
00:09:52 <m-relay> <p​lowsof:matrix.org> lol
01:12:11 <m-relay> <j​effro256:monero.social> @selsta did you see my recent DM? IRC bridge has had many changes so idk if you received it
01:12:28 <selsta> nope
01:12:44 <selsta> wait will message you from matrix
01:17:06 <selsta> messaged you from slstmd:monero.social
01:41:56 <m-relay> <t​rasherdk:monero.social> selsta: Hitting zmq-rpc on `v0.18.2.2-release` crashes zmq server.
01:56:21 <m-relay> <o​frnxmr:monero.social> Why ping plowsof instead of ofrnxmr #cowards
01:57:42 <m-relay> <o​frnxmr:monero.social> well then. Lets just go visit 18082 on every p2pool users ip
01:57:53 <m-relay> <o​frnxmr:monero.social> (Quick, go close yur ports)
01:58:30 <m-relay> <o​frnxmr:monero.social> PSA should go out to mining pools who use p2pool as a backend too, probably
01:59:09 <m-relay> <o​frnxmr:monero.social> What is 18082 used for? (as in. What uses it)
01:59:28 <m-relay> <o​frnxmr:monero.social> What relies on it*
02:05:24 <selsta> zmq
02:05:45 <m-relay> <p​lowsof:matrix.org> im testing simply looking at the url+port on my own node atm
02:13:42 <selsta> trasherdk: do you have --zmq-pub setup?
02:13:54 <selsta> I assume it's required for p2pool?
02:14:15 <plowsof> yes (monero-lws uses it also)
02:25:27 <m-relay> <o​frnxmr:monero.social> I knowi zmq
02:25:37 <m-relay> <o​frnxmr:monero.social> I mean, any harm in blocking 18082?
02:25:48 <m-relay> <o​frnxmr:monero.social> Prior to p2pool i would run with --no-zmq
02:27:35 <plowsof> still zmq activity after my simple test, must require something else
02:44:51 <selsta> trasherdk or someone else who can reproduce the issue, please open a github issue
02:45:00 <selsta> with detailed steps to reproduce
02:59:48 <m-relay> <o​frnxmr:monero.social> Os? SNeedlewoods @sneedlewoods_xmr:matrix.org:
07:19:55 <m-relay> <t​rasherdk:monero.social> I think selsta is on the wrong side of the bridge: monerod config for stagenet
07:19:56 <m-relay> <t​rasherdk:monero.social> ```
07:19:56 <m-relay> <t​rasherdk:monero.social> p2p-bind-ip=<listen ip address>
07:19:57 <m-relay> <t​rasherdk:monero.social> public-node=true
07:19:57 <m-relay> <t​rasherdk:monero.social> confirm-external-bind=true
07:19:58 <m-relay> <t​rasherdk:monero.social> out-peers=24
07:19:58 <m-relay> <t​rasherdk:monero.social> in-peers=24
07:19:59 <m-relay> <t​rasherdk:monero.social> limit-rate=4096
07:19:59 <m-relay> <t​rasherdk:monero.social> no-igd=true
07:20:00 <m-relay> <t​rasherdk:monero.social> data-dir=/var/lib/monero/data/stagenet
07:20:00 <m-relay> <t​rasherdk:monero.social> log-file=/var/lib/monero/data/stagenet/logs/monerod.log
07:20:01 <m-relay> <t​rasherdk:monero.social> rpc-access-control-origins=*
07:20:01 <m-relay> <t​rasherdk:monero.social> rpc-bind-ip=<listen ip address>
07:20:02 <m-relay> <t​rasherdk:monero.social> rpc-bind-port=38081
07:20:02 <m-relay> <t​rasherdk:monero.social> zmq-rpc-bind-ip=<listen ip address>
07:20:03 <m-relay> <t​rasherdk:monero.social> zmq-rpc-bind-port=38082
07:20:03 <m-relay> <t​rasherdk:monero.social> zmq-pub=tcp://<listen ip address>:38083
07:20:04 <m-relay> <t​rasherdk:monero.social> rpc-restricted-bind-ip=<listen ip address>
07:22:39 <m-relay> <t​rasherdk:monero.social> Only p2p 38080 and restricted 38084 ports are reachable by public. Other ports are firewalled to allow only my IP addresses.
07:23:36 <m-relay> <t​rasherdk:monero.social> Mainnet daemon have identical setup.
09:20:31 <StarF0x13> anyone recommend the BasicSwap DEX for atomic swaps?
09:20:58 <StarF0x13> now that XMR<->BTC for atomic swap, i really qwant to get into offering liquidity for that
13:25:52 <m-relay> <s​needlewoods_xmr:matrix.org> > Os? SNeedlewoods @sneedlewoods_xmr:matrix.org:
13:25:52 <m-relay> <s​needlewoods_xmr:matrix.org> Linux Mint
13:40:17 <m-relay> <o​frnxmr:monero.social> Which ubuntu lts base?
13:40:21 <m-relay> <o​frnxmr:monero.social> 22 or 20
13:41:57 <m-relay> <o​frnxmr:monero.social> And simple browsing to 127.0.0.1:18082 kills it?
13:45:13 <m-relay> <s​needlewoods_xmr:matrix.org> > Which ubuntu lts base?
13:45:13 <m-relay> <s​needlewoods_xmr:matrix.org> cat /etc/upstream-release/lsb-release
13:45:13 <m-relay> <s​needlewoods_xmr:matrix.org> DISTRIB_ID=Ubuntu
13:45:14 <m-relay> <s​needlewoods_xmr:matrix.org> DISTRIB_RELEASE=20.04
13:45:14 <m-relay> <s​needlewoods_xmr:matrix.org> DISTRIB_CODENAME=focal
13:45:15 <m-relay> <s​needlewoods_xmr:matrix.org> DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"
13:45:26 <m-relay> <s​needlewoods_xmr:matrix.org> > And simple browsing to 127.0.0.1:18082 kills it?
13:45:27 <m-relay> <s​needlewoods_xmr:matrix.org> yes
13:49:08 <m-relay> <o​frnxmr:monero.social> Hm. I tried that on my android node, and my zmq pub is still pushing updates to xmrig
13:52:54 <selsta> there must be something else going on, seems not everyone can reproduce it
15:15:04 <m-relay> <s​needlewoods_xmr:matrix.org> I've copied the get header that my browser generates into a python script and tested each line individually
15:15:04 <m-relay> <s​needlewoods_xmr:matrix.org> the following is the minimal script that reproduces the error
15:16:49 <m-relay> <s​needlewoods_xmr:matrix.org> '''import requests
15:16:49 <m-relay> <s​needlewoods_xmr:matrix.org> params = {}
15:16:50 <m-relay> <s​needlewoods_xmr:matrix.org> params["Accept"] = "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8"
15:16:50 <m-relay> <s​needlewoods_xmr:matrix.org> requests.get("http://127.0.0.1:18082/", params)
15:16:51 <m-relay> <s​needlewoods_xmr:matrix.org> '''
15:17:27 <m-relay> <s​needlewoods_xmr:matrix.org> okay, this is not how to make a code block 🙈
15:29:42 <selsta> paste.debian.net is best for sharing code
15:30:38 <m-relay> <s​needlewoods_xmr:matrix.org> thanks
17:17:40 <m-relay> <v​tnerd:monero.social> Ok, I can now reproduce the zmq bug, zmq-pub must be enabled for it to trigger
17:18:24 <m-relay> <p​lowsof:matrix.org> what services require this rpc over zmq?
17:19:31 <m-relay> <v​tnerd:monero.social> Lws uses zmq rpc
17:20:43 <m-relay> <s​packle_xmr:matrix.org> p2pool as well, yes?
17:20:48 <m-relay> <p​lowsof:matrix.org> usually this is not public facing, but glad you have reproduced it
17:21:08 <m-relay> <p​lowsof:matrix.org> p2pool uses zmq for something else? here is my confusion
17:23:03 <m-relay> <v​tnerd:monero.social> Theres zmq-rpc and zmq-pub. The latter is for pushing events (new blocks, new txpool, new mining block). Zmq-rpc is similar to http rpc, but in theory less overhead compared to http
17:23:33 <m-relay> <v​tnerd:monero.social> P2p pool uses zmq-pub, but I'm not certain about the rpc method used
17:23:51 <m-relay> <v​tnerd:monero.social> Lws uses both, although zmq-pub is optional
17:24:32 <m-relay> <p​lowsof:matrix.org> thanks for the explanation
17:27:55 <m-relay> <v​tnerd:monero.social> sech1: I think I found the source of zmq issues - on invalid data revents from poll returns true, but on inspection returns EAGAIN because there's no parseable message. I'll work on this asap
17:30:13 <m-relay> <v​tnerd:monero.social> When zmq-pub is disabled, it just does a blocking read which hides the bogus messages entirely
21:15:38 <rbrunner> Did you try a Google search for "Monero mixer" recently? The results will surprise you :) Seems nothing is stupid enough to not find victims.
21:18:04 <m-relay> <g​fdshygti53:monero.social> The algorithm recommend me the new Monero "Token" on ETH 🤡
21:22:30 <m-relay> <1​23bob123:matrix.org> used the G trigger word!