00:03:11 <selsta> I personally think a separate program would be better suited for that.
00:07:54 <gingeropolous> for maintenance / upkeep purposes?
00:08:06 <gingeropolous> it would be nice for noobs if everything was available from getmonero.org
00:08:18 <gingeropolous> as opposed to having to navigate the messy world of cryptocurrency mining
00:09:15 <gingeropolous> i see the appeal of 1 single software to manage your monero stuff
00:11:33 <moneromooo> Oh, yeah. Add a monero wallet to emacs!
00:22:15 <bevanoff[m]> So I guess the problem with a pool miner in the GUI is that for simplicity there’d probably be a list of pools hard coded in but what if core hosted and maintained a dns list like people do for the open rpc nodes?
00:28:26 <bevanoff[m]> Actually ever mind that’s probably a bad idea
00:28:46 <bevanoff[m]> Probably better as a separate program
05:21:16 <gingeropolous> so is my split up the inputs from different remote nodes complete nonsense?
05:21:48 <gingeropolous> or is it so cool we need to come up with a l33t name for the protocol and make a pre-announcement
05:22:15 <gingeropolous> like Ringnet Protocol
05:24:28 <gingeropolous> or .... simulpull. no thats bad
05:25:24 <gingeropolous> ooh got it. Nectar Protocol.
05:25:33 <gingeropolous> because the wallet is like a bee pollinating a tx from multiple nodes
05:26:14 <gingeropolous> hah, and it can even mimic the temporal nature of pollinating by having a random delay between input pulls
05:27:16 <gingeropolous> so you can get a ring member spread across the 4th dimension, which is something that isn't even possible on the blockchain
05:27:25 <gingeropolous> not a ring member, but a ring construction
05:27:49 <gingeropolous> someone tell me im talking nonsense
05:48:07 <luigi1111> yes
12:56:59 <gingeropolous> couldn't stop thinkin about it last night. thought maybe we could do a reverse dandelion stem. Wallet user A requests tx material from node B. Node B then requests the same thing from node C. Node C from D. etc
13:24:18 <gingeropolous> any node in the chain wouldn't know that the one requesting the tx data was the one creating the tx
14:19:15 <gingeropolous> but nodes in the chain may have to select a new random node from their p2p list, as opposed to using the peers they're already connected to
14:19:32 <gingeropolous> to mimic the behavior of wallet users that use remote nodes
14:19:49 <gingeropolous> that might do it. nonsense?