10:06:04 <sech1> How exactly does auto updater work? It just checks for new hashes, downloads them and shows a folder with downloaded file, so use has to explicitly run it?
10:06:11 <sech1> *user
10:11:44 <plowsof11> will confirm the ux but there are some more verification steps selsta ^ 
10:13:12 <sech1> I only found SHA256 checks in the code
10:14:35 <sech1> and no GPG keys check
10:19:16 <sech1> although hacking this update way will require hacking both getmonero and moneropulse domains
10:19:27 <sech1> so it's relatively safe
10:22:31 <sech1> Actually I was checking how P2Pool would update. As long as user has to run actual installer, it's fine.
10:23:55 <plowsof11> i must be getting confused with github workflow things. i currently have 17.3.2 , fully synced, eagerly waiting for an update prompt 
10:27:10 <sech1> moneropulse is not updated yet, you should get an update window when it does
10:27:34 <sech1> also, 0.17.x.x is outdated since August
10:29:42 <plowsof11> ah yes, i just wanted to experience an update, but the prompt hasn't appeared yet
10:44:25 <plowsof11> now im wondering also how p2pool would update 
10:50:31 <sech1> GUI installer just wipes p2pool folder and then the new GUI downloads new p2pool when needed
10:52:24 <plowsof11> ah thanks, makes sense, then "isInstalled" wont see it -> download p2pool fresh 
11:47:53 <lanmman> hello
12:16:05 <lanmman> is possible to use both "QT_AUTO_SCREEN_SCALE_FACTOR"   " QT_SCALE_FACTOR"   or will be one-cancels-the-other (OCO)
12:40:27 <lanmman> i c that QT_AUTO_SCREEN_SCALE_FACTOR" is a replace for QT_ENABLE_HIGHDPI_SCALING
13:02:44 <ofrnxmr[m]> You could have trued and let us know by now
14:25:25 <plowsof11> Afaik the gui on android isnt officially supoorted. ^^^ lanmman is our head android dev/qa tester
14:25:57 <ofrnxmr[m]> And malinero
15:34:53 <selsta> sech1: GUI auto updater does check GPG
15:36:59 <selsta> it even requires the signature from 2 separate core team members
15:39:10 <sech1> src/qt/updater.cpp?
15:39:21 <sech1> it has 3 maintainers and checks for only 1 valid signature
15:40:33 <sech1> or maybe I'm reading the code wrong
15:40:38 <sech1> yes, it checks for 2 signers