04:53:19 <spacekitty420[m]> <ooo123ooo1234567> "from matrix side it's always..." <- even from matrix you can manually @ someone, quoting can be useful but in most cases you used the feature, you really didnt have to as the context for it was already there (also, less quoting means less scroll to actually see the context and it'... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/dd518c152cc21c810524387c7932ebb7422e9d58)
06:52:49 <vicsn2> Obligatory meme without value judgement: https://xkcd.com/1782/
07:02:17 <rbrunner> Yeah, it's so much better that about every 3 years your favorite darling is totally out and something else is totally cool, and everybody has to switch every 3 years.
07:02:26 <rbrunner> Because people have nothing else to do, you know.
07:02:38 <rbrunner> (darling chat app)
07:34:41 <rbrunner> In the 5 years I am into Monero I have already left behind Mattermost (once bridged to IRC) and Keybase (once used by the Haveno team)
07:34:48 <rbrunner> So once every 3 years sounds about right :)
07:36:33 <rbrunner> And sorry about the non-research. Just a boomer rambling because nobody else around to stop me
07:36:51 <ErCiccione> please -lounge
07:36:54 <ErCiccione> There you are. Stopped 🙂
14:11:05 <UkoeHB> last minute proposed change to jamtis: https://gist.github.com/tevador/50160d160d24cfc6c52ae02eb3d17024?permalink_comment_id=4204089#gistcomment-4204089 please let me know any comments asap, I'd like to squeeze this change into my monerokon presentation
14:43:33 <jberman[m]> can you explain the benefit a bit more?
14:44:49 <rbrunner> That's secret key #7 now? I guess the complexity difference won't be that great - it's anyway scary already :)
14:44:51 <UkoeHB> the benefit is a find-received scanner and generate-address hub can't combine into a payment validator
14:45:25 <UkoeHB> with this change, you can only make a payment validator if the main view-balance wallet spawns one
14:46:23 <jberman[m]> ahh, got it I follow
14:46:54 <UkoeHB> (combining find-received and generate-address still lets you find all normal enotes, but after this change you won't be able to read the amounts)
14:47:55 <rbrunner> Is it worrying that this wasn't discovered until now? Or, in other words, how do you judge the probability that somebody finds a way to combine some of the other keys to to "forbidden" things?
14:48:23 <UkoeHB> I knew about already, it just finally nagged on me enough to think up a fix
14:48:30 <rbrunner> Ok :)
14:52:11 <UkoeHB> rbrunner: there shouldn't be any other weird interactions, but I'll think about it
14:53:29 <rbrunner> Nice, can't do harm, I guess.
14:54:41 <jberman[m]> downsides are that (1) a user who wants either a payment validator or an address generator has to handle more keys for either use case (4 with this change vs. 2 before this change), and (2) added complexity to address generation + scanning?
14:55:27 <UkoeHB> the added complexity is pretty small
14:55:39 <UkoeHB> I will write a commit in a couple hours to show
14:56:52 <UkoeHB> yes there are more keys to handle, but no 'new' ways to handle keys (just larger structs really), unless there is an extremely constrained key management environment
14:57:14 <jberman[m]> seems a solid tradeoff to me. adds defense/greater separation of uses
15:29:39 <ooo123ooo1234567> <ErCiccione> "please -lounge" <- grab that scammer and go there together, would be much more helpful
16:40:00 <UkoeHB> ooo123ooo1234567:  control yourself or get banned from this channel
17:03:39 <ooo123ooo1234567> <UkoeHB> "ooo123ooo1234567:  control..." <- let's discuss all rules for the channel firstly, I have no problems with following rules, but I'll point out all cases where others break them too
17:07:38 <ooo123ooo1234567> <UkoeHB> "ooo123ooo1234567:  control..." <- if you all are going to continue doing the same incompetent actions like before in public without any changes, then indeed, there is no other way except banning me (probably few times in a row for enough strong signal, that I'm the only one who must leave)
17:12:22 <hyc> or, you could analyze why the way you're delivering your message is annoying literally everyone else around, and see if there's a more effective way to make your point
17:12:33 <hyc> that doesn't turn all the active developers and researchers against you
17:14:45 <UkoeHB> ooo123ooo123457 guess what? I checked logs just to see if you had anything constructive to say about the jamtis update. Instead I am confronted with this continuing garbage. Strike 1
17:15:43 <UkoeHB> There are no strict rules, but there is a line and you are way over the line.
17:32:05 <ooo123ooo1234567> if it's possible to make a warn like "control yourself or get banned from this channel" and it's impossible to list all rules due to "There are no strict rules, but there is a line and you are way over the line." then it's called ping-pong where no one is responsible for everything. Please, prepare all rules the next time and warn me in case if I've been removed from your personal ignore list.
17:43:28 <hyc> if you need to know the specific rules because you plan to go right up to the limits of them, I think You're Doing It Wrong
18:19:46 <gingeropolous>  -_-
18:44:23 <UkoeHB> jberman[m]: https://github.com/UkoeHB/monero/commit/9026789d75b2f0a6164c19a8b3214c83d33a22fe mostly just plumbing it through the call tree
21:24:05 <jberman[m]> LGTM, I'm for it
21:41:20 <UkoeHB> jberman[m]: very first working unit test with enote scanning https://github.com/UkoeHB/monero/blob/fb75e5dcc31da91bcce4975de7ed26509c1280a0/tests/unit_tests/seraphis_enote_scanning.cpp#L151 still a lot more testing to do but yay! big milestone
22:03:09 <plowsof[m]> can one of the people qualified / allowed to leave emoji reactions place a rocket and or confetti and or a simple thumbs up on the above comment? 
22:18:08 <jberman[m]> woooooooot 🎉
22:20:13 <jeffro256[m]> this is huge !