00:38:24 "I encourage a certain someone to..." <- "productive conversation with a group of people with a lot of conflict interests that force them to trade-off security for something else so easily" it's impossible 00:39:42 "I encourage a certain someone to..." <- "... and encourage everyone else to be more aggressive at changing discussions to get back on topic when someone is clearly trying to derail." define the goal, it isn't clear whether it's a derail or rail 00:40:16 "I encourage a certain someone to..." <- I hate you for stupid msg like "seems consensus reached", the same happened during discussion of Triptych multisig 00:54:29 "whoever you would give your..." <- I had to explain why exploits are exploits and got only 100xmr for it, 0 respect, 0 credit, resubmit of PR by those who didn't care about deeper inspection; indeed, why not tell these people now what the issues are 00:55:05 "vulnerabilities in unmerged code" <- there is comp-sci bug with deadlock, in mainnet code, but does anyone care ? 01:03:48 how much would've been required to not be "only"/ 01:03:51 ?* 01:07:30 "So they've claimed this, there's..." <- there were/are examples with denied existence/importance even for comp-sci bugs with reproducible tests pushed into repo; indeed, no evidence, no one else has found them, it's obvious they don't actually want to help; indeed, you all would appreciate it 01:08:15 Can we not necrobump discussions please 01:08:39 (kaybanerve, I've already said that I don't care about etiquette ) 01:08:41 No one's saying there weren't p2p issues. jberman spent weeks going through them. We appreciate the work 01:09:09 It feels like you're just trying to start an argument though. I have no idea why these are coming up now nor what triggered it 01:09:12 kayabanerve[m]: jberman spent weeks on personal learning of code via reproducible tests from my PR 01:09:16 it's education 01:09:32 Like if you want to further discuss this, because you're frustrated, PM us, please. Don't spam #monero-dev:monero.social 01:09:56 And if the other person doesn't accept your PMs, that's their choice. You didn't accept mine 01:10:32 My message was also about multisig specifically. 01:15:04 "ooo123ooo1234567: Tell koe one..." <- knowing we it would be better to say: there are 100 other interesting projects / bounty programs that you can pursue instead of wasting your time here, and I can help somehow with them 01:15:18 instead of suggesting 10xmr, which is like 100% disrespect 01:15:33 s/we/me/ 01:15:35 ... if I offer you a thousand dollars from my personal funds, it's not direspect 01:15:51 I wasn't saying it's a fair bug bounty. I've already commented on my thoughts there 01:16:01 But you realize I'm not a millionaire, right? 01:16:19 I offered you multiple percent of my cash if you could submit a valid bug 01:16:28 So no, it's not disrespect. It's what I could. 01:17:25 kayabanerve[m]: it would be better to not say anything money then, instead of suggesting that amount 01:17:30 * say anything about money then, 01:18:19 If that's your opinion, that's what it is, but you should realize that when community members put forth what they can, it's meant to be a reward for volunteers. It's in no way disrespectful, and it should still be a pleasant treat to receive. 01:18:32 Plus, it's free money, if you're going to submit it anyways. 01:20:31 acknowledge that you outcompete someone worth more than any direct financial compensation 01:20:41 at least for me 01:23:23 ? 01:23:34 Oh. Got it. Sorry, took me a second to understand 01:23:41 I did also say "Prove you're superior" :p 01:24:03 kayabanerve[m]: I've proved when had to explain why exploits are exploits already 01:24:08 or when explaining why bugs are bugs 01:24:16 > <@kayabanerve:matrix.org> I did also say "Prove you're superior" :p 01:24:16 * I'd proved it already when had to explain why exploits are exploits already 01:24:38 luigi asks "how much would've been required to not be "only"?" (reg 'only' 100xmr) 01:30:28 This starts to feel like a case of "Prima Donna Syndrome". Nasty. 01:32:30 it would be better to analyse bugs in code (which is open source and public) instead of analyzing concrete humans 01:33:21 TrasherDK[m]: if I don't comment on personality of others then it doesn't mean that I don't have questions to them 01:33:47 but it looked like discussion of technical problems is much better 01:35:27 "how much would've been required..." <- why do you focus on that amount instead of all other problems that I've called before ? 01:37:24 because you brought it up and it's relevant to me 01:58:45 MONERO is going LIVE in Boston Harbor on the 4th of July. 01:58:45 should I ride in on a fluffy poney? 02:03:08 Try community or main for that question. 02:10:32 "word" <- How much would it cost to change your word to something like "I'm against cryptography changes without rigorous proofs, security is much more important than any short-term benefits from new features" ? 02:20:28 https://nitter.42l.fr/matthew_d_green/status/1537144725555355649#m, "As academic researchers we’re doing this for the research credit, not the bucks. Nobody is going to report bugs to big corporations if that isn’t respected."; comment about motivation of researchers said not by me 02:56:12 "because you brought it up and it..." <- do you ignore all other problems since they are going to be fixed ? 02:56:21 s/are/will/, s/going/not/, s/to// 02:57:27 "there is comp-sci bug with..." <- I care, I spent this whole beautiful saturday on this + tx pool related stuff 03:23:03 no 03:29:16 it would be interesting to participate in discussion of full list of problems that are supposed to be fixed and not be fixed 03:30:59 judging by replies in the above meeting, it isn't obvious that there is some non-zero intent to change something 03:36:11 if I'd want something to change some rules then I'd try to firstly stop breaking them by myself 03:36:16 s/something// 04:33:11 "I care, I spent this whole..." <- you've started since 2nd July (at least in public, https://libera.monerologs.net/monero-community/20220702#c116207), but I've replied to tobtoht comment from 30th June, and that problem is existing since 27th June (https://libera.monerologs.net/monero-dev/20220627#c113240) in public; 04:41:03 Ya once it became abundantly clear you had no intention of PR’ing the solution you already found 04:55:42 "now ooo asks all developers to..." <- do you agree with it or not ? 05:00:38 "Ya once it became abundantly..." <- It would be wise to blame for a bug those who created it, but not those who've spent time on investigation whether that bug is related to their PR or not 05:00:43 s/wise/better/ 05:01:10 Retrospective analysis should be applied to source of bug, but not source of solution 05:06:08 Analysis should be applied to both. The source of a bug’s problem and solution are both obviously important. In a healthy collaborative developer environment you would actually share what you know on both fronts 05:06:21 So that we can move forward avoiding similar problems in the future in an actually efficient way 05:09:04 https://teddit.net/r/Monero/comments/sw5t09/seeks_funding_ccs_jberman_fulltime_development_3/hxo1kuu/?context=10, "I like to be pushed. And I welcome this push. I want to reach a higher bar and demonstrate that I am capable of it, leaving no room for doubt." If I would say something like then I wouldn't complaining about any technical challenges on the way 05:09:10 * https://teddit.net/r/Monero/comments/sw5t09/seeks\_funding\_ccs\_jberman\_fulltime\_development\_3/hxo1kuu/?context=10, "I like to be pushed. And I welcome this push. I want to reach a higher bar and demonstrate that I am capable of it, leaving no room for doubt." If I would say something like this then I wouldn't complaining about any technical challenges on the way 05:12:16 Unsolved technical challenges from the code I like to solve. Human problems like convincing you to collaborate and participating in games not as much 05:12:58 What's about human problem like me convincing others to not follow path of least resistance ? 05:13:16 I'm spending time on both: technical challenges and humans, 2nd one isn't successful yet 05:14:39 ooo123ooo1234567: The path of least resistance would be not repeating work that has been completed, and instead reviewing or improving upon it 05:16:23 No comment on your human challenges. I would just like to see better code and us moving forward toward better code collectively and I think you are holding that back 05:18:07 Did you notice at least one case when I blamed someone who knows solution for not disclosing it ? 05:19:33 jberman[m]: I didn't receive credit even for my patch for multisig which was resubmited, it's one of the reasons to not release everything asap currently 05:21:48 Everyone credits you including koe idk what you’re talking about 05:22:25 ooo123ooo1234567: No one does this except you 05:33:50 "Everyone credits you including..." <- I'd say after resubmit it's impossible to separate contribution to PR from my side and from UkoeHB, and explicit questions a this only confirmed it 05:34:04 s/a/about/ 05:35:00 You’re complaining the git history won’t immortalize your anonymous account? 05:40:48 There was reasonable justification for why a new PR was made. This is petty 06:00:23 "You’re complaining the git..." <- No, it's required for a confirmation that I've solved task properly from the first try and all changes on top are unimportant (including those suggested in comments) 06:05:06 Required for who? 06:19:35 for me that I did work well, for others that they did bad review 06:20:41 It's like someone submit fix to bounty program 06:20:53 then incompetent developers slap patch on top of it -> squash it -> release as collaborative efforts 06:21:15 don't know why someone would like to participate in such collaborative environment 06:21:24 especially those who are doing original work 06:23:17 You weren’t responsive for months and it’s good code that people should run and that seemed the optimal way for the code to be used. And then you came back 06:31:59 Funny that there was no doubt to resubmit patch (presumably good, don't know why) of someone unresponsive, but there was no clear & public conclusion regarding that scammer 06:33:30 if work would be credited / rewarded based on it's quality then that scammer would be kicked immediately 06:34:01 * regarding that very responsive scammer 06:36:17 "You weren’t responsive for..." <- The only case when I wouldn't have any questions to UkoeHB 06:36:49 * to UkoeHB if he pursue security analysis too and done it faster than me 06:37:05 * to UkoeHB if he would do security analysis faster than me 06:37:33 * to UkoeHB if he would have done security analysis faster than me 06:43:14 https://libera.monerologs.net/monero-community/20220626#c113145, "project goal -> the next obstacle -> task description (at least should be verifiable and helpful for project goal)-> reward funding (add incentive to solve task, tasks with good verifiable description are supposed to be more attractive) -> submitted solutions (public log of incremental work done by participants, motivate to submit solutions asap) -> reward split 06:43:14 (unbiased judgement, punish incorrect solutions / spam); " did you this comment ? 06:56:28 "No one does this except you" <- Judging by inability to get concrete replies to critical questions, others are not disclosing all solutions too, but I don't blame them for it. 06:57:55 I want say that It's normal to say everything preliminary if you're doing original work 06:58:01 * normal to not say everything 06:58:47 and especially in non ideal collaborative environment 08:07:58 "Like if you want to further..." <- who are us ? 08:13:31 "This starts to feel like a..." <- funny that I'm the only one who is using fresh anonymous account and ignore any direct questions about identity; certainly "Prima Donna Syndrome", but not a try to prove the point 08:36:20 "There was reasonable justificati..." <- "Follow up to PR #8114. I lost contact with the original author two weeks ago." indeed, reasonable, especially in the context of broad problems with development (that scammer, no merges of p2p patches in time that didn't required hardfork, etc) 08:49:54 A question, just to gather facts, not to take side or even accuse: Back in January, when that "PR takeover" happened, did you speak up in any way? If you decided against, why? 08:52:10 You can't gather facts without looking into private communication, why not to focus on other problems that are easier to track via public log ? 08:52:19 There are so many contradictions in words of others 08:54:53 The point is that independently on actions of original author there are problems 08:58:01 Well, then I am a bit confused why you bring that January PR takeover story up now. Shouldn't we better concentrate on solving problems *ahead*? 08:58:27 Do you follow context of conversation ? 08:59:03 I think so, yes, jberman brought this up originally yesterday. I wonder why it looks you still want to *continue* that conversation. 09:00:53 First thing on the way to solve hard problems is to understand them. My understanding of the problem is still quite limited. 09:02:21 "A question, just to gather facts..." <- It wasn't expected step and there was no agreement to do, but for some reason it happened and it created interesting opportunity what others will do with my PR 09:02:55 * interesting opportunity to see what others 09:03:31 You mean you let it run back then because you were curious to see what happens next? 09:04:54 I was sure that I'll find some deep issues that will not be fixed within resubmitted PR, so it was a challenge that UkoeHB created by himself 09:05:22 I continued to work on security analysis and turned out I had found something 09:05:39 And resubmitting PR without understanding it is kind of interesting case 09:07:22 Hmm, looks like a high-risk venture to me, this course of action. Maybe you found out interesting things, as you see them, but with quite some risks and tradeoffs involved 09:07:25 It also added so much confidence to others, so that they were attacking even my p2p code after 09:07:27 https://github.com/monero-project/monero/pull/8365, though failed too 09:07:31 interesting story 09:08:37 rbrunner: It was risky for me too, but I took it as a challenge: whether I'll outcompete all of them or not 09:09:14 Technical problems are interesting, and challenge add motivation to pursue it to the end 09:09:23 s/add/adds/ 09:09:47 It may turn out to be a bit tragic that you indeed outcompeted them all but now can't reap the fruits because of the tangled relationship of the Monero dev community and you 09:10:02 That resulted from this all 09:10:15 rbrunner: It was an opportunity to prove the point in the most uncontroversial way 09:10:38 rbrunner: There is no justification in ignoring technical problems just due to personal disagreement 09:10:47 Well, lol, I think opinions differ widely whether that was indeed the "most uncontroversial way" 09:12:12 even auditors didn't find the issues 09:12:21 Ok, sorry, have to go again; maybe we find time to chat a little more in a few hours time, maybe better over in #monero-community if not strictly dev-related 09:12:22 how is it not the most uncontroversial way ? 09:12:28 I read the log in any case 09:13:49 Really sorry to create a cliffhanger, I am invited to lunch, those human things. 09:14:36 rbrunner: It just shows that something else is more important for you 09:20:09 "Hmm, looks like a high-risk..." <- If there would be no problems with CCS / hackerone / development process, then there would be no need in it 09:21:58 "It may turn out to be a bit..." <- "can't reap the fruits" what do you mean ? 09:29:56 "It may turn out to be a bit..." <- It would be enough to just admit development/technical problems (there are many of them) and do something to solve them, but for some reason those who blaimed me in "too much ego / behaving like 12 / etc" can't overcome their own personal goals in order to do improvements for project goal. 09:42:29 The project goal is to make the code better. No one here cares about anything more than that. You’re not making it easy to discuss that you want to add drama to things that aren’t worth drama 09:44:03 "Well, then I am a bit confused..." <- Do you need me to find examples in history of -dev/-lab when others are avoding discussion of technical problems once it reaches some difficulty ? 09:44:34 No, can we move forward? 09:45:05 Can you help move forward to a better direction? 09:45:38 yes, I'll list technical problems and others will confirm their importance and solve them and provide countrexample why they are not important and solve them 09:46:04 though it should be done somehow without abuse where I do the work and others only add minor comments on the result 09:47:11 Discussing unsolved technical problems sounds productive to me 09:48:15 https://libera.monerologs.net/monero-dev/20220517#c96445, "Fundamental concept is to approach common goal without compromises and with critical thinking." at the beginning it was very gentle pressure: let's set common goal, though everyone rejected 09:49:27 https://libera.monerologs.net/monero-dev/20220517#c96521, "16:33 UkoeHB ooo123ooo1234[m]: ‘critical questions’ pretty rich coming from someone who thinks he is too important to answer questions. Nice double standard" and this reply about whether it makes sense to reply to questions 09:50:24 These aren’t technical progressive discussions 09:52:33 "Discussing unsolved technical..." <- ok, let's try one more again with discussion of technical problem to see whether it will be stopped once it reached certain level of difficulty 09:53:26 problem with txpool: does required more time on investigation ? 09:53:28 * problem with txpool: does it require more time on investigation ? 09:54:53 (I can't use info from PM) 09:55:51 * important and not solve them 09:56:29 * yes, I'll list technical problems and others will confirm their importance and solve them or provide countrexample why they are not important and not solve them 09:56:59 Yea, to have a completely informed discussion on it yes? What does that have to do with difficulty 09:57:40 then txpool isn't suitable for discussion yet 09:57:43 any other problem ? 09:58:41 (deadlock isn't suitable since others think that I have a solution) 10:00:11 You said you wanted to list technical problems 10:04:13 bulletproofs++ 10:09:48 "Discussing unsolved technical..." <- https://github.com/monero-project/research-lab/issues/62, but it requires firstly choosing the design to implement among all those listed 10:11:03 https://github.com/monero-project/research-lab/issues/100, this one requires research (not clear whether it's even possible) + implementation + security analysis 10:17:55 "These aren’t technical progressi..." <- "Fundamental concept is to approach common goal without compromises and with critical thinking" I would firstly start from discussion goals since it looks like others have different priorities on what things to fix firstly 10:18:19 s/discussion// 10:18:31 and I strongly disagree with their priorities 10:25:11 All 3 are neat IMO and worthy of concrete rationale in a decision to pursue or not built on logic. From what I know.. bulletproofs++ have gotten very little love not borne out of academia, Janus has been sitting it requires wallet changes too which arguably could’ve should’ve been done along view tags, but we’re here now, zk snarks obviously worth research that’s absolutely critical imo 10:26:02 bulletproofs++ origin isn't argument for competent people who can verify it and implement it 10:26:36 Ya, agreed 10:26:56 jberman[m]: Please, don't mention argument against bulletproofs++ and then agree that it isn't an argument 10:27:04 I can't understand such quick change of opinion 10:27:12 Wasn’t an argument against 10:27:23 hmm, for me it was like an argument 10:27:41 Nah, just a statement 10:27:45 janus: did you read all those designs ? are you sure that all of them require wallet changes and can't be done in backward compatble way ? 10:28:40 zk snarks: this topic is very close to whether Seraphis is a way to forward or not, but it's very heavy an the same time 10:29:39 s/an/at/ 10:30:17 Hmm on Janus, there’s a non fingerprintable design that can be done at any time? 10:31:20 jberman[m]: https://github.com/monero-project/research-lab/issues/62, I believe so, otherwise I've not noticed some deep problem that prevents it 10:31:43 if you will just do C++ implementation like with view tags, then someone else should provide the design to you 10:33:00 for me subaddress privacy issues mitigation is much more important, than speed up from view tags 10:41:46 "Nah, just a statement" <- "bulletproofs++ have gotten very little love not borne out of academia" source for a statement then ? 10:43:14 "for me subaddress privacy issues..." <- Ya, I’d agree. It’s a larger byte bump per tx. But probably as if not more worth it considering. Did you argue for it in the past? 10:44:56 "Did you argue for it in the past?" is it possible to not ask questions about personal opinion ? In the worst case it's verifiable via logs checking 10:45:33 "But probably as if not more worth it considering. " is it a comment in favour or against ? can't understand 10:45:50 Sure. I think you make a reasonable point with it. In favor 10:47:11 jberman[m]: I don't like in your comment that make some conclusions without providing numbers 10:47:19 > <@jberman:matrix.org> Ya, I’d agree. It’s a larger byte bump per tx. But probably as if not more worth it considering. Did you argue for it in the past? 10:47:19 * I don't like in your comment that make some conclusions without knowing exact numbers 10:47:41 or you know them ? at least upper boundary on tx size increase? 10:48:52 jberman[m]: "I think you make a reasonable point with it" it would be better to replace with something like " it's about X bytes, while size of tx is Y, so it's reasonable trade-off" 10:51:23 I always try to find lower/upper boundary on effect of some change in order to preliminary filtering whether it's useful or not 10:51:29 don't know whether others are doing it, but it's useful 10:51:52 `-inf/+inf` means undefined 10:53:17 * default is `-inf/+inf` or undefined 11:00:56 32 bytes extra per tx not involving subaddresses and 32 bytes extra per output per tx involving subaddresses with 3+ outputs? Did I read it wrong? 11:04:54 Plus it feels like a more complex change to wallets to me, more involved edge 14:06:02 "It just shows that something..." <- I once had an employer tell me to treat my job like my kids.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/f451417d5b999e89d06213a44a7cb488527c63c1) 16:01:56 do i neeeed Docker on Ubuntu 18.04 for building Monero to Android? 16:02:20 i mean if we are building on Docker why do i need Ubuntu 18.04? 16:15:16 nah you shouldn't need docker then 16:16:23 depends build should work there 16:17:52 can i just use Docker to build to Android on Windows? 16:19:53 dunno, I've never tried to use docker on windows 16:20:17 why are you building for android on windows? 16:20:47 im using Windows 16:20:59 the thing i wonder about is 16:21:08 there are dependencies of Monero 16:21:24 where are they coming from on Ubuntu for ARM target? 16:21:39 aren't they pre-built archives? 16:28:55 no. in a depends build, most of the dependencies are built from source 16:29:45 okii goooooood 16:29:47 that's kind of why it's called a depends build... 16:30:13 https://github.com/monero-project/monero/blob/master/contrib/gitian/gitian-android.yml what is this for? 16:30:32 it's for building with gitian 16:30:45 which usually uses docker (or lxc) 16:30:50 on MSYS2 libraries are prebuilt archives 16:31:14 you don't have any prebuilt archives for android on msys2 16:32:02 yess 16:33:20 can i use WSL/Debian to use it? 16:33:48 i have no idea, never tried it 16:33:51 or should i be able to use Debian? 16:33:53 ummmm 16:33:56 supposedly wsl2 works pretty well tho 16:34:17 yess WSL2 is like just Linux 16:34:29 but i mean do i need Ubuntu 18.04 to build with Docker? 16:34:36 no 16:34:54 if you have ubuntu 18.04 you should be able to just do a depends build 16:35:19 if you want to use docker, it ought to work with any recent ubuntu or debian release 16:37:20 IMO using docker is the easiest approach 16:38:42 if i use Docker why do i need Ubuntu? 16:39:17 it will be faster 16:39:37 the docker build image installs compiler and a bunch of other stuff from ubuntu repos 16:40:04 it assumes you have apt-cacher-ng running on the host, to cache these images 16:40:15 afaik apt-cacher-ng is only available on ubuntu and debian 16:41:03 why there is no a Dockerfile? 16:41:18 but again, if you have ubuntu you can just build on ubuntu and ignore docker 16:41:56 there's no Dockerfile because it's more complicated than a dockerfile setup 16:42:31 anyway, this conversation is over. I've already given you the best advice on how to build. 16:47:39 im trying to run gitiean-build.py on Docker/Ubuntu 18.04 16:47:45 but im getting strange errors 17:04:41 TypeError: expected str, bytes or os.PathLike object, not NoneType 17:04:49 im getting this from gitian-build.py 17:04:53 on Ubuntu 18.04 17:10:16 ./gitian-build.py -j 5 --memory 10000 --detach-sign --no-commit --build rohanrhu v0.17.3.2 17:10:18 im doing this 17:10:28 subprocess.CalledProcessError: Command '['make', '-C', 'inputs/monero/contrib/depends', 'download', 'SOURCES_PATH=/root/monero/contrib/gitian/builder/cache/common']' returned non-zero exit status 2. 17:10:31 but getting this error 17:14:51 your invocation there doesn't use docker, is that what you intended? 17:19:02 im trying to use gitian-build.py on Docker/Ubuntu 18.04 17:20:23 I think all you need to do is follow the readme in contrib/depends 17:20:55 make HOST=aarch64-linux-android 17:21:03 that will build all the 64bit android dependencies 17:21:40 then cmake to build monero itself 18:56:33 .merges 18:56:33 -xmr-pr- 7774 8296 8356 8357 8358 8384