Skip to content

Introduce Asian directory server in code#3697

Open
ann0see wants to merge 1 commit into
jamulussoftware:mainfrom
ann0see:directoryAsia
Open

Introduce Asian directory server in code#3697
ann0see wants to merge 1 commit into
jamulussoftware:mainfrom
ann0see:directoryAsia

Conversation

@ann0see
Copy link
Copy Markdown
Member

@ann0see ann0see commented May 18, 2026

Short description of changes

For geo-redundancy, latency and since Any Genre 3 is not heavily used, we introduce a directory in Asia. See
#3692

CHANGELOG: Introduce Directory Server in Asia. This replaces Any Genre 3. Asian/Australian users should from now on use Any Genre Asia.

Context: Fixes an issue?

Does this change need documentation? What needs to be documented and how?

Fixes: #3692

Status of this Pull Request

Ready for review

What is missing until this pull request can be merged?

Review

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I tested my code and it does what I want
  • My code follows the style guide
  • I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
  • I've filled all the content above

For geo redundancy, latency and since Any Genre 3 is not heavily used,
we introduce a directory in Asia. See
jamulussoftware#3692
@ann0see ann0see added this to the Release 4.0.0 milestone May 18, 2026
@ann0see ann0see added this to Tracking May 18, 2026
@github-project-automation github-project-automation Bot moved this to Triage in Tracking May 18, 2026
@ann0see
Copy link
Copy Markdown
Member Author

ann0see commented May 18, 2026

Any Genre Asia shows up correctly in the client and server instead of Any Genre 3

@ann0see ann0see requested review from corrados, pljones and softins May 18, 2026 19:11
@ann0see ann0see moved this from Triage to Waiting on Team in Tracking May 18, 2026
@ann0see
Copy link
Copy Markdown
Member Author

ann0see commented May 18, 2026

@corrados We've now moved Any Genre 3 to Any Genre Asia hosted by @dtinth We believe it's safe to shut down Any Genre 3 directory on your end.

Comment thread src/util.cpp
case AT_ANY_GENRE2:
return CENTSERV_ANY_GENRE2;
case AT_ANY_GENRE3:
return CENTSERV_ANY_GENRE3;
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably rather not name it CENTSERV anymore...

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I was going to say - separate PR to move to DIRECTORY_ and .app in one go?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could do this yes. But .app didn't resolve for me yet. @gilgongo

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, looking at the Cloudflare config- I'd forgotten that it works using 301 redirects. For some reason I thought it had some DNS wildcard capability. So no .app for directories right now I'm afraid.

Copy link
Copy Markdown
Member

@gilgongo gilgongo May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I was going to say - separate PR to move to DIRECTORY_ and .app in one go?

I suppose we could replicate the .io zone to .app and maintain both in parallel? We don't make changes that often after all. As far as I can tell, CloudFlare don't allow pointing two domains to the same zone file at least.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. .app should be the base and all .io records should cname to .app (minus MX records probably). That's the easiest config. Moreover I'd prefer not using cloudflare as proxy. GitHub is already DDOS etc protected I'd assume.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK sure. I'll see if I can set up .app with the same host names as .io. Then when that's done we can CNAME all the the .io hosts to those. Might mean some slight downtime on the website cert while that gets re-generated perhaps (or some other hidden issue crops up).

BTW we don't use the CF proxy for .io - in fact we found out we can't with GitHub Pages as it breaks their cert renewal. The proxy is only for .app at the moment so that it can do the http redirects I think.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, looking at the Cloudflare config- I'd forgotten that it works using 301 redirects. For some reason I thought it had some DNS wildcard capability. So no .app for directories right now I'm afraid.

301 redirects are a HTTP-only concept, and don't apply when just resolving names in DNS. We can do all we need using CNAMEs or parallel A records (and AAAA when we're ready).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Waiting on Team

Development

Successfully merging this pull request may close these issues.

Introduce new Asian directory server

4 participants