[185.253.190.33:39980 INC] peer claims higher version that we think (60 for 2046932 instead of 12) - we may be forked from the network and a software upgrade may be needed "or maybe there is an asshole spamming the wrong version"

^ can we add that line. It's freaking me out

Sure.

Ah! That will show them

bogus, ted

Would it also be smart to only show this message once per IP address and not for once per IP:port combination?

Because the spammer started a lot of nodes on the same IP address but different ports

that's just the usual random-port-assignment for outbound sockets

ah that explains it :P

I’ve usually only seen the message once per IP address but last time there were a lot of messages with same IP and different ports so I thought that’s what they did.

supposedly we have a dev meeting right now

I hereby declare myself emperor of the dev channel. all opposed?

done. thanks for attending.

De nada.

meeting in about 20 minutes no?

Ahhh, those time zones ...

17:00 UTC

At least it once was, back in the old times, when there were still meetings :)

I see current time as 17:43 GMT, so no, it should've started 43 minutes ago

Yup.

In fact, I Imperially Decree that it should have started 43 minutes ago.

Palace revolution, eh?

oh god. Let's start the meeting. First point: abolition of time zones

Together with all that daylight savings nonsense, of course

that especially

Stupid sun

Anyway, aren;t we skipping too many dev meetings?

Anybody has anything they want to speak about?

let's have a quick one

how is the dandelion PR going? just waiting for more reviews? i see moneromooo already reviewed it a couple of weeks ago

I think it's just stuck in the PR backlog that we currently have, but not sure

or vtnerd around? maybe he has something to say about his supercop changes?

(look at me, pretending to know what i'm talking about)

Anyway, I have my testnet daemon running with that code, so Dandelion-ready. It's just feeling a little lonely, I think

i was thinking of running it on my mainnet node, but that wouldn't make any sense if i'm the only one doing it

about the backlog, do we only need snipa to merge things or there are other reasons?

should probably stick to testnet for now

Yeah

also if testnet is small enough that we know what all the nodes are, we should be able to see if txns propagate as expected

iirc there should be very few testnet nodes, but i haven't run one in some time. Shame on me

so what we actually need would be people running dandelion on testnet and see how things go. Maybe worth making a reddit post?

Why not

alright, i can make a post tomorrow, but if somebody want to do it earlier, be my guest.

is anybody else running a dandelion testnet node except rbrunner at the moment?

Just consider that it's not trivial to cherry-pick that PR and compile with it. Not magic, but not trivial.

yeah, i will add instructions in my reddit post

are you doing anything besides just running the PR as its own branch?

Not really, you are right, just could take vtnerd 's branch and compile that

yeah that would be the easier way, and afaik nothing else nothing major got merged in the meantime

fluffypony: if you are around any updates with the deployment of the onion service for getmonero?

Ah, please review website stuff when you have time: repo.getmonero.org/monero-project/monero-site/merge_requests

often my PR stay there unreviewed for weeks until a good soul (usually selsta and few others) review them

Quite a queue there, yes

all my open PR except the one marked WIP are ready to go, if people here have time, please review.

I am unsure about the best way to test dandelion. A quick first look at the code did not show me a way to log, with entries like "Dandelion tx received" or "Dandelion tx passed on". Maybe I overlooked.

In that case, should make that comment on the PR itself and that can be added

Yeah, why not. Will check again.

how big is the testnet blockchain? maybe i can squeeze it in my vps

I think somewhere between 2 and 3 gig

Mostly empty blocks

alright, i'll see how much space i have left, but i think i can make it. I would run it from my laptop but i am always on mobile roaming (monero nomad life)

so, maybe something came out from this meeting. Good. If anybody have something else to say, let's talk about it. Otherwise, with the permission of our emperor hyc, we can go back to whatever we were doing

You are all summarily dismissed

so enlightened

Thanks, your majesty

be sure to tip the palace guards on your way out

There is no dandelion tx. Dandelion is just you sending to one (or two) peer rather than N.

Wait, actually that can't be true. Otherwise a peer would not know whether to continue fluffing.

exactly

we should be able to monitor its progress from node to node on testnet

Posted a proposal to improve censorship-resistance for Monero on getmonero.org...looking for some feedback: repo.getmonero.org/monero-project/ccs-proposals/merge_requests/127

working with Locha Mesh to add their radio implementation into the Full Spectrum Radio sensor.