| 18 Jan 2026 |
hexa |
Cloudflare does not yet support the ".ci" extension.
| 17:52:25 |
hexa | it is registered at some obscure registrar, because .ci wasn't widespread back then either | 17:52:43 |
hexa | apparently 21 EUR at afriregister.com | 17:54:01 |
hexa | * apparently 21 EUR/yr at afriregister.com | 17:54:10 |
Winter | Oh! | 17:54:14 |
hexa | so by all means, find out if you want the domain, and if graham still wants to give it away | 17:55:31 |
hexa | we can probably do afriregister.com | 17:55:37 |
hexa |
Registration restrictions Name must match official name of company, organization, or trademark
| 17:55:45 |
hexa | 🙂 | 17:55:49 |
hexa | is a reasonable price for a three letter .ci domain imo | 17:57:56 |
hexa | * is a reasonable price for a three letter .ci domain, that fits us so well imo | 17:58:08 |
| 19 Jan 2026 |
vcunat | I'm not too fond of domain hacks, personally (Côte d'Ivoire in this case). | 11:04:21 |
| 25 Jan 2026 |
7c6f434c | Are ofborg builds of «headline» packages of the PRs auto-triggered currently, or no longer (due to load, presumably)? | 19:02:09 |
K900 | They are triggered | 19:02:21 |
K900 | But they may not be executed for a long time | 19:02:27 |
| 26 Jan 2026 |
| Mohamed Hisham Abdelzaher joined the room. | 21:09:28 |
| 27 Jan 2026 |
| mynacol joined the room. | 09:54:43 |
mynacol | Not sure if this is the right place, but I just noticed that the messages.ofborg.org domain provides an invalid certificate when connecting over IPv6. Over IPv4, the right certificate is returned, so Happy Eyeballs clients will fall back to that. See https://v6check.miyuru.lk/#!https://messages.ofborg.org for a test | 09:57:39 |
hexa | not sure it is even used for https | 12:56:15 |
hexa | you are getting the default vhost instead | 12:56:33 |
| 1 Feb 2026 |
| Fernando Rodrigues changed their display name from SigmaSquadron to Fernando Rodrigues. | 10:43:16 |
| 4 Feb 2026 |
| tiferrei joined the room. | 03:07:23 |
| tiferrei left the room. | 12:19:33 |
| 6 Feb 2026 |
mynacol | I looked at the wrong thing, the wrong port number. The website connects to messages.ofborg.org:15673. There, the IPv6 address 2a01:4f8:c012:cda4::1 gives Connection refused, while the IPv4 address 138.199.148.47 returns with valid HTTPS (and valid TLS) stuff.
$ curl 'https://messages.ofborg.org:15673/ws/' -Ss -v -6
* Host messages.ofborg.org:15673 was resolved.
* IPv6: 2a01:4f8:c012:cda4::1
* IPv4: (none)
* Trying [2a01:4f8:c012:cda4::1]:15673...
* connect to 2a01:4f8:c012:cda4::1 port 15673 from [redacted] port 35854 failed: Connection refused
* Failed to connect to messages.ofborg.org port 15673 after 13 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to messages.ofborg.org port 15673 after 13 ms: Could not connect to server
| 14:37:43 |
mynacol | This very much smells like either a firewall rule, or this service is not listening on IPv6 sockets. | 14:38:34 |
hexa | # ss -lpn | grep 15673
tcp LISTEN 0 1024 0.0.0.0:15673 0.0.0.0:* users:(("beam.smp",pid=2507139,fd=53))
| 14:39:49 |
hexa | redeploying with web_stomp.ssl.ip set to :: | 14:50:14 |
hexa | # ss -lpn | grep 15673
tcp LISTEN 0 1024 *:15673 *:* users:(("beam.smp",pid=3905929,fd=53))
| 14:52:26 |
mynacol | Nice! Now my curl test as well as Firefox successfully work over IPv6 | 14:54:45 |
mynacol | * Nice! Now my curl test as well as Firefox successfully work over IPv6 (and IPv4) | 14:55:03 |