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?

*user

will confirm the ux but there are some more verification steps selsta ^

I only found SHA256 checks in the code

and no GPG keys check

although hacking this update way will require hacking both getmonero and moneropulse domains

so it's relatively safe

Actually I was checking how P2Pool would update. As long as user has to run actual installer, it's fine.

i must be getting confused with github workflow things. i currently have 17.3.2 , fully synced, eagerly waiting for an update prompt

moneropulse is not updated yet, you should get an update window when it does

also, 0.17.x.x is outdated since August

ah yes, i just wanted to experience an update, but the prompt hasn't appeared yet

now im wondering also how p2pool would update

GUI installer just wipes p2pool folder and then the new GUI downloads new p2pool when needed

ah thanks, makes sense, then "isInstalled" wont see it -> download p2pool fresh

hello

is possible to use both "QT_AUTO_SCREEN_SCALE_FACTOR"   " QT_SCALE_FACTOR"   or will be one-cancels-the-other (OCO)

i c that QT_AUTO_SCREEN_SCALE_FACTOR" is a replace for QT_ENABLE_HIGHDPI_SCALING

You could have trued and let us know by now

Afaik the gui on android isnt officially supoorted. ^^^ lanmman is our head android dev/qa tester

And malinero

sech1: GUI auto updater does check GPG

it even requires the signature from 2 separate core team members

src/qt/updater.cpp?

it has 3 maintainers and checks for only 1 valid signature

or maybe I'm reading the code wrong

yes, it checks for 2 signers