Opened at 2021-08-03T16:11:40Z
Last modified at 2021-08-19T14:39:24Z
#3756 new defect
use default wormhole server
| Reported by: | meejah | Owned by: | meejah |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
It seems the default wormhole server is "wormhole.tahoe-lafs.org" but there is nothing running there.
We should use the default magic-wormhole server (ws://relay.magic-wormhole.io:4000/v1) until there's another viable alternative.
Change History (2)
comment:1 Changed at 2021-08-03T18:27:09Z by exarkun
comment:2 Changed at 2021-08-19T14:39:24Z by exarkun
- Owner set to meejah
speculatively re-assigning to meejah who I think can modify tahoe-lafs.org dns.
Note: See
TracTickets for help on using
tickets.
it seems to be a cname for wormhole.leastauthority.com. but the service leastauthority.com operated a wormhole relay for is no longer operating. so quite likely that wormhole relay went away as a result, sometime. I think the original idea for having wormhole.tahoe-lafs.org as a cname for some other server may have been to avoid burning a dependency on a third-party service into all of the distributable tahoe-lafs software in case that third-party service became unusable at some point which now seems to have been a pretty good plan, except perhaps for the part where there was no monitoring system to tell us when that happened (apart from our users). So ... we can change DNS config now right? I suggest making wormhole.tahoe-lafs.org a cname for relay.magic-wormhole.io. Then the issue is fixed without code changes and without having to distribute updates.