04:16:46 <xmrmatterbridge> <sgp_> I scheduled the community workgroup meeting at 16:30 utc this Saturday (30 minutes early)
04:16:58 <xmrmatterbridge> <sgp_> The coffee chat will be at 18 utc, shortly after the meeting
17:02:43 <Snipa> I'll probally end up mossing this week's community meeting unfortunately, that's a tad early for when I'm usually up and moving.  I'll have to catch up on the logs.
17:13:39 <sarang> Updated (and incomplete) draft to supply audit blag post: https://gist.github.com/SarangNoether/89a08ab5f9bd09350e653fb9b2e4e99b
18:33:38 <sgp_> This is hilarious: https://twitter.com/xmr_whale_alert
18:33:39 <monerobux> [ Clueless Whale Alert (@xmr_whale_alert) | Twitter ] - twitter.com
18:38:53 <rottensox> happy birthday monero. lol.
18:40:55 <fort3hlulz> XD
19:47:51 <Inge-> Nobody is addressing the real question in Monero in 2020
19:48:42 <Inge-> ... how to pronounce snipa
19:50:47 <lza_menace> well, it can't be "snip-uh" otherwise there would be 2 p's
19:51:08 <lza_menace> it's got to be "snyp-uh"
19:51:31 <lza_menace> maybe he plays a lot of FPS games and prefers to use snipers
19:51:38 <asymptotically> didn't we have this in #monero-pools yesterday? Mochi101 says it like "snipper" because of course he does, and everyone else voted for something that sounded like sniper
19:51:59 <lza_menace> .shrug
19:51:59 <monerobux> ¯\_(ツ)_/¯
19:53:45 <Inge-> on monero-talk it was Snaip-Ah like sniper, but I am just nok OK with that.
19:54:31 <selsta> Sneep ah
19:55:02 <asymptotically> i wonder why his parents picked such an odd name. they must not like him
20:10:35 <lza_menace> is there any sort of documentation or process in place for "passing the torch"? I'd be interested to know what the procedure is like and how things like domain registrations are managed and by whom
20:11:25 <lza_menace> I get that we all like decentralization, but we'll still need somebody/some group to maintain domains/DNS/content/etc
20:13:37 <selsta> Did you read the announcement blog post?
20:14:09 <lza_menace> which one?
20:14:21 <lza_menace> core team one, dec 16?
20:15:28 <selsta> yes
20:15:29 <lza_menace> I guess it does mention that
20:15:43 <selsta> yup bF and fluffy manage things like DNS, domain, etc
20:25:42 <lza_menace> new CCS page looks good...the old one (ffs?) was so spammy
20:39:22 <lza_menace> can we not clone repos from repo.getmonero.org via ssh?
20:40:45 <sarang> Apparently there's some kind of CloudFlare issue that would require running their code on the machine, or something like that
20:40:52 <sarang> mooo knows more details
21:04:20 <tevador> if anyone is running windows here, check if you are vulnerable: http://testcve.kudelskisecurity.com/
21:04:52 <koe> it sounded like the story around 'mixins' is being deprecated; previously it was commonly said that the MLSAG ring members was the mixin plus the real sender [ring size = mixin + 1]; what is the preferred semantics now?
21:07:30 <koe> sgp_ said some time ago to just use ring size https://monero.stackexchange.com/questions/3978/what-is-the-difference-between-mixin-and-ringsize is that still the party line?
21:09:43 <sarang> The give equivalent information
21:09:48 <sarang> *they
21:10:37 <koe> yeah Im thinking about semantics, consistency
21:11:53 <sarang> Is one or the other used in any public-facing interfaces like RPC calls?
21:13:00 <sarang> I happen to prefer "ring size"
21:13:20 <sarang> Since this corresponds to the input anonymity set parameter for various signature and proof constructions
21:14:34 <koe> looks like they are both used quite a bit
21:14:43 <koe> throughout the code
21:15:06 <koe> Ill stick with mixin since it's more obscure and more important to drill into people's heads
21:15:14 <koe> ring size is obvious
21:15:46 <sarang> Why is it important?
21:15:57 <sarang> Both are a measure of input anonymity set size
21:16:35 <koe> because someone encountering the code base will be more likely to think 'wtf is this exactly'
21:17:06 <sarang> I also don't like the term "mixin" since it makes people think of mixing, which is _not_ the same thing
21:17:23 <sarang> and that seems to get confused in articles all the time
21:18:06 <koe> I just have it as a footnote no big deal
21:18:34 <sarang> word
21:20:36 <koe> I think the word itself is confusing, but the concept is relevant to developers since 'selecting unrelated addresses from the blockchain' is an activity separate from actually signing messages
21:21:09 <nioc> no idea about the code but as far as use goes mixin has and is being replaced by ringsize
21:38:43 <sgp_> koe: I've been using ringsize since early/mid 2017
21:38:50 <sgp_> I have learned to like it a lot more
21:42:25 <koe> ok thanks guys