09:01:17 so, now that you've registered with this new server, do I have to make any changes on my end? I am confused 11:25:44 so is there any interest in removing simple mode? 14:16:32 Yes 14:17:33 Its not a simple removal though. As you know, simple mode isnt a wallet feature, its a gui hack and a node feature 14:20:16 So we'd be removing bootstrap-daemon=auto, but not bootstrap-daemon=insertAddress. 14:20:16 and gui would have to redesign simple bootstrap mode to allow manual input of a node, and to remote node, and for "simple" mode to stop running a node (bootstrap + no-sync hack) and to just use advanced mode + configure a remote node. 14:20:18 annoying changes to implement imo 14:20:48 "and to remote node" << delete that 14:24:05 Arguably then we would need to specify a list of default nodes 'trusted by the community' 14:24:42 No 14:25:48 GUI is a "reference" software. We shouldnt include trusted features (community nodes) or hackish features (simple mode) that are centralized or potentially privacy and security harming 14:26:46 If someone wants "community nodes" they should use another wallet, like cake, stack, feather or some other wallet that provides nodes trusted by the wallet provider 14:26:57 * moneromooo has this twitter-in-wallet flashback... 14:27:25 Introducing "community trusted" nodes to gui is just asking for all of those wallets to be MITM or ddosed 14:28:14 imagine shipping community nodes with cli. Yeah, same difference here 14:29:26 I would assume that the majority of nodes running with --public-node (used for bootstrap) are spy nodes 14:31:49 list of nodes "trusted by the community" << even cake and monerujo had node.moneroworld.com in their node lists, and moneroworld was pointing to spynodes for yrs 14:49:30 ofrnxmr: I agree with you in principal, but from a UX perspective not having a list of nodes to choose from will cause a lot of friction 14:50:26 Please choose node type: [ ] centralized [ ] adversarial [ ] yours 15:04:25 :D