How's 3.17 looking? A few weeks back there was some discussion that people were still shaking out bugs, I'm wondering if it's worth upgrading from 3.16 out of CVS from right before 3.17 came out?
How's 3.17 looking? A few weeks back there was some discussion that people were still shaking out bugs, I'm wondering if it's worth upgrading from 3.16 out of CVS from right before 3.17 came out?
IPv6 and TLS are really the only "big" new features so far that I can think of, and TLS with anything except a self-signed certificate isn't easy to set up yet.
For the record. I haven't had a single problem (that I know of) with IPv6 yet, and I've had it tested by others. Thank you, kind sir!
The Synchronet Control Panel absolutely has IPv6 issues, and it's likely that BAJA modules and maybe even JS modules that use IP addresses will also have issues.
I haven't tested the .can support yet with IPv6, so there may be problems there as well (especially since IPv6 addresses are generally not fully specified).
The Synchronet Control Panel absolutely has IPv6 issues, and it's likely that BAJA modules and maybe even JS modules that use IP addresses will also have issues.
I don't use the control panel, and I *think* the only JS module I have that uses IP addresses would be dyndns.js if anything. I don't think I've had any problems with that.
It's one of those not-very-important things we have on our plate... for now, if you want your QWKID.synchro.net host to have an AAAA record, your best bet is to ask Digital Man directly.
Sysop: | Ragnarok |
---|---|
Location: | Dock Sud, Bs As, Argentina |
Users: | 136 |
Nodes: | 10 (0 / 10) |
Uptime: | 33:13:49 |
Calls: | 15,172 |
Calls today: | 1 |
Files: | 19,859 |
D/L today: |
19 files (4,250K bytes) |
Messages: | 1,692,626 |