00:06:20 <selsta> We stopped using TravisCI a while ago.
12:06:06 <mj-xmr[m]> <xmrscott[m]> "Something I guess to be aware of..." <- Oh wow. I'm glad we're out of this before.
14:36:28 <justverify[m]> Hey guys I’m trying to fork the ccs proposals repo on gitlab, but I can’t do it due to an error. It says: “You have reached your project limit”
14:36:28 <justverify[m]> And then: “You tried to fork monero-project/CCSProposals but it failed for the following reason:
-Namespace is not valid “
14:36:28 <justverify[m]> There’s a way to solve this issue without having to delete and recreate the gitlab account?
14:38:57 <moneromooo> What is your login name on that site ?
15:09:12 <moneromooo> Well, I'm out for a bit, I'll fix it later if you post your login.
15:09:30 <selsta> Alternatively you can signup without Github Login.
16:26:29 <ErCiccione> moneromooo ^
16:27:10 <ErCiccione> justverify: what's the nick of your account on gitlab?
16:27:14 <moneromooo> Might have been filtered by my /ignore settings, I don't see a nick.
16:27:23 <slstmd[m]> somehow irc messages don't show up on matrix
16:28:33 <justverify[m]> ErCiccione: Bl5ckj5ck
16:28:40 <selsta> moneromooo: Bl5ckj5ck is the nick
16:28:50 <ErCiccione> i hope they read us on irc at least
16:28:55 <slstmd[m]> yes
16:29:47 <moneromooo> Should be fixed now.
16:30:39 <slstmd[m]> justverify: should be solved now
16:32:04 <justverify[m]> slstmd[m]: Yes! Thanks
17:46:25 <ErCiccione> From the meeting in -lab there seems to be support for a meeting dedicated to discuss the next hard fork and the consensus items that should go in. Is sunday 3th at 17:00 a good time for people here?
17:48:25 <gingeropolous> y all the way in octobeR?
17:49:11 <sethsimmons> ErCiccione: 17:00 UTC I assume?
17:50:06 <ErCiccione> yep, sorry didn't specify
18:28:14 <mj-xmr[m]> selsta: here's the proof, that we reuse the upstream's master's caches in the forks: https://github.com/monero-project/monero/pull/7928#issuecomment-920272185
18:29:18 <selsta> you linked to https://github.com/monero-project/monero/runs/3575081554 which isn't the fork
18:33:50 <carrington[m]> FYI anyone who uses this room but doesn't see the IRC messages at the moment, you can join
18:33:50 <carrington[m]> #monero-dev:libera.chat
18:33:50 <carrington[m]> Directly from Matrix
18:36:32 <Rucknium[m]> I talk to appservice and say "!join #monero-dev" 
18:36:32 <Rucknium[m]> Is that different carrington  ? 
18:37:02 <Rucknium[m]> It doesn't work for #monero:monero.social  though. It says that I need to register a nickname on libera chat.
18:44:41 <mj-xmr[m]> selsta: other than the `hashdir` fail, is the cleanup OK for you?
18:47:11 <carrington[m]> Rucknium  I think those have the same result, and I am not sure of the -community situation
18:55:18 <mj-xmr[m]> Anyway. I have just updated the branch, ditching the hashdir.
19:17:47 <woodser[m]> hi all, just want to confirm that publicly sharing input key images of unbroadcast txs is harmless (i.e. cannot reveal anything that can compromise privacy) because the associated ring is not known to the chain? my hope / assumption is that new key images posted in isolation before its tx is broadcast to the chain would pose no additional risk. is this correct or any thoughts to the contrary?
19:36:32 <woodser[m]> to give context to the use case: we want to attach key images of source funds when a haveno user posts an offer. this allows peers to verify that the maker's funds are unique and unspent. we need to be sure that sharing the offer's key images before the tx is broadcast would not allow an attacker to somehow link the offer with external data like poisoned outputs, thus allowing the trade to be targeted for additional info. my understanding
19:36:32 <woodser[m]> is sharing revealing key images should not pose any risk in isolation before the tx is broadcast
19:39:10 <woodser[m]> s/sharing//
20:10:25 <ellpepe[m]> Hi guys,
20:10:25 <ellpepe[m]> I'm new here.
20:10:26 <ellpepe[m]> I have decent skills in C#, Java, Python, JavaScript and want to extend my skillset by adding C++ to it. At the same time I'd like to support monero, therefore I followed Rucknium's call to introduce myself to this channel.
20:10:26 <ellpepe[m]> I have little experience with C++ but am motivated to change that :)
20:11:26 <moneromooo> Hi. Best is to find little things that seem broken and annoy you. Ping here to make sure it's something we want changed, then fix/improve it.
20:11:59 <moneromooo> This means you only get to deal with small amounts of monero at once, and gives you tangible progress.
20:12:33 <moneromooo> Inconsistent formatting etc etc aren't deemed broken in this context :)
20:12:48 <moneromooo> Minimal patches are preferred.
20:13:13 <moneromooo> Otherwise, there's haveno, a monero based p2p exchange, which is in java/javascript.
20:18:57 <Rucknium[m]> ellpepe: I'm pasting in moneromooo  's response since for some reason the IRC --> Matrix bridge is broken:
20:19:11 <Rucknium[m]> >This means you only get to deal with small amounts of monero at once, and gives you tangible progress.
20:19:11 <Rucknium[m]> >Inconsistent formatting etc etc aren't deemed broken in this context :)
20:19:11 <Rucknium[m]> >Minimal patches are preferred.
20:19:11 <Rucknium[m]> >Otherwise, there's haveno, a monero based p2p exchange, which is in java/javascript.
20:19:23 <Rucknium[m]> How can the bridge be fixed?
20:21:13 <moneromooo> First sentence got missed: Hi. Best is to find little things that seem broken and annoy you. Ping here to make sure it's something we want changed, then fix/improve it.
20:21:20 <moneromooo> Unless it's also a bridge drop.
20:25:27 <Rucknium[m]> ellpepe: Manually bridging again:
20:25:27 <Rucknium[m]> >First sentence got missed: Hi. Best is to find little things that seem broken and annoy you. Ping here to make sure it's something we want changed, then fix/improve it.
20:25:38 <moneromooo> ty
20:26:39 <ellpepe[m]> ah ok, thanks Rucknium 
20:27:10 <ellpepe[m]> and thanks moneromooo 
22:54:27 <jberman[m]> Post-mortem on the decoy selection algorithm bugs from 0.17.2.3: https://github.com/monero-project/monero-site/pull/1831
22:58:59 <jberman[m]> Biggest update from there: MyMonero/monero-lws did not have the widely publicized bug, and therefore very recent spendable real outputs could not be identified with certainty as widely reported
22:59:12 <jberman[m]> Once that post-mortem is finalized, I figure it makes sense for me (or someone with contacts) to reach out to news organizations to try and correct the prior statements, especially where I was quoted as saying real outputs were identifiable
22:59:27 <jberman[m]> This was a deeply unfortunate error, I've been grappling with it
23:01:45 <jberman[m]> It does mean privacy was better protected though, which is good news
23:49:01 <Rucknium[m]> jberman:  No real error, as far as I see it. Much better to be overly cautious than the opposite. You/we said what we knew at the time that we knew it, with the best information available at the time.