02:14:44 <n1oc> [CCS Proposals] hinto closed merge request #539: Draft: Cuprate 2024 report + roadmap for 2025 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/539
02:15:04 <m-relay> <s​yntheticbird:monero.social> what
02:15:06 <m-relay> <s​yntheticbird:monero.social> is n1oc a bot ?
02:23:31 <m-relay> <o​frnxmr:xmr.mx> Yes
02:24:07 <m-relay> <s​yntheticbird:monero.social> Are we a bot?
02:26:10 <nioc> n1oc was cleaved from me
02:26:28 <m-relay> <s​yntheticbird:monero.social> Tron moment
02:27:38 <nioc> enabled me to increase my shitpost ratio 
02:28:31 <m-relay> <s​yntheticbird:monero.social> epic
12:53:49 <m-relay> <a​remor:matrix.org> Care to share the repo?
12:56:09 <m-relay> <o​frnxmr:xmr.mx> He cant see your reply
13:09:31 <m-relay> <a​remor:matrix.org> He’s offline?
13:13:26 <m-relay> <o​frnxmr:xmr.mx> Irc doesnt see "replies"
13:17:31 <m-relay> <a​remor:matrix.org> Elucidator can you share the repo?
13:25:32 <m-relay> <s​yntheticbird:monero.social> aremor there are no repo yet
14:37:37 <elucidator> @aremor it's not on a non personal repo yet. I'll post as a paste when I'm on my PC 
14:38:04 <elucidator> It's for older simplex daemon tho.
14:41:01 <m-relay> <a​remor:matrix.org> Thanks! Elucidator
17:54:32 <m-relay> <f​iatdemise:matrix.org> Wanted to give heads up that I won't be available to attend next meeting. Rare for me to be available on weekends, always have family stuff. I agree with what was discussed last meeting (tipxmr funds for retro part, prospective for expanded scope). And we will replace the integrated addresses with subaddresses.
17:54:55 <m-relay> <f​iatdemise:matrix.org> Also, XMRChat has integrated Trocador for swapping from LTC and BTC to XMR. More info on that here, https://x.com/xmr_chat/status/1877339542899834967.
19:00:05 <revuoxmr> Revuo Monero Issue 224: January 12 - 23, 2025. https://www.revuo-xmr.com/weekly/issue-224/
21:46:02 <m-relay> <s​yntheticbird:monero.social> In the light of recent presidential election, I propose we deploy our very own social network focused entirely on Monero, by monero people for monero people. The app will be written in Dart/Flutter. The first milestone of 75 XMR will be the foundation trust me guys I'm an advanced developer and know what im doing.
21:53:30 <m-relay> <o​frnxmr:xmr.mx> But are you a full-stack dev, with experience in blockchain and web3:
21:53:38 <m-relay> <s​nowman:tetaneutral.net> You could use the wownero network for messaging
21:54:03 <m-relay> <s​nowman:tetaneutral.net> Surprised someone hasn’t done that yet
21:54:29 <m-relay> <s​nowman:tetaneutral.net> The wownero block chain should be at least 100x the size of Monero
21:56:53 <m-relay> <o​frnxmr:xmr.mx> Or not
21:57:05 <m-relay> <o​frnxmr:xmr.mx> LOL
21:58:48 <m-relay> <3​21bob321:monero.social> Bsv style
21:59:45 <m-relay> <o​frnxmr:xmr.mx> Use dero or xelis for messages
21:59:48 <m-relay> <o​frnxmr:xmr.mx> Actually, maybe even particl's smsg
22:01:30 <m-relay> <o​hchase:envs.net> Actual idea I had today, would be nice if there was a simple script or some easy application to run that you could run against your own monerod public node to detect any simple misconfigurations or security concerns
22:06:30 <m-relay> <o​hchase:envs.net> I wouldn't be suprised there is someone by accidentally having an open wallet rpc available when they just want a daemon node
22:08:44 <m-relay> <o​frnxmr:xmr.mx> There are these scripts ezistong
22:08:46 <m-relay> <o​frnxmr:xmr.mx> How do you think i solomine on ppl's unrestricted rpc ports
22:11:41 <m-relay> <o​hchase:envs.net> also relevant would be interesting to expand rpcs to have contact information similar to tor nodes, so you don't have to figure out from online or just word of mouth the same person is hosting multiple nodes
22:12:15 <m-relay> <o​hchase:envs.net> especially to alert operators if they have a vulnerability
22:15:03 <m-relay> <o​hchase:envs.net> wouldn't have to depend on domain names and could just have straight identity keys you trust
22:15:41 <m-relay> <o​hchase:envs.net> unless im being stupid and this already is possible?
22:30:14 <m-relay> <o​frnxmr:xmr.mx> Why?
22:30:23 <m-relay> <o​frnxmr:xmr.mx> Stop using random nodes
22:30:47 <m-relay> <s​yntheticbird:monero.social> Why?
22:30:52 <m-relay> <s​yntheticbird:monero.social> Stop having 90GB free on your disk
22:31:05 <m-relay> <o​hchase:envs.net> do you host your own guard, and relays when you use tor?
22:31:14 <m-relay> <o​frnxmr:xmr.mx> I dont want anyone contacting me to confirm that they are using my node
22:31:16 <m-relay> <s​yntheticbird:monero.social> oh
22:31:18 <m-relay> <o​frnxmr:xmr.mx> If you didnt get it from the source, you shouldn't be using it
22:31:33 <m-relay> <s​yntheticbird:monero.social> i was assuming monero node
22:31:35 <m-relay> <s​yntheticbird:monero.social> not tor one
22:31:55 <m-relay> <s​yntheticbird:monero.social> tho I heard you can actually have your own private tor entry guard?
22:32:27 <m-relay> <o​frnxmr:xmr.mx> No, and i treat tor like a centralized system
22:32:29 <m-relay> <o​hchase:envs.net> i mean i haven't ever done it but im sure you can specify your own tor circuits, and always use a guard you own yourself
22:32:50 <m-relay> <o​frnxmr:xmr.mx> Since its very much "permissioned"
22:33:12 <m-relay> <s​yntheticbird:monero.social> YOU WILL EAT TRUST TORPROJECT AND BE HAPPY
22:33:15 <m-relay> <s​yntheticbird:monero.social> YOU WILL TRUST TORPROJECT AND BE HAPPY
22:33:37 <m-relay> <o​frnxmr:xmr.mx> I host my own i2p relay when i use i2p, and i host my own monero node(s)
22:33:41 <m-relay> <o​hchase:envs.net> I appreciate the ultimate privacy position and understand it, but there has to be a middle ground. You can't expect all users to run their own node
22:34:20 <m-relay> <o​frnxmr:xmr.mx> I also use nodes that a) i setup for other ppl or b) that were given to me by other ppl
22:34:35 <m-relay> <o​hchase:envs.net> Nor do all users have the privacy risk that warrants it being necessary to run their own node, hell its accepted to use a light weight wallet server
22:34:58 <m-relay> <o​hchase:envs.net> my first wallet was mymonero 🫨
22:35:23 <m-relay> <o​frnxmr:xmr.mx> I dont. I expect people to use nodes that are run by ppl they trust
22:35:30 <m-relay> <o​frnxmr:xmr.mx> Whether that trusted person us cake, stack, feather's trusted list, seth or someone they physically know
22:36:39 <m-relay> <o​hchase:envs.net> yes so if monero nodes had a contact mechanism, then I could search and see oh these ones are run by goodguy foundation; and then just keep goodguy foundation's identity stowed away as my go to for remote
22:36:52 <m-relay> <o​frnxmr:xmr.mx> a restricted rpc is that it is indistinguishable from others on the network
22:36:53 <m-relay> <o​frnxmr:xmr.mx> And you trusted their server with your view keys
22:37:30 <m-relay> <o​frnxmr:xmr.mx> Its not really an accepted practice. Its a convenience vs privacy tradeoff
22:37:33 <m-relay> <o​hchase:envs.net> Correct! Because, there is a lot of information to digest and people are falliable
22:38:10 <m-relay> <o​frnxmr:xmr.mx> You lose almost all privacy by using mymonero
22:38:26 <m-relay> <s​yntheticbird:monero.social> NOOOOOOO MYMONERO WILL DIE FOR ME
22:38:40 <m-relay> <o​hchase:envs.net> I know, thats why I said it was my first
22:38:41 <m-relay> <o​hchase:envs.net> but that was the first wallet that came up on search engines when I was just learning about the coin
22:39:13 <m-relay> <r​ucknium:monero.social> The closest thing is https://github.com/feather-wallet/feather-nodes
22:39:55 <m-relay> <o​hchase:envs.net> yep just saw that earlier this week, and was like huh and thats kinda like the tor contact mechanism
23:03:40 <m-relay> <3​21bob321:monero.social> Money transmitter spotted
23:05:35 <m-relay> <3​21bob321:monero.social> Or run your own node