06:36:35 are we going to be arbitrarily punished for requesting rapid re-deployments of the website now :P 06:37:08 you now have to pay 1 XMR for every re-deployment of the website 06:37:22 (that's a joke) 06:37:29 Lol 09:37:06 my only concern is proper opsec when accessing the hosting server, which comes with a bit of constraints for myself. Otherwise I don't mind. 19:18:51 Would a PR to the site to have hashes-v0.18.0.txt and hashes-v0.18.1.txt be accepted? Basically, ensure easy access to signatures for all currently supported Monero versions. 19:19:14 *this would leave hashes untouched as a copy of whatever the current head is 19:28:36 we have all historical hashes on github: https://github.com/monero-project/monero-site/commits/master/downloads/hashes.txt 19:31:55 sech1: Yeah, I pointed that out, BUT monero-site isn't tagged 19:32:07 So you have to lookup the hash for the specific commit you want and grab that. 19:32:40 ... or clone the repo, run git log on the file, grep for the version you want which isn't 100% guaranteed to work, run a filter pattern, and then use that hashes.txt? 19:32:50 Like that's the mess we're discussing for this to be programmatic. 19:35:02 If it's just under the Monero site, like the actual binaries are, it can be kept solely programmatic over the site. Not programmatic over a version AND a monero-site commit hash. 21:03:42 kayabaNerve might relate to https://github.com/monero-project/monero-site/issues/811 ? 21:06:42 didn't progress on this one but if a particular solution pleases everyone, happy to do 21:10:46 Cool. Exactly what I'm discussing and seems you signed off :D 21:11:32 I was only proposing it for officially supported versions, as I'm not here to discuss archival beyond what git offers, yet modern day access feasibility, which git isn't offering 21:11:39 But yeah, will do a pr to resolve that