19:00:12 <laanwj> #startmeeting 19:00:12 <core-meetingbot`> Meeting started Thu Feb 17 19:00:11 2022 UTC. The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 19:00:12 <core-meetingbot`> Available commands: action commands idea info link nick 19:00:18 <sipa> hi 19:00:22 <hebasto> hi 19:00:23 <achow101> hi 19:00:24 <laanwj> #bitcoin -core-dev Meeting: achow101 _aj_ amiti ariard BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj larryruane lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball 19:00:26 <laanwj> morcos nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild 19:00:27 <fjahr> hi 19:00:33 <jonatack> hi 19:00:33 <Murch> hi 19:00:38 <cfields> hi 19:00:48 <laanwj> welcome to the weekly general bitcoin-core meeting, there have been no proposed topics for this week, any last minute ones? 19:01:07 <b10c> hi 19:01:35 <lightlike> hi 19:01:53 <MarcoFalke> ahoi 19:02:03 <warren> hi 19:02:56 <jonatack> Murch: sendall is shorter, too! 19:03:16 <laanwj> #topic 23.0 milestone 19:03:16 <core-meetingbot`> topic: 23.0 milestone 19:03:56 <laanwj> we've passed the 23.0 feature freeze and strings freeze, and are now in the last bit before the branch-off 19:04:23 <larryruane> hi 19:04:50 <laanwj> from now to the branch we'll merge only bugfixes, so going over high priority for review doesn't make sense at the moment 19:05:00 <laanwj> what we could do is look at the milestone of course https://github.com/bitcoin/bitcoin/milestone/52 19:05:24 <laanwj> let me know if anything should be added, or is unlikely to make 23.0 and should be removed 19:05:30 <hebasto> do we have any progress in #15774 ? 19:05:31 <gribble> https://github.com/bitcoin/bitcoin/issues/15774 | macOS App Notarization ÷ Issue #15774 ÷ bitcoin/bitcoin ÷ GitHub 19:05:39 <achow101> Can #24365 be added? It is a bug fix for a crashing issue 19:05:40 <gribble> https://github.com/bitcoin/bitcoin/issues/24365 | wallet: Dont generate keys for wallets with private keys disabled during upgradewallet by achow101 ÷ Pull Request #24365 ÷ bitcoin/bitcoin ÷ GitHub 19:06:26 <laanwj> achow101: it's already added 19:06:29 <MarcoFalke> added 19:07:45 <laanwj> hebasto: i don't know 19:08:27 <jonatack> have a couple of doc improvements that might be nice ( they may not need to be tagged if doc improvements can be merged anytime) 19:08:41 <laanwj> hebasto: it was brought up last week though, fairly sure fanquake is working on it 19:09:18 <hebasto> laanwj: ok 19:09:20 <laanwj> jonatack: yeah, i think we can just merge those when they're ready 19:09:25 <fanquake> yes, have been looking at that 19:10:03 <hebasto> fanquake: is there a chance for 23.0 to be notarized? 19:11:01 <achow101> I think notarization will also require some changes to signapple so it may take some time for me to work that out too 19:11:19 <fanquake> yes I think we should be able to work it out for 23.0 19:12:10 <laanwj> great 19:12:17 <luke-jr> I thought we were intentionally not notarising? 19:12:21 <laanwj> let's leave that on the milestone then 19:12:55 <hebasto> luke-jr: could you remind reasons for that? 19:13:44 <luke-jr> hebasto: IIRC it pinged Apple every time a user launches it? 19:14:15 <hebasto> yeap, it does, at least once 19:14:42 <laanwj> as i understand it it does that for every binary that is launched the first time 19:14:52 <luke-jr> so my understanding was that we intentionally didn't want that, for user privacy 19:15:05 <laanwj> see e.g. the link in that issue https://sigpipe.macromates.com/2020/macos-catalina-slow-by-design/ 19:16:01 <luke-jr> laanwj: but notarisation IIRC did extra pinging stuff? 19:16:07 <hebasto> can we be sure that it does not ping Apple for non-notarized app? 19:16:17 <luke-jr> idk, don't really follow macOS stuff closely - but if this is going to change, probably someone should look into it 19:16:48 <sipa> Based on https://sigpipe.macromates.com/2020/macos-catalina-slow-by-design/ I'd think it runs for every program, notarized or not. 19:17:04 <sipa> If it's even the case for shell scripts you write yourself. 19:17:05 <laanwj> i think attaching the notarization to the application can save a ping, not sure though 19:17:24 <hebasto> whatever we find out we cannot rely on it, as apple can change things anytime 19:17:43 <laanwj> that's for sure 19:17:46 <luke-jr> hebasto: sure, but we can refuse to actively participate in privacy-violating stuff 19:17:59 <laanwj> always fun what new hoops they come up for software developers 19:18:32 <fanquake> at some point itâÂÂs either we fulfil the requirements or stop supporting macOS 19:18:47 <fanquake> users are reporting their bitcoin core apps just flat out disappearing 19:18:54 <luke-jr> fanquake: sure, but it's a different scenario if we're forced to do it, vs voluntarily enabling it 19:18:58 <luke-jr> :| 19:18:59 <MarcoFalke> I think you can already assume your privacy compromised by apple if you are using apple products 19:19:14 <warren> their data remains intact though right? 19:19:15 <hebasto> for now we have multiple claims that macos removes Bitcoin Core; assuming it could be related to lack of notarization 19:19:22 <laanwj> if they really ping their server for every binary that is launched for the first time i think that's right 19:20:15 <luke-jr> might be nice to investigate a disappeared-Bitcoin system and see if the logs say why 19:20:24 <luke-jr> idk how practical that is 19:21:00 <luke-jr> might also be Apple just trying to force everything to go through their App Store :/ 19:22:51 <laanwj> any other topics? 19:24:33 <laanwj> #endmeeting