10:38:21 <m-relay> <s​yntheticbird:monero.social> Hello, maintainers/developers that are owner of a ProtonMail address, could you please look at your inbox and inspect if you have received a spam from an entity known as Euron. Assessing this would permit me to conclude if SimpleLogin has suffered a data breach. One plausible explanation is that they are specifically targeting cryptocurrency developers/contributors thus my questio<clipped message>
10:38:21 <m-relay> <s​yntheticbird:monero.social> n in this channel.
10:43:46 <m-relay> <d​etherminal:monero.social> yes, I got one too
10:44:15 <m-relay> <s​yntheticbird:monero.social> was it a public or private email address (private meaning you are sure it has never been disclosed publicly)
10:44:41 <m-relay> <d​etherminal:monero.social> probably public, I used it in lot of places
10:45:19 <m-relay> <s​yntheticbird:monero.social> i see thx. I've received one on a completely private email address
11:52:00 <m-relay> <s​needlewoods:monero.social> I got it too, not sure about all the places where I used that address though.
12:32:00 <m-relay> <a​dmin2025:matrix.org> у меня статический IP  193.105.41.254. Он у меня уже мнго лет. Больше 10. И я использую Tailscale. Что мне нужно сделать ?
12:34:10 <m-relay> <a​dmin2025:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/cKLQXijZIPeSZFTDHfCbbGiu
12:34:20 <m-relay> <a​dmin2025:matrix.org> вижу такую картину
13:23:29 <m-relay> <o​hchase:envs.net> I too got this email. Not sure what SimpleLogin is
13:23:46 <m-relay> <o​hchase:envs.net> I too got this email. Not sure what SimpleLogin is. My proton email is public on my github
13:25:26 <m-relay> <s​yntheticbird:monero.social> SimpleLogin is an email alias service that Proton owns. You can generate an incoming only mail to avoid giving your real address when signing up in services
13:26:20 <m-relay> <o​hchase:envs.net> Kk if relevant, I have never used the alias capability. My proton email is my "developer" email, and have my own personal email for personal things etc
13:27:13 <m-relay> <s​yntheticbird:monero.social> Could you tell when you received an email from their part?
13:30:55 <m-relay> <o​hchase:envs.net> Do you need an exact time frame or can i give you a +- 30 minute? Little confused on if I'm doxing myself
13:31:21 <m-relay> <s​yntheticbird:monero.social> nah you can just say the day+-2
13:32:37 <m-relay> <o​hchase:envs.net> Friday January 3th - Monday January 6th, 2025 , between 9am - 5pm Working Hours EST
13:33:10 <m-relay> <o​hchase:envs.net> its probably not rocket science to figure out my real identity anyways lol
13:33:51 <m-relay> <o​hchase:envs.net> Friday January 3th - Sunday January 5th, 2025 , between 9am - 5pm Working Hours EST
13:34:02 <m-relay> <s​yntheticbird:monero.social> thx that reassure me a bit ig. SimpleLogin may have no been data breached (at least ive come up with a plausible explanation)
13:34:39 <m-relay> <o​hchase:envs.net> I have also only actually contributed to Haveno as well and just general issues/stars of monero related public technologies
13:35:31 <m-relay> <s​yntheticbird:monero.social> I think they just collected emails of any monero (cryptocurrency) related project contributors and are sending spam regularly
13:35:58 <m-relay> <o​hchase:envs.net> thought i was a little special *feels bad*
16:18:45 <m-relay> <o​hchase:envs.net> https://github.com/monero-project/monero/issues/9696 "Thats a bold move cotton, Let's see if it pays off for him"  😅
16:20:12 <m-relay> <s​yntheticbird:monero.social> gonna make a comment
16:20:49 <m-relay> <s​yntheticbird:monero.social> dont be scared lol
16:21:07 <m-relay> <o​hchase:envs.net> But fr, I kept it on topic for solely technical. I stand firm gray is a terrible naming convention
16:22:02 <m-relay> <o​hchase:envs.net> not to mention the "gray" versus "grey" confusion, think the css community got screwed by this as well
16:38:01 <m-relay> <o​hchase:envs.net> Okay i see I failed to understand the peer list logic quite significantly here. Though perhaps too optimistically/vain, your commentary very validly dismisses my incorrect/uninformed suggested changes but does not seem to dismiss that the naming is in fact confusing. It just feels so off for there to be white and gray and then **banned**. As in there is definitely an odd one out i<clipped message>
16:38:03 <m-relay> <o​hchase:envs.net> f that makes sense
16:38:30 <m-relay> <s​yntheticbird:monero.social> for me it make sense in the white/black duality
16:39:01 <m-relay> <s​yntheticbird:monero.social> the white market is the legal market
16:39:03 <m-relay> <s​yntheticbird:monero.social> the black market is the illegal market
16:39:05 <m-relay> <s​yntheticbird:monero.social> the gray market is the one that touches both legal and illegal
16:39:18 <m-relay> <s​yntheticbird:monero.social> gray peers can be both valid and bannable
16:39:25 <m-relay> <s​yntheticbird:monero.social> gray peers can be both valid and ban-able
16:39:36 <m-relay> <s​yntheticbird:monero.social> schrodinger's cat
16:40:18 <m-relay> <s​yntheticbird:monero.social> you don't know the current state, you need to observe to assert. Thus between black and white there is only gray
16:44:48 <m-relay> <s​yntheticbird:monero.social> Regarding https://github.com/monero-project/monero/issues/9695, can i host a seed node
16:45:04 <m-relay> <s​yntheticbird:monero.social> guaranteed glowie you all know i'm a fed
16:46:46 <m-relay> <o​hchase:envs.net> Well if we could genuinely find high fidelity members to host seed dns nodes, this could have possibly alleviated the spy node issue quicker. If the dns seed node providers were active they would have been apprised to Boog
16:46:59 <m-relay> <o​hchase:envs.net> 's and others investigation and could have censored the bad nodes
16:48:45 <m-relay> <s​yntheticbird:monero.social> mhm per MRL policy regarding the ban recommendation I doubt about the willigness to allow seed node operators to ban nefarious nodes. That's interesting, i haven't realized it sooner but seed nodes definitely do have a place to play in this. Would require further discussion however. Recommending is something, hard coding a biased node is another.
16:49:15 <m-relay> <s​yntheticbird:monero.social> (i'm completely for seed nodes to ban nefarious nodes btw)
16:51:36 <m-relay> <r​ucknium:monero.social> AFAIK removing malicious IPs from seed nodes would have little effect on whether those malicious IPs are propagated to other peers. New nodes would quickly encounter other nodes that would give them a peer list with those malicious IPs.
16:52:44 <m-relay> <r​ucknium:monero.social> Node switch connections a lot. Most connections last less than an hour.
16:53:49 <m-relay> <s​yntheticbird:monero.social> I see
16:54:31 <m-relay> <o​hchase:envs.net> If i'm understanding correctly, not to be hyperbolic but we are in a pretty nasty situation until FCMP comes out with the Spy Node issue
16:54:47 <m-relay> <o​hchase:envs.net> because how many people really run their own nodes
16:54:58 <m-relay> <s​yntheticbird:monero.social> not really in a nasty situation
16:55:04 <m-relay> <s​yntheticbird:monero.social> wdym
16:55:33 <m-relay> <s​yntheticbird:monero.social> not a lot, majority are using public nodes, but afaik almost no one is directly using these spy nodes RPC
16:56:38 <m-relay> <o​hchase:envs.net> minimal cost to flood network with spy nodes and feed tainted ring members to weaken transaction ambiguity
16:57:48 <m-relay> <s​yntheticbird:monero.social> flooding network (aka every dandelion++ attack eg. blackhole) is indeed an issue but not nasty.
16:57:49 <m-relay> <s​yntheticbird:monero.social> as for ring members, it only happen if your wallet is connecting to a nefarious node RPC. other nodes do not influence that. It has been repeated a lot of time that you should only use node that you trust
16:58:00 <m-relay> <r​ucknium:monero.social> Spy nodes generally don't feed tainted ring members. There are checks in the wallet to detect if a spy node tries to feed an incorrect distribution. Wallets pick decoys
16:58:02 <m-relay> <s​yntheticbird:monero.social> these spy nodes have (for the most) no public dns record
16:58:06 <m-relay> <r​ucknium:monero.social> not nodes
16:58:08 <m-relay> <s​yntheticbird:monero.social> no users
17:05:05 <m-relay> <o​hchase:envs.net> damn advanced cryptocurrency making my brain hurt, why can't yall just give up on his fungibility and privacy stuff /s
17:05:27 <m-relay> <o​hchase:envs.net> damn advanced cryptocurrency making my brain hurt, why can't yall just give up on this fungibility and privacy stuff /s
17:52:26 <m-relay> <r​ajafan:xmr.se> hi guys, there are programmers here who write in phyton
17:59:47 <m-relay> <r​ajafan:xmr.se> ???
18:01:37 <m-relay> <o​hchase:envs.net> Can you expand on why you need a developer who can write in python, are you looking for someone to maintenance a python monero related project?
18:13:47 <m-relay> <r​ajafan:xmr.se> Yes
18:15:05 <m-relay> <o​hchase:envs.net> Not sure on rules here, but unless its an opensource public repository you probably can not solicit help here
18:16:45 <m-relay> <r​ajafan:xmr.se> Not sure on rules here, but unless its an opensource public repository you probably can not solicit help here
18:18:02 <m-relay> <s​yntheticbird:monero.social> ah, bro missed copy pasted into translator i think
18:31:37 <m-relay> <r​ajafan:xmr.se> I understand that, I'm all for open source
18:44:04 <m-relay> <o​hchase:envs.net> Okay feel free to link repository and issue that you need to bring attention to
18:45:22 <m-relay> <o​hchase:envs.net> Okay feel free to link repository and issue that you need to bring attention to; or message me i guess. I can develop in python and if the problem is minimal and not actually requiring monero code base work but communication with an active RPC I might be able to assist
19:24:44 <m-relay> <r​ajafan:xmr.se> guys who want to participate in the development of the ecosystem for Monero and in betotest, write
19:44:45 <CTRL_FAILURE> Good evening Devs, hope you're doing well.