15:25:25 <m-relay> <s​gp_:monero.social> rando: do you have a summary overview for lionlink? I've been mostly out of the loop for that. I can pitch the story as an idea to the privacy guides journalists
16:29:02 <plowsof> sgp_ https://b10c.me/observations/06-linkinglion/ and https://b10c.me/blog/013-one-year-update-on-linkinglion/ 
17:39:56 <m-relay> <o​frnxmr:xmr.mx> https://b10c.me/observations/05-inbound-connection-flooder-down/
18:00:31 <m-relay> <b​asses:matrix.org> cool thanks, the links shared by plowsof and ofrnxmr should suffice.
18:17:47 <m-relay> <s​gp_:monero.social> Alternatively, one or several of you want to take a stab at a research piece to be published there, I could help coordinate that. The cryptocurrency expertise at privacy guides is relatively light, so they may appreciate a starting off point. lmk if any of you want to attempt that
19:38:02 <m-relay> <o​frnxmr:xmr.mx> sgp_  those nodes were also in the chainalysis video (not mentioned)
19:38:46 <m-relay> <o​frnxmr:xmr.mx> Their purpose or impact isnt known. This was, iirc, the first sighting of them https://b10c.me/observations/05-inbound-connection-flooder-down/
19:40:06 <m-relay> <o​frnxmr:xmr.mx> they monitor bitcoin traffic, so its not to defeat dandelion. Ive noticed them for years as they were always present on a new node sync, and used ports like 18380 18480 18580 etc
19:41:10 <m-relay> <o​frnxmr:xmr.mx> Probably more like dragnet surveillance. Collecting data on tor, i2p, bitcoin, and monero, to one day come back and try to decipher
19:41:47 <m-relay> <o​frnxmr:xmr.mx> one of our old sponsors, forked.net, leases them their IPs
19:45:10 <m-relay> <o​frnxmr:xmr.mx> iirc they dont make outgoing connections, so i dont know how they determine who has incoming connections enabled (if they were trying to defeat dandelion)
19:47:50 <m-relay> <o​frnxmr:xmr.mx> All seems rather passive to me, especially since its been running for like 7yrs