It's working now. It wasn't working last night. Probably something wrong with the DNS. Thanks!
It should work fine. Perhaps you can share some details regarding the error you're seeing.
If you have access to command-line utilities, such as dig and ping, you could share the output of:
dig spectre.pw
dig @rajeev.ns.cloudflare.com. spectre.pw
ping spectre.pw
ping 172.64.80.1
Alternatively, share what spectre.pw resolves to for you, both with your standard and the official domain's nameserver, and whether you're able to reach its IP address from your network. If not, a traceroute could shed more light.
Maarten Billemont (3df43be6) at 16 Feb 03:12
Resolve a regression preventing user creation.
... and 2 more commits
Maarten Billemont (4bbd2db6) at 17 Jan 22:17
Correctly isolate all Spectre API stateful calls into a Spectre exe...
Maarten Billemont (8588ba2a) at 08 Jan 00:00
Style update.
Maarten Billemont (4b7cc5ce) at 07 Jan 04:46
Correctly isolate all Spectre API stateful calls into a Spectre exe...
... and 2 more commits
Maarten Billemont (e10fe479) at 31 Dec 00:45
Swift Concurrency for Spectre operations.
... and 1 more commit
Looks like this is a duplicate of #34, closing in favor of that.
Maarten Billemont (f7629704) at 07 Jun 18:26
Defer to the OSLogStore for log records.
... and 3 more commits