Uh oh!
There was an error while loading. Please reload this page.
chore(keys): remove the retired AWS gateway from the index - #170
Merged
Conversation
The AWS gateway is being shut down. It was kept listed by bare IP through the changeover so no peer lost a bootstrap target while adoption of gw1/gw2 happened; that is now complete — gw1 and gw2 are carrying 170 and 147 peers respectively, comparable shares of the live network. The release path stopped touching that host in freenet-core#5540, so nothing in a release run reaches for it any more. Peers re-fetch this file at startup. One holding a stale copy will dial the AWS address until it refetches; that entry stays live until the gateway is actually stopped, and the two nova entries work throughout, so there is no window where a peer has no usable gateway. Claude-Session: https://claude.ai/code/session_01SvxFMoTCSqeqyMc8VmpKDZ
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The AWS gateway is being shut down to cut ~$198/mo. It was deliberately kept listed by bare IP through the changeover so no peer lost a bootstrap target while
gw1/gw2.freenet.orgadoption happened.That adoption is now complete: gw1 has 170 peers and gw2 has 147 — comparable shares of the live network, where gw2 started from zero on 2026-08-29.
Approach
Drop the AWS entry, leaving the two role-based nova gateways.
The release path stopped touching that host in freenet-core#5540, so nothing in a release run reaches for it any more.
Rollout
Peers re-fetch this file at startup. One holding a stale copy will dial the AWS address until it refetches — and that gateway stays running until this has propagated, so the dial still succeeds. The two nova entries work throughout. There is no window where a peer has no usable gateway.
Order from here: this merges and deploys → the AWS gateway and gkapi stop → the instance is terminated separately, by hand.
[AI-assisted - Claude]