<3​21bob321:monero.social> Or plowsof can do exective order ?

Meta says April 12

Last meeting was last Saturday

thanks nioc, speaking of, BTCpayserver plugin proposal has a new comment repo.getmonero.org/monero-project/c…als/-/merge_requests/538#note_29400

<o​frnxmr:xmr.mx> I posted in their room

<p​lowsof:matrix.org> #btcpay-monero:matrix.org (hopefully history is viewable)

<o​frnxmr:xmr.mx> ```

<o​frnxmr:xmr.mx> i have np with lws support, but if the ccs dropped lws stuff, imo its essentially limited to my proposed m1 (below). Whether that is a good or bad thing, is uo for debate

<o​frnxmr:xmr.mx> - M1: Finish GUI for remote node configuration [started here](btcpayserver/btcpayserver #6239).. making sure to address [this comment](btcpayserver/btcpayserver #6239#issuecomment-2481847461)

<o​frnxmr:xmr.mx> - M2: multi-wallet support via LWS and/or wallet-rpc + adapt M1 and M2 for lws (probably 70% of the ccs). + "wallet setup interface (create*, import, export*, update*)" for lws

<o​frnxmr:xmr.mx> - M3: setup (new users) and migration (existing users) documentation

<o​frnxmr:xmr.mx> re m2. Might be a bad idea for spend keys to touch the server, so might should Not create wallets(rpc), and be import(view wallet) only.

<o​frnxmr:xmr.mx> i don't know where export-wallet would make sense? Or what update-wallet means(change wallet?)?

<o​frnxmr:xmr.mx> anyway, sounds like duplicate of "Onboarding redesign to support both wallet-rpc and lws"

<o​frnxmr:xmr.mx> ```

<o​frnxmr:xmr.mx> Basically, w/o lws, after clearing up their duplicated milestones, its essentially just "finish the pr that was opened a long time ago"

<o​frnxmr:xmr.mx> the milestones somewhat conflict with one another as well, since "simplify by allowing remote nodes" isnt exactly inline with running an lws server

<o​frnxmr:xmr.mx> "adding remote node support" isnt real, as it already exists

<o​frnxmr:xmr.mx> "create a repo org" .. is like saying "click 3 buttons"

<m​onerobull:matrix.org> Reddit will have whole ass subreddits with tens of thousands of people about it but when someone posts on r/monero about taking XMR for their weed, REMOVED BY REDDIT

<a​remor:matrix.org> The same site that will permanently shadow ban you for using Tor once

<a​remor:matrix.org> We have to find a better medium

<c​t:xmr.mx> shame that power tripping Lemmy Adkins block so much that federation is essentially worthless

<s​pirobel:kernal.eu> it would be best if only the identity was federated and not the content.

<m​ainnet_pat:monero.social> x.com/mainnet_pat/status/1907800302071296186

<m​ainnet_pat:monero.social> Big thanks to monero communty being supportive towards my work <3

r4v3r23 ANONERO Ms2 payout expedited and completed

<m​onerobull:matrix.org> That looks great

<w​oodser:monero.social> surprised there's no announcment on old.reddit.com/r/btc, maybe someone could post

<m​ainnet_pat:monero.social> I am out of reddit as it does not recognize me as a human anymore

<j​effro256:monero.social> Same

<j​effro256:monero.social> There's like a 10% chance on any given day that Reddit works for me

<s​yntheticbird:monero.social> poor SethForPrivacy node

<s​yntheticbird:monero.social> literally all the apps are using it by default

<m​ainnet_pat:monero.social> yeh. I am really sorry. But I have reduced the list I got from monero.fail by alot.

<m​ainnet_pat:monero.social> many do not respond or do not like some cors

<m​ainnet_pat:monero.social> I hope Seth likes me for blessing him

<m​ainnet_pat:monero.social> monero-ts does indeed do some strain on remote rpc

<w​oodser:monero.social> hopefully not adding more than using the core software directly would

<s​yntheticbird:monero.social> anyway pat love the UI, very simplistic and styling is 🤌

<o​frnxmr:xmr.mx> Should really host your own

<o​frnxmr:xmr.mx> I gave xmrbazaar shit about this too. Using random nodes from monero.fail, or abusing seth's, is a sure way to run into issues that you cannot troubleshoot

<o​frnxmr:xmr.mx> When dealing with users funds, you should not be relying on a public node to be accessible

<o​frnxmr:xmr.mx> And should not be relying on it to serve non-junk data

<o​frnxmr:xmr.mx> Either a) run a node specificially for the service or b) have users enter their own specified nodes. But dont c) use seth's

<o​frnxmr:xmr.mx> When multisig would fail on xmrbazaar, it was always because seths node was being ddosed.

<o​frnxmr:xmr.mx> I'm not sure about _today_, but a couple weeks ago only 3 (or maybe 15) nodes were accessible in feather. Public nodes are often ddosed, and random nodes from monero.fail cannot be trusted. In any event, service providers (xmrbazaar, axeswap) should run their own nodes. For both security and usability

<o​frnxmr:xmr.mx> Only 3 (out of* maybe 15) **

<m​ainnet_pat:monero.social> setting custom nodes, even not in a list of suggestions is suppoerted though!

<o​frnxmr:xmr.mx> especially this. Community nodes are provided by community members as a courtesy for users, not to be abused by service providers.

<m​ainnet_pat:monero.social> I get you. But this would raise a user suspicion of service centralization

<m​ainnet_pat:monero.social> like the app is by pat, the node is by pat, and the p2p relay is by pat - rigged scam no trust

<o​frnxmr:xmr.mx> I still stand by what i said

<o​frnxmr:xmr.mx> Should run your own node and don't offer seths to the slaughter. Seth's node is not reliable _because so many people do what you did_

<m​ainnet_pat:monero.social> not denying the validity of your point

<o​frnxmr:xmr.mx> well, imo, you have 2 choices: 1. offer your own (pats) node w/ option to use custom 2. Dont offer any node by default

<o​frnxmr:xmr.mx> Seths node was one of the 12 that was offline due to heavy ddos

<o​frnxmr:xmr.mx> He (and plowsof) are running a special configs to stomach the ddos

<o​frnxmr:xmr.mx> under default settings, their nodes arent reachable

the nodes require, CORS settings to be web accessible correct? so the pool of available nodes is further reduced

<m​ainnet_pat:monero.social> I see, your issue is that I have chosen Seth's node and I get your concern. In fact I have chosen it without any knowledge of ddos issues or else. I found it to be most reliable when testing on mainnet. I can simply put another one to be the default one or to be on top of the list to be chosen

<s​yntheticbird:monero.social> just a reminder that it is possible (it is even the only way) to put an http/CORS reverse proxy that link to non-CORS nodes

<o​frnxmr:xmr.mx> "Seths" node is indeed one of my issues - everyone abuses it. Its default inbitcart, was being used for xmrbazaar behind the scenes, many people in basicswap come for help and theyre always using seths node

<o​frnxmr:xmr.mx> Its overused.

<o​frnxmr:xmr.mx> but my _main_ issue is that remote nodes cannot be trusted unless you trust the op.

i hear spirobels browser wallet could connect to any node. that MITM proxy sounds both convenient and scary

<o​frnxmr:xmr.mx> so, swapping for a node that is not trusted, is worse than abusing seths

<o​frnxmr:xmr.mx> Example: chainalysis runs nodes/proxies to spy on users

<m​ainnet_pat:monero.social> In my app, both parties can choose different monero rpc nodes, they do not need to trust the node the other party would want to enforce to use them

<s​yntheticbird:monero.social> may not be added, but in theory Cuprate could add CORS support very easily

<o​frnxmr:xmr.mx> the only way you (as provider of the service) know that a node is not malicious, is to run the node yourself.

<s​yntheticbird:monero.social> LIAR

<s​yntheticbird:monero.social> SETH FOR PRIVACY WILL DIE FOR MY PICONEROS

<o​frnxmr:xmr.mx> I'm talking about you, pat, trusting the node you set as default

<m​ainnet_pat:monero.social> or you mean, me as the dev of the app suggest users the users the node which is on top of the suggestion list?

<o​frnxmr:xmr.mx> The users can use whatever they feel like. You, pat, should not be defaulting to anything that you yourself cant verify

<o​frnxmr:xmr.mx> Seths node is unreliable

<s​yntheticbird:monero.social> wyrc skids would like to have a word with you

<m​ainnet_pat:monero.social> I will lower the ranking of the seth's node in the list

<r​ucknium:monero.social> pat: Wonderful news! Thanks.

<r​ucknium:monero.social> Consider changing the Monero "testnet" to "stagenet". Testnet will likely hard fork to FCMP before stagenet. Probably, the choice of testnet/stagenet depends on whether you plan to write code for FCMP-compatible swaps sooner or later.

<r​ucknium:monero.social> And there is a typo: both fields say "Default Monero RPC Endpoint", but the bottom one is for BCH.

<m​ainnet_pat:monero.social> in which dialog do you see both fields say the same?

<r​ucknium:monero.social> pat: In settings

<r​ucknium:monero.social> Mainnet, Testnet, and Regtest

<m​ainnet_pat:monero.social> See it thanks

<m​ainnet_pat:monero.social> Fixed

<o​frnxmr:xmr.mx> "so, swapping for a node that is not trusted, is worse than abusing seths"

<m​ainnet_pat:monero.social> I am, and the app is not opinionated about the node to be connected to. I merely present the user the possible choices. It was by chance that seth's was on top.

<o​frnxmr:xmr.mx> i dont think youre hearing me

<o​frnxmr:xmr.mx> You cant just lead your users to the slaughter. You should npt even suggest any nodes that you cant personally vouch for

<o​frnxmr:xmr.mx> tldr: seths is likely the only node in your list that _can_ trust.

<s​yntheticbird:monero.social> seth for privacy cannot be trusted

<s​yntheticbird:monero.social> No one can

<s​yntheticbird:monero.social> it's muh cyPhErPuNk IdeOloGy

<s​yntheticbird:monero.social> naw gimme my reddit karma im big brain

<s​yntheticbird:monero.social> MoNeRo is the freeDoM!!!!!!

<o​frnxmr:xmr.mx> Note the italics

<o​frnxmr:xmr.mx> You could have claimed that moneroworld was trusted until we saw it being used on chainalysis videos

<o​frnxmr:xmr.mx> seth's node is better than some random one off of monero.fail, but youre still telling yourself that seth isnt and wont ever go rogue

<o​frnxmr:xmr.mx> There are at least 10 nodes on monero.fail that all have the same underlying node

<r​afael_xmr:monero.social> Negativo