Monero Dev Meeting Note Highlights – 2019-07-28
Logs
351 lines
rehrarAlright, it's time to start ladies and gentlemen.
rehrar1. Greetings
rehrarAnybody out there?
rbrunnerNope. All people on holiday.
rbrunner
vtnerd__yes
rehrarwell, the three of us can have a grant ol time then
rehrarjust pinging hyc moneromooo dsc_ selsta and dEBRUYNE also
rehrarmaybe a luigi1111 and fluffypony in the mix too, who knows
rehrareither way
rehrar2. What's been completed since last meeting?
dsc_dont ping me broooo
rehrar_csd
rehrarthere, I took it back
dEBRUYNECLI v0.14.1.2 has been released
dEBRUYNEWhich is mostly bug fixes I guess
dEBRUYNEmooo is holding a vacation, but he provided me a list of stuff that is ready to be merged
dEBRUYNESo I am working with luigi to get the merge queue relatively empty
kinghat🙏
rehrarah, did not know mooo was on vacation
rehrarI hope he ignores my ping then. Sorry!
dEBRUYNEFor the GUI, we tagged 0.14.1.2 and we're waiting on pony to finish the builds
dsc_I'm more than half way into integrating i2p-zero and tor into GUI
dEBRUYNEMain new feature is optimized Tails support
dEBRUYNEPerhaps dsc_ can share a bit more detail
dsc_Sure thing.
rehrardsc_: that's actually super exciting
dsc_So Tails integration is a collection of improvements that improve user experience for our Tails users
dsc_You would be suprised how big the audience is there
dsc_So, starting from 0.14.1.2 it will be very easy to use GUI on Tails
dsc_As for i2p-zero, I need a couple of days then that's done too
dsc_I suggest to package i2p-zero with the GUI release
dsc_Which can pose problems for our reproducible build efforts
dEBRUYNEI don't see much harm in packaging it with the GUI, especially if the user first has to check a checkbox to turn it on
dsc_but that's a problem for later
dsc_That also
rbrunnerShouldn't the CLI pack it also then?
dEBRUYNEI think most CLI users are able to download the package themselves
dEBRUYNEAnd get it running (especially given the instructions present on Github)
dEBRUYNEBy contrast, GUI users need a checkbox and not tons of steps
rbrunnerOk, makes sense, more or less …
dsc_The fact we package i2p-zero is a convienence feature. I'm also 'integrating' support for Tor but we wont be packaging that. That's basically running Tor and using socks proxy at :9050
rehrarwe GUI people are scrubs
xmrmatterbridge<xmr-romine> is there already some doc about running monerod over tor ?
dEBRUYNEhttps://github.com/monero-project/monero/blob/master/ANONYMITY_NETWORKS.md & https://github.com/monero-project/monero#using-tor
xmrmatterbridge<xmr-romine> thanks guys
rehrarhyc any update on randomx audit?
rehrarThe last one?
dsc_One more thing regarding i2p-zero.. It can take up to 1-2 minute(s) for the local socks proxy to become 'active' which means, if the user has i2p-zero enabled and starts up the GUI to create a quick tx … might have to wait a minute or two
dsc_This is related to how i2p-zero works
dsc_so beware of that limitation
rbrunnerSo it's i2p-two, from "two minutes"?
kinghatcan it check if i2p is currently running?
dsc_rbrunner: haha
rehrarit's how i2p works in general, no? Getting bootstrapped into the network, I mean.
dsc_rehrar: most likely
dsc_kinghat: it can
rehrarunder bad circumstances it can take even longer
rehrarI wonder if there can be some kind of notification to let users know this
vtnerd__tor should have similar issue iirc, building circuits isn't immediate
kinghatalso, are we still going to do the beta builds for the gui?
dsc_vtnerd__: Sure, but not 1-2 minutes?
dsc_kinghat: yes
kinghat👌
vtnerd__I think it might be longer than that, at least it seemed like forever yesterday when I was testing
vtnerd__actually no, I've run tails once before, it takes some amount of minutes, just don't remember the exact time frame
dsc_vtnerd__:
dsc_$ time (sudo service tor restart && sleep 2 && torify curl icanhazip.com)
dsc_171.25.193.77
dsc_real0m2.759s
vtnerd__if your not using outbound connections tor destroys the circuits and goes into an idle mode too, which isn't a problem if "noise" is enabled (because its always sending)
rehrarthere goes dsc_ bragging about his internet again
dsc_yes, my internet.
vtnerd__it keeps state in a file that it might re-use, so you'd have to a cold restart
dsc_vtnerd__: fair enough
rehraralright, anything else?
dEBRUYNEvtnerd__: I was wondering if you intend to pick this up somewhere in the future? https://github.com/monero-project/monero/pull/2317
vtnerd__this one and the next one after that PR is a bit rough because its x86 ASM
rehrarthat was a hilarious conversation to witness
rehrarperson 1: i was wondering if git link
rehrarperson 2: Well you see it's like git link
dEBRUYNEThanks
vtnerd__Im also not certain that having a separate repo for this is beneficial, but I guess some other project could make use of the custom hooks
vtnerd__my original code should need some re-working since the device/ledger stuff got slammed in, but I look at recently and I think its possible to rebase/update that without crying
vtnerd__Im also not certain whether that supercop repo should be an external git thing, or something that you manually have to do
vtnerd__I'm thinking the latter, since people are blasted without another submodule
vtnerd__*are not
dEBRUYNEI see, seems like a thing that warrants more in depth discussion in a future dev meeting
rehrarWith more attendees?
rehrarserious question
rbrunnerAnd maybe some more background info to prepare
rehrarwho should be present for such a discussion?
rehrarwe can add it to next meeting as an item and try to ping the people to be there
vtnerd__the background is either the supercop code goes as a submodule and it must be synced by every person
vtnerd__or only those that which to accelerate wallet scanning drop the repo into a folder and toggle a cmake bit
rbrunnerSo that's not something for the normal, general release then?
vtnerd__its not needed for testing, unless you need to test the feature specifically
vtnerd__no, likely it would be in the normal general release, but I suppose it doesn't have to be
vtnerd__this came up because ryo recently added support for basically the same thing, and it should cut wallet-scanning time in half
vtnerd__although its probably dependent on your HD speeds too
rehraralright, any more discussion on this?
hycre: randomx audit, Quarkslab are finalizing their report, said we may get it by middle of next week
rehrarnice!
rehrardoes anyone have anything else that they want to discuss?
hycsince they've been opening github issues as they arose, there's not likely to be anything in the report we haven't already seen
ErCiccioneGitHub is starting to censor people coming from countries under US sanctions, we should definitely migrate away
ErCiccionei don't know how the core team feel about it
rehrardo people here have any thoughts about the Github/Gitlab thing, especially in light of the recent Github things?
vtnerd__those countries listed probably require some vpn/tor/i2p opsec to contribute anyway … ? I'm certainly not attempting to stop a switch to a self-hosted gitlab, but meh
rbrunnerIf such a switch was so easy it would probably have happened already, I think, after the Microsoft acquisition …
vtnerd__or maybe not, but they would have to after that hammer that was thrown
rbrunnerWith all submodules still on GitHub, for example
vtnerd__the support team for the gitlab instance are probably the most relevant for this
ErCiccionerbrunner: the point was to test monero-site on the self-hosted gitlab first, and then see what to do with the other repos. But has been almost an year now
hycI've always favored moving to self-hosted gitlab and away from github
rbrunnerYeah, I remember. But I think the site is a particularly simple case
vtnerd__I mean most devs should have a copy of the code and history luckily, but its the discussions that can get purged if not backed up properly
hycbut this particular issue only affected private, paid github accts
hyc(i.e., github closing off accts from sanctioned countries)
ErCiccionehyc: i guess that depends by how they are forced to enforce the sanctions
hycthey're splitting some hairs I guess. trade sanctions only affect commerce. if you paid for a private acct, you're affected.
rbrunnerHas any other notable cryptocurrency team already made such a switch?
hycif you're on a public/free acct, you're not affected
rehrarrbrunner: define notable?
rbrunnerI mean, some "interesting" team. Top 100 coin, maybe? Sizeable community, I mean
ErCiccionethanks for the links. it's still a very precarious situation.
ErCiccionerbrunner: sia
rbrunnerAnd complexity of the code
hycErCiccione: agreed. as I already said, I'm in favor of moving off.
kinghati think ppl are worried about contributions after moving off github. i dont think it would make a difference.
hycagain, just my perspective: the OpenLDAP Project maintains our own repo. we only mirror to github, because it seems you're not a real project these days if you're not on github
hycout github mirror is read-only
hycour*
ErCiccionekinghat: i agree.
dsc_I keep repeating myself but I question people whose first thought is 'gitlab' when thinking of a git alternative
dsc_There is more! Noooo.. Yes!!
dsc_Consider it…
hycgitea?
dsc_for example, yep
hycI don't really care which alternative is used. all I care is self-hosted.
ErCiccioneiirc gitea was considered
hycyou could make an argument that being off github adds a barrier to entry - people don't like having to create accounts just to interact with another project
rehrarIn favor of gitea
dsc_Even more so when considered gitlab is a company, enterprise, they have funding, maybe they have shareholders - and capitalism is evil. Therefor, gitea
rehrarhyc which is why I am arguing for a federated git ecosystem
rehraropen issues on another git based project management site from yours, etc
ErCiccionelet's not forget that we already have half repos on github and half on gitlab. That's not ideal
hycrehrar: agree, federated identity would be preferable
rehrarlet's build it
rehrarwe can have it out by Wednesday at the latest
hyc+1
dsc_ok sounds good
ErCiccionei want 2
rehrarthat'll take an extra day
hycthis could be a long conversation, but totally - we need to rethink the notion of accounts and identities
rehrarBut for reals though this is an ongoing discussion and…
rehrar^ hyc
rehrarwe have the issue open about this that ErCiccione
rehraralthough that one is about moving to gitlab, I think
rehrarso maybe another one can be opened for discussion on which platform?
dsc_+1 for centralized authentication service
dsc_(hosted by monero)
rbrunnerOh the added complexity
dsc_rbrunner: for whom?
rbrunnerThe system in general, I mean.
dsc_It could simplify things
hycnot quite centralized authent. just public key based.
rbrunnerSomething more that can go wrong
ErCiccionerehrar it is yes, as hyc says for me the important is to move away from a centralized place. I think gitlab is the best choice because we have been testing it for an year, but sure let's discuss alternatives
hycwe could use monero wallet addresses as our identities
rehrarhyc I've been thinking of using Monero signatures as password alternatives
dsc_thats a cool idea
rehrarpublic key as ID
rehrarsignature from private key as password
kinghatdoes that work with subaddys or am i missing something?
rehrarbut then losing your seed is even a bigger deal
rehraror getting it stolen
hycgood point
rehraras long as there are standard ways of resetting or something
rehrarit's no more annoying than losing or getting your regular password stolen
hychaving a reset facility implies a centralized admin authority
dsc_Call the Monero helpdesk and provide them your miaden name, your first car brand and your date of birth
hyc^
rehrarenforced 2/3 MFA then
hycshould we wrap up the mtg before continiung this conv?
rehrarbut yeah, we'll call it here
rehrarunless anyone has any last minute things?
vtnerd__I hope to finally issuing some PRs related to the i2p/tor white noise stuff, took some time to architect this bt hopefully. nothing else needs to be reported by that really other than look for more stuff to review
rehrarcool deal!
rehrarwell everyone, thanks for making the time today.
rehrarYou're all free to disperse. Coffee on the little table outside the meeting room.
Sources and notes
- Meeting log: Overview and Logs for the Dev Meeting Held on 2019-07-28, getmonero.org. The official post carried the raw log and pointed readers to Hello Monero for the overview.
- Original Hello Monero URL slug recovered from the Wayback Machine index; the original page content did not survive, so this reconstruction carries the log as archived by the Monero Project.