are we going to be arbitrarily punished for requesting rapid re-deployments of the website now :P

you now have to pay 1 XMR for every re-deployment of the website

(that's a joke)

Lol

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.

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.

*this would leave hashes untouched as a copy of whatever the current head is

we have all historical hashes on github: github.com/monero-project/monero-si…commits/master/downloads/hashes.txt

sech1: Yeah, I pointed that out, BUT monero-site isn't tagged

So you have to lookup the hash for the specific commit you want and grab that.

... 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?

Like that's the mess we're discussing for this to be programmatic.

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.

kayabaNerve might relate to monero-project/monero-site #811 ?

didn't progress on this one but if a particular solution pleases everyone, happy to do

Cool. Exactly what I'm discussing and seems you signed off :D

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

But yeah, will do a pr to resolve that