16:10:37 dev meeting today? 16:59:50 We can, sure. 16:59:58 And it's just about time. 17:00:21 Anyone around? 17:06:27 o/ 17:06:41 not a dev. just a fly. 17:11:45 i'm here 17:21:44 well Im sitting here, but it doesn't appear many others are 17:22:18 I have nothing to report anyway 17:22:20 I am here. Not much to say though. 17:22:39 v0.16 appears to be a pretty good release so far 17:31:33 From looking at action in the Monero subreddit, I don't think that even a single serious problem surfaced so far with 0.16. Pretty solid. (And of course not a serious problem that it *still* wants an update :) 17:36:15 One would wish to get hold of a good statistic how Dandelion++ gets rolled out, and how the percentage of txs broadcast using it grows over time, but probably impossible to get such overview 17:37:01 (And overall that's probably a good thing) 17:41:00 also to point out, yesterday marks 6 months of RandomX deployment 17:41:47 network hash rate is pretty steady, and number of miners has returned to its pre-hardfork level 17:41:56 Snipa: are you around? 17:49:27 technically 6 months of RandomX is today, not yesterday 17:49:47 What month length are you using ? 17:49:59 (if we're going to be pedantic, I want in) 17:50:01 *long rant about our primitive calender and month lengths follows* 17:55:04 We are in leap year. Don't forget. 17:56:18 let's just says 183 days 17:56:21 *say 17:58:16 +1 rbrunner 17:58:22 :) 17:59:01 We could schedule some little celebration for some round number of blocks mined with RandomX, say the next larger round number, whatever that is. I think the success would merit it. 17:59:54 I'd wait for at least 1 year. CNv1 also went 6 months with no trouble 18:01:03 Has something, that argument. 18:03:28 November 30 would be just after Thanksgiving, maybe we aim for a Christmas-ish celebration 18:03:42 early/mid December 18:04:36 or call it Yuletide ;) 18:17:56 150000 RandomX blocks (block 2128433) - June 25th 18:18:38 aligns nicely with Midsommar :) 20:31:27 how is it that we have such incurious users. https://old.reddit.com/r/Monero/comments/gu18ee/is_running_a_remote_node_heavy_on_hardware_and/fsgbld3/?context=3 20:31:47 people download and run software blindly, without looking to see what it comes with 20:34:20 By incurious, do you mean ignorant ? Ignorance is much better than stupidity, and the user you point to seems to have gone straight for it when you mentioned it. 20:51:28 I meant, not curious. Not curious enough to see what everything was in the archive of software they downloaded onto their PCs 20:52:01 they presumably just launched monerod.exe and ignored everything else. 20:58:29 Sure, but faulting someone for not getting up to speed fast enough is just harsh. 20:59:35 The post just shows ignorance to me, which is fine. 21:00:00 And once the pruned ability was pointed out, the user just went and tried it. 21:03:41 it's not about getting up to speed or not. It's about being aware of what you just downloaded and installed. 21:04:14 just like in #monero the other day, when I was telling someone how to plut the output of monero-blockchain-stats "I was not aware this tool existed" 21:04:24 it's understandable to not know how these tools work 21:04:35 it's not understandable to not know that they're sitting there on your drive 21:05:01 It's totally understandable. There is shitloads of crap on my drive right now I have no idea what it does. 21:05:24 There's just so much stuff around, and finite time to get through all of it. 21:05:29 if it was bundled there before you fired it up, that's one thing 21:05:46 What is important is the willingness to go through it when it's pointed out, not whether you knew about it in the first place. 21:05:46 if you downloaded it yourself, extracted the archive yourself ... that makes no sense to me 21:06:04 Meh. Depth first is fine, but breadth first also is. 21:06:34 I downloaded the GIMP, and I search the web when I want to do something not super simple. 21:06:46 It's nornal. There is a LOT of stuff around. 21:07:04 but this is like extracting an archive and ignoring the README file 21:07:05 Learning about it all first thing would be a waste of time. 21:07:19 OK, fair point here. 21:07:43 Our README does not mention pruning, I just looked :D 21:07:50 My fault I guess. I'll add. 21:08:16 ;) 21:08:59 Hmm. If I mention pruning, I guess I sohuld mention a lot of other stuff -_- 21:09:59 What we'd want is a documentation, in addition to the README. 21:10:19 * moneromooo looks at the mountain and gulps 21:10:55 should start shaking the trees for tech writers 21:11:15 and maybe launch a CCS for a writer to team up with a dev 21:12:46 i do readmes on websites and github but rarely from zips. the only time it would be super pertinent would be like a router firmware or something? 21:14:29 lots of devs put notes in the release ntoes/change logs. how many people read those? like a psychopath, i actually do. 21:14:53 good! :) 21:15:12 What's a README ? 21:15:37 * moneromooo afj 21:15:42 i treat them like little christmas 🎁 21:20:48 It's kind of a big ask for every user to be an expert on everything they download. 21:23:32 not to be an expert. 21:23:40 to be aware that these things exist. 22:37:33 and maybe launch a CCS for a writer to team up with a dev <= Not a bad idea imo 22:38:11 Would need a well delineated scope though. 22:38:31 Or a lot of time :) 23:14:23 "team up with a dev" sounds like you're getting volunteered moneromooo :p