07:40:30 <KiloLima> 2020-02-24 05:02:32.227 W [3.9.95.50:63319 INC]  peer claims higher version that we think (13 for 9999999 instead of 12) - we may be forked from the network and a software upgrade may be needed
07:40:31 <KiloLima> 2020-02-24 05:07:00.586 W [3.9.95.50:3322 INC]  peer claims higher version that we think (13 for 9999999 instead of 12) - we may be forked from the network and a software upgrade may be needed
07:43:28 <selsta> you can ignore it or ban the IP
07:43:37 <KiloLima> alright
11:14:20 <fluffypony> ErCiccione[m]: I'm ready to go on it, just waiting for pigeons to find some time away from his newborn to set it up :)
11:19:19 <selsta> fluffypony: any update on moving monero-project to an org?
14:40:52 <ErCiccione[m]> fluffypony: alright, thanks. And congrats to dad pigeons!
15:45:57 <fluffypony> selsta: it's done
15:47:00 <selsta> nice :D
15:48:58 <selsta> can you give dEBRUYNE, xiphon and me triage rights for GUI repo?
15:49:06 <selsta> also ErCiccione[m] if he wants
15:49:52 <fluffypony> selsta: what's your GitHub username?
15:50:26 <ErCiccione[m]> Nice!
15:50:34 <ErCiccione[m]> yeah i would appreciate triage rights
15:50:53 <ErCiccione[m]> also, i'll write a post on the meta issue soon, but at this point i'm in favor of moving monero-site back to github
15:55:55 <fluffypony> ok cool
15:58:57 <selsta> fluffypony: selsta
15:59:09 <fluffypony> lol I should've guessed
15:59:40 <selsta> I think other repos should think about who wants triage rights and give you a list
15:59:44 <fluffypony> agreed
16:00:00 <selsta> the meta repo needs someone that closes outdated issues
16:00:06 <fluffypony> ErCiccione[m] / xiphon / dEBRUYNE: please confirm your GitHub usernames
16:00:15 <ErCiccione[m]> maybe it's enough to get the list from the issue bot
16:00:35 <ErCiccione[m]> fluffypony: erciccione
16:01:07 <selsta> ok ty
16:01:11 * selsta happy
16:04:31 <ErCiccione[m]> now that the monero-project is an actual project i have some suggestions that i think would be cool to implement. Like teams and public members. Should make easier to organzie things. Will write in the meta post when i have time
16:04:54 <omartijn> Does anyone have an overview of what is still required when it comes to zmq? I was looking at https://forum.getmonero.org/9/work-in-progress/2564/0mq-by-tewinget and the activity on it (https://github.com/tewinget/bitmonero/commits/zmq-dev), and it doesn't look like that was merged.
16:05:09 <selsta> ErCiccione[m]: we disabled public members intentionally
16:05:35 <selsta> also not aware of any teams functionality
16:05:37 <omartijn> I do see a few zmq commits in master though, there seems to be a ZmqRpcServer, but I didn't see quickly whether the wallet already uses it
16:05:46 <ErCiccione[m]> Why selsta?
16:05:54 <selsta> omartijn: vtnerd is working on it
16:05:55 <moneromooo> vtnerd added zmq (not sure whether htat was on top of tewinget's code or not). AFAIK it's still not got pub/sub.
16:06:32 <selsta> ErCiccione[m]: let’s move to #monero-community
16:06:52 <ErCiccione[m]> teams functionality -> they can be useful to set up teams to work on something. Bisq uses those and i think they work quite well, with the ability to ping an entire team if you nead a review. I haven't looked it up recently, but i think it would work the same way
16:07:01 <ErCiccione[m]> Ok
17:30:46 <dEBRUYNE> fluffypony: dEBRUYNE-1 on Github
18:36:41 <Snipa> ErCiccione[m] - Backlog is due to life roaring to life around me over the last week, and pushing to finish the GUI builds.  Those are going into final testing over the next day or two (Pending final packaging), then I'll be back to reviewing merge requests. dEBRUYNE has been maintaining a list for me, I just haven't had a chance to check it. :)
18:56:37 <objectorange> Is censorship-resistance important to the Monero community?
18:56:54 <gingeropolous> yes
18:57:51 <objectorange> Has anyone reviewed 1M5.io to assist in this?
19:03:46 <objectorange> I'm looking into integrating it as a 3rd tx proxy option so it can be tested against censorship attempts.
19:09:53 <objectorange> Not having a strong background in Monero, I was told this is the place to find it.
19:11:20 <ErCiccione[m]> thanks for the clarification snipa :)
19:11:53 <ErCiccione[m]> objectorange is referring to https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/127
19:12:13 <Snipa> Yup yup.  I got the OSX builds done last night for the first time after a bit longer of a fight, but that's the last one to test once I push it to selsta after I get home today, then it's packing, release, and back to merges for me. :)
19:12:26 <ErCiccione[m]> i suggested him to discuss here his idea of integrating 1M5 to Monero
19:13:01 <ErCiccione[m]> Snipa: Cool. Do you plan to merge dandelion++ already or we are waiting on more reviews?
19:13:41 <Snipa> I don't think I've taken a particularly close look at that one yet, I feel like I eyeballed it, but wasn't fully comfortable with my own understanding when I looked it over.
19:15:06 <ErCiccione[m]> Yeah don't rush it, it's an important feature. Maybe would be better to test it on testnet a bit first
19:15:48 <Snipa> My general rule of thumb is I need to at least generally understand what's going on before I push the button
19:25:42 <ErCiccione[m]> objectorange: My suggestion is to give an overview of what 1m5 is and what benefits would bring to Monero. I don't know how many here are familiar with the project (i'm definitely not)
19:37:10 <asymptotically> Snipa: understanding things before you introduce them into a billion dollar cryptocurrency? that's insane!
19:37:16 <asymptotically> less reviewy more pushy new features!
19:37:44 <gingeropolous> its ok, if it breaks we'll just turn the network off
19:38:18 <asymptotically> yeah you can just take all of the coins and then give them back after people provide KYC info and proof of purchase. it's the modern way
19:38:32 <gingeropolous> thats what decentralized means, right?
19:39:32 <gingeropolous> regarding dandelion++, i was debating if we should setup another subnet thing like I tried to do for flufflyblocks
19:39:47 <gingeropolous> the problem is that you need transactions originating from within the subnet to try and break out into mainnet
19:40:06 <objectorange> 1M5 provides routing around blocks using multiple anonymity networks. When TOR gets blocked, it uses I2P. When I2P gets blocked, it uses TOR. When both are blocked, it can use Bluetooth to hop out until someone with an unblocked TOR/I2P is found to fulfill it. WiFi-Direct, a Full-Spectrum Radio service, and LiFi (Light Fidelity) are being worked on to expand the support.
19:40:32 <gingeropolous> i guess we could try and enlist remote node operators to modify their daemons to only work within a subnet
19:40:46 <gingeropolous> that would force a lot of transactions to be routed through dandelion++
19:41:00 <objectorange> End users can stipulate under what threat they are so that some networks will not be used if under a more serious threat.
19:43:24 <objectorange> For example, Monero is made illegal in Russia and Snowden, who loves Monero (don't know if that's true), wishes to continue using Monero, but doesn't want to give the Russians a reason for kicking him out. So he sets the system to a level that ensures all Monero transactions go out over LiFi, the P2P Full Spectrum Radio sensor, Bluetooth, not TOR or I2P to ensure his IP is not associated with Monero.
19:43:40 <moneromooo> objectorange: sounds like you should talk to anonimal, who's working on a layer that "drives" several networks like tor, ip2, etc.
19:44:33 <moneromooo> Some mesh networking thing to go with it would seem like a good thing.
19:44:48 <objectorange> yeah, if we could integrate his work into it that would be terrific too.
19:45:00 <objectorange> The more options the better I believe.
19:45:14 <objectorange> Basically one big intelligent mesh.
19:45:38 <moneromooo> The advantage of something like sekreta is that monero doesn't have to care about adding support for every overlay network under the sun. Leave that to some layer of abstraction.
19:45:40 <objectorange> TOR and I2P currently work within 1M5.
19:45:59 <moneromooo> And your system sounds like it's working on a similar layer.
19:46:01 <objectorange> Bluetooth is working under discovery, but not yet for sending messages.
19:46:24 <kinghat> librecast/multicast looks awesome as well
19:47:15 <objectorange> networks can be selected
19:48:10 <objectorange> having a dedicated group on the censorship resistance front I belive is going to become very important. This isn't just a Monero thing, but a free speech thing.
19:48:33 <objectorange> ...with the support of the decentralization/p2p community.
19:48:39 <objectorange> as a whole
19:53:58 <objectorange> haven't checked out librecast yet
19:54:21 <objectorange> monero uses multi-casting for transaction propagation correct?
19:55:17 <moneromooo> There's no multicast on IPv4 WAN. Or at least wasn't, though I doubt this changed.
19:55:47 <moneromooo> I find myself unsure about IPv6.
20:13:45 <objectorange> maybe anycast?
20:16:07 <objectorange> my background isn't in networking, so I want to be sure I understand how Monero propagates transactions
20:16:59 <objectorange> I would think multicast would be ideal for cryptocurrencies but unsure the level of support available
20:17:32 <objectorange> Or anycast + relay
20:28:31 <objectorange> Or does each Monero node maintain an addressbook of all Monero nodes?
20:28:43 <objectorange> And just push to each?
20:30:21 <gingeropolous> afaik, u maintain 8 peers and transmit everything to each peer, and listen on all peers etc
20:33:40 <objectorange> ah, yes, I believe Bitcoin works the same no?
20:34:07 <objectorange> Here's an interesting link about someone pushing a new method...Erlay.
20:34:08 <objectorange> https://medium.com/@SDWouters/erlay-an-awesome-performance-improvement-to-the-bitcoin-network-f59d757b2d14
20:42:19 <objectorange> So when using TOR and I2P as proxies, does Monero push a copy of each transaction to each of the 8 nodes through both TOR and I2P?
20:42:53 <objectorange> ...and the clearnet too?
20:43:06 <objectorange> for a potential of 3 copies going to each node?
20:43:17 <objectorange> And then they just drop copies?
20:43:52 <objectorange> perhaps for now while it's still experimental?
20:44:06 <gingeropolous> no idea
20:44:25 <objectorange> probably need to get anonimal on here
20:44:55 <objectorange> or does he hang out somewhere else?
20:45:02 <objectorange> (or she)
20:45:14 <objectorange> (or they) :)
20:46:19 <gingeropolous> theres #sekreta and #sekreta-dev
21:35:19 <moneromooo> Different sockets, tx pushed N times.
23:55:04 <objectorange> spoke with anonimal and it seems kovri was integrated with monero independently and sekreta in another integration yet both are awaiting pulls? are they just awaiting the next version or are they on hold?
23:56:06 <anonimal> single pull request, separate libraries, unified interface.