@obsidian @GrapheneOS did my reply not make it?
We can be a mirror, but not a primary part of their internal infrastructure. They need to be running a load balancer like mirrorbits for us to shave traffic off their main servers.
If the traffic levels are high enough and they're good about archiving past releases, MicroMirror would also be able to help, but at least mirror.fcix.net would be possible
@corvus_ch @GrapheneOS can someone from Graphene team reach out via the contact form on my website Openfactory.net please do I can write back, don't want to publish the email here in case bots scrape it ;)
But I can surely do sth and also reach out for sponsors of bandwidth in the social network. This is doable!
@GrapheneOS
If the deal is very good it may make sense, but coming from the CDN sector, I'd say that a hosting operation that can't provide v6 _at all_ in 2025 is either suffering from worrying levels of technical debt or other serious organizational issues.
Personally, I would at least avoid committing to anything beyond a monthly contract before evaluating whether they can reliably deliver promised capacity even with legacy IP.
@bl4x1 There are signatures verified by the update client and it makes sure the new version is equal or greater than the previous version. Install process has firmware verification built-in and has people check OS verified boot key post-install. CLI install has users verify the install zip.
Our app repo has all the metadata signed including what's in which release channel. OS updates themselves are signed but we plan to sign release channel metadata for them as an extra layer of protection.