01:51:24 <nakedpony> I have a confession
01:52:26 <nakedpony> I have seen a little bit about "moonero"
01:52:56 <nakedpony> until 2 minutes ago... I was wondering what was up with the cow thing
01:53:20 <nakedpony> I saw a "bitcoin to the moon" thing and i finally got it
01:53:36 <gingeropolous> u mean dis? https://monerom.ooo/ ?
01:56:27 <nakedpony> gingeropolous: hahahaha well I didn't at first, but this is the start of my weekend and I get to kick it off laughing at this cow
01:57:07 <nakedpony> *laughing {with} this cow
04:15:52 <doktoro> has the idea of making Background mining in the gui/cli opt out instead of opt in (if you are running a local node) been talked about? Was thinking about it today and was wondering what the community thought of that? I feel like it would help decentralization and wouldn't really hurt the user at all.
04:17:45 <lza_menace> seems rude, not everyone wants to bog down their system just to use a wallet
04:18:05 <doktoro> Does background mining really bog down systems?
04:18:29 <lza_menace> not much if only a thread on an average spec'ed system
04:22:46 <doktoro> over 60% of the network hashrate is held between 2 pools, and a couple days ago minexmr was at 50%. For everything I love about Monero I'm not a huge fan of this. Bitcoin has a better decentralization of hashpower between pools. :(
04:26:16 <doktoro> A very low mininmum background mining (that you can opt out of if you want) may help. I have not done any research to determine how much it would actually help though.
04:26:37 <lza_menace> depends on the usage patterns of users i guess
04:26:46 <doktoro> True
04:26:49 <lza_menace> i dont really run the gui or cli for prolonged amounts of time
04:27:01 <lza_menace> I get in, refresh against the chain, make transfers, then exit
04:27:10 <lza_menace> or sometimes just refresh the chain and exit
04:28:11 <doktoro> Yeah, refresh chain and then low background mine until gui/cli is turned off. Not sure how big of a change to the network that would actually have in practice.
04:30:51 <doktoro> When Making a wallet it could give you a prompt telling you that your wallet will background mine until the wallet is turned off and the benefits of mining and give you an opt out option.
04:33:05 <lza_menace> I'm sure people much smarter than you or I have already thought about this in depth :)
04:33:59 <doktoro> that's why I asked in my first message if the idea has been talked about. I wanted to hear what the concensus was. I'm sure it's been discussed but I personally have not seen talk about it.
04:34:37 <lza_menace> gotcha - try asking in #monero-pools
04:34:48 <lza_menace> some of those large pool operators hang out there
07:53:50 <endor00[m]> Meanwhile I can't seem to be able to disable automatic background mining in my cli wallet every time I open it
07:54:24 <endor00[m]> I try the 'set <whatever>' command but it doesn't seem to stick for some reason
08:00:28 <selsta> endor00[m]: make sure to use latest version and use `exit` to close the wallet
08:01:57 <endor00[m]> I think I built from the 16.0.3 tag. I'll look into it
09:01:51 <artefact> would it really make a difference? let's assume 6k nodes running at... 80% uptime with an average cpu, maybe 4 kh/s. that's 20 megahashes per sec, or about 1% of the total hashrate
09:10:20 <selsta> artefact: automatic background mining is a wallet feature
09:12:39 <artefact> yeah, so the uptime would be even worse
09:12:57 <Inge-> Hm. I got "failed" on a transaction
09:13:01 <Inge-> No idea why
09:13:06 <artefact> especially once the average user realises he's spending extra power/heat for mostly nothings when he opens his wallet
09:13:11 <artefact> that or distro will patch it out
09:14:27 <selsta> is it disabled by default anyway
09:15:18 <selsta> Inge-: are you using your own node?
09:15:37 <artefact> yes. i was commenting wrt morning's backlog
09:18:42 <Inge-> selsta: yes
09:18:50 <artefact> --tx-proxy?
09:19:16 <Inge-> selsta: I tried to just re-do the same tx, and then the receiving wallet got notified of a possible double-spend. It did get mined however
09:19:47 <Inge-> so somewhat uncertain if the failure was wallet or node, and if it was the first or second attempt that actually got mined.
09:22:46 <Inge-> Another thing: Ledger can go to locked state *while* processing a tx
09:23:02 <Inge-> i.e. it seems the "screensaver timeout" is counting even if it is processing a tx
09:23:17 <selsta> maybe you can open an issue on their issue tracker
09:23:33 <selsta> they have a new dev which seems to be a bit more active
09:23:49 <Inge-> Yeah I saw there was a changing of the guard
09:23:55 <selsta> https://github.com/LedgerHQ/app-monero/issues
09:26:36 <asymptotically> Inge-: i noticed that too, i couldn't even unlock it when i woke it back up because it decided to run sooo slowly
09:26:43 <asymptotically> that it couldn't detect both of the buttons being pressed at once
09:27:59 <Inge-> heh. try using it to sweep_below a few hundred transactions :D
09:31:17 <Inge-> Hm. takes far longer than I am used to, for a tx sent to my node, to end up in the mempool somewhere out there
10:03:49 <selsta> should take a bit longer due to dandelion++
10:04:00 <selsta> but only a couple seconds in theory
10:04:42 <Inge-> aah yes that would explain it
10:05:53 <Inge-> From what version is dandelion++ activated?
10:06:01 <selsta> v0.16
10:06:20 <Inge-> noice
10:06:54 <Inge-> anyone heard from m2049 and gang lately? Have been real quiet for like 1.5 years or so?
10:07:21 <selsta> he is still putting out updates
10:07:36 <Inge-> yes, which is great!
10:07:39 <selsta> he is busy with his job
10:08:03 <Inge-> I try to remember to donate, but have been forgetful of late
10:08:05 <selsta> that’s the last thing I heard 1 year ago
10:53:30 <Inge-> I wonder if MS telemetry is now in breach of GDPR
18:24:14 * moneromooo stabs firefox loading random pages from mozilla.org to.... tell me about privacy. Hypocrits.
18:44:29 <artefact> how so? they're not perfect but still one of the better ones in that regard
18:45:00 <artefact> the cloudflare dns thing though... not sure about that brilliant idea
18:47:17 <moneromooo> Oh the rest are worse maybe. I'm not claiming any ranking.
18:47:47 <moneromooo> But auto opening pages (because it's more than one) to the mothership wihtout asking me is @&!*#$.
18:48:07 <artefact> that's annoying for sure.
18:48:07 <moneromooo> Especially when it's to tell me they care about my privacy.
18:48:31 <moneromooo> And these are the poeple that auto installed some blob to play mp4. Which would auto update silently.
18:48:50 <moneromooo> Who suddenly disabled the "no images" setting. And IIRC the "no javascript" setting.
18:48:50 <artefact> firefox is the only browser that 100% works with umatrix, so i don't really have a choice. also linux is definitely a 2nd class citizen wrt new cool features regarding hw accel
18:48:59 <moneromooo> Every once in a while, FF fucks you over.
18:49:21 <moneromooo> But sure, there's worse. Google, Cloudflare, MS.
18:49:43 <moneromooo> Facebook. Doubleclick (oh, I already said google).
18:50:19 <artefact> i still respect mozilla. back then it took some balls to release the netscape codebase. and it worked
18:50:32 <moneromooo> Silently disabling the "no js" seting was really heinous. All of a sudden, everyone could run their code on your computer.
18:50:53 <artefact> i think browsers have become too bloated and too full of code debt, but that's another issue
18:51:56 <artefact> that is indeed unacceptable. you don't use some kind of addon for that? (noscript, umatrix, requestpolicy)
18:52:44 <moneromooo> Oh, and adding a trap button next to the downloads button. Misclick and the current URL gets uploaded to some third party website, aloing with your IP. Seriously, from people who claim they respect your privacy.
18:53:15 <moneromooo> Happened to me a couple times. My fault, admittedly, but made way too easy.
18:53:58 <artefact> i agree, the pocket thing was idiotic
18:54:16 <artefact> good thing you can more or less move/remove any button in the ui to wherever you want
18:54:39 <moneromooo> Oh. I didn't know that.
18:55:15 <moneromooo> Oh, and it seems like it relaods the favicon (which I do not carea bout) every time you move the mouse over a tab.
18:55:52 <moneromooo> Which I often do on old tabs, just to close them. And I can't find how to add the close button to non current tabs again, despite poring over an old config where it still works.
18:56:02 <artefact> mine dosen't- i host a few services locally so i'd see it in the journal
18:56:13 <moneromooo> So if you want to clean up tabs, boom, your old visited URL goes to the network.
18:56:13 <artefact> could be some addon or obscure setting i changed years ago though
18:59:40 <artefact> one thing i always forget, is that the resistFingerprinting setting also changes your reported timezone to utc+0. this got me in trouble a few times, as my boss uses services like doodle a lot
19:02:24 <moneromooo> Oh, and the time when it started parsing/displaying PDF files instead of asking you where to save them.
19:02:43 <moneromooo> Of course, I want to have you parse a complex format in the browser you twat.
19:03:06 <moneromooo> Since then a couple exploits were in that code, not unexpectedly.
19:03:28 <artefact> to the average user, the limited pdf thingy that runs in the sandboxed tab is probably safer than whatever other pdf reader software they use
19:03:32 <artefact> i'd say this is a good thing overall
19:03:54 <moneromooo> It did not ask.
19:04:04 <moneromooo> It just needs to ask *once*.
19:04:35 <moneromooo> Same for the disabling or js, images, etc settings. If what you're going to do has an impact on security or privacy, and you're a gui, ask.
19:04:35 <artefact> you're too smart for your own good, i think ;-) the devs just think "the average user won't know"
19:05:17 <moneromooo> That makes me think, maybe we should have a "set enable-openalias" in the wallet. Off by default.
19:09:33 <selsta> Having an option to disable openalias is probably a good idea though I disagree to disable it by default.
19:09:45 <moneromooo> Oh, it'd tell you what to do.
19:10:14 <selsta> That would work.
19:10:23 <moneromooo> But if enabled it will query DNS with the destintation, which you might not expect if you don't know how it works. And your ISP will know if it's not DNSSEC.
19:10:45 <moneromooo> Well, even with DNSSEC. I don't think it's encrypted.
19:10:49 <artefact> uhhh dnssec afaik is clear signature
19:10:56 <artefact> DOT/DOH isn't
19:13:07 <fluffypony> correct
19:13:15 <fluffypony> dnscrypt / DoT / DoH / DoTor are all good
20:06:44 <Inge-> hmm ... https://old.reddit.com/r/Monero/comments/i955g6/fatf_wants_to_ban_peer_to_peer_trading/
23:25:59 <lakesh> for me that i'm connected on external daemon how to print_block ....
23:26:31 <moneromooo> Can you rephrase ?
23:26:53 <lakesh> i have wallet-cli connected on external daemon
23:27:02 <lakesh> node.xmr
23:27:18 <moneromooo> And you want to print a block ?
23:27:22 <lakesh> yes
23:27:49 <lakesh> block number 11111
23:27:50 <moneromooo> You might be lucky with the console: ./utils/python/console node.xmr 18081
23:28:02 <moneromooo> daemon.get_block_header(1111)
23:28:11 <moneromooo> daemon.get_block_header_by_height(1111)
23:28:43 <lakesh> whereis utils
23:28:46 <moneromooo> Well, you get some of the block data I ugess.
23:28:59 <moneromooo> That's a subdirectory of the root monero tree.
23:28:59 <lakesh> i donwloaded binary
23:29:06 <lakesh> ah
23:29:17 <moneromooo> Ah. Then you get to run your own daemon. Or check xmrchain.net.
23:29:52 <lakesh> blockchain is 80gb
23:29:53 <moneromooo> You could also run monerod in proxy mode.
23:30:08 <moneromooo> Pruned, it's only ~25 to 30 GB.
23:30:10 <lakesh> the problem is the size
23:30:19 <lakesh> i must download and prune
23:30:38 <moneromooo> Proxy mode does not download (not really recommended though, but if you dib't have the space...).
23:30:55 <lakesh> ok proxy mode
23:31:10 <lakesh> i dont have lot of money so no big risk
23:31:12 <moneromooo> Can't recall the options rn, let me check.
23:31:39 <asymptotically> lakesh: what do you want to do with the block?
23:32:03 <moneromooo> --bootstrap-daemon-addres node.xmr --no-sync
23:32:05 <lakesh> to c txid
23:32:25 <moneromooo> Then you can run "print_block 11111" and it'll proxy to the other daemon.
23:32:35 <lakesh> this is for wallet-cli
23:32:37 <moneromooo> Which can lie to you of course  since you don't check as you don't sync.
23:32:50 <moneromooo> Yeah you'd do that from monerod.
23:34:46 <lakesh> this is saying "SYNCHRONIZATION started"
23:35:24 <moneromooo> Might do. It should not actually sync with --no-sync though. It'll just proxy RPC.
23:36:12 <lakesh> print_block 21642Error: Unsuccessful
23:36:32 <moneromooo> What does "status" say ?
23:36:51 <lakesh> Height: 35570/2164575 (1.6%) on mainnet, bootstrapping from node.xmr:0, local height: 35570 (1.6%), not mining, net hash 171.51 kH/s, v1, 8(out)+0(in) connections, uptime 0d 0h 3m 13s
23:37:33 <moneromooo> Oh, it's actually syncing, looks like.
23:37:49 <lakesh> what to do
23:37:56 <moneromooo> Guess you quit.
23:37:56 <lakesh> exit
23:37:58 <asymptotically> did you forget the .to after your daemon address too?
23:38:24 <moneromooo> The :0 is odd. Add :18081.
23:38:32 <moneromooo> (to the daemon address)
23:38:43 <lakesh> ./monerod --bootstrap-daemon-addres node.xmr --no-sync
23:39:08 <lakesh> ./monerod --bootstrap-daemon-addres node.xmr:18081 --no-sync
23:39:21 <moneromooo> Looks right.
23:39:41 <moneromooo> Maybe it's a bug that it syncs even with --no-sync.
23:39:50 * moneromooo never used that facility
23:39:51 <lakesh> same
23:40:01 <lakesh> again is syncing
23:42:09 <lakesh> there is print_tx on wallet-cli ?
23:42:29 <asymptotically> you could look it up on an online block explorer like xmrchain.net too
23:44:16 <moneromooo> There is show_transfer, which only works for your own txs (sent or received).
23:44:57 <moneromooo> show_transfers will show you an abridged version of all your txes.
23:45:08 <moneromooo> show_transfer TXID for details.
23:46:51 <lakesh> yes good command but when u do monerod print_tx u have more infos
23:47:16 <moneromooo> Yes. Incentive to run your node :)
23:47:50 <lakesh> i cant download pruned blockchain somewhere
23:48:40 <selsta> you can sync with --prune-blockchain, it will not download and prune afterwards it will prune from the beginning
23:50:08 <lakesh> the size of pruned will be not bigger than 25gb ?
23:50:16 <selsta> it will be 27GB or so
23:50:21 <lakesh> ok
23:50:23 <selsta> but not bigger, no
23:50:29 <selsta> it will get bigger over time but only slowly
23:50:34 <lakesh> i have no choice
23:50:53 <selsta> make sure to use v0.16.0.3
23:51:13 <lakesh> ok
23:56:54 <lakesh> what else to insert on command line except --pruned-blcockhain
23:58:30 <selsta> prune-blockchain not pruned-blockchain
23:58:32 <msavoritias[m]> <lakesh "what else to insert on command l"> Did you write it like that? Because its written wrong here
23:58:46 <lakesh> ah yes --prune-blockchain
23:59:02 <selsta> nothing necessary
23:59:38 <lakesh> thnx all