TZUTC: -0500
MSGID: 2321.ipv6@1:2320/105 2ce39860
REPLY: 1714.fido_ipv6@1:135/115 2ce23a84
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
FORMAT: flowed
> In reality, IPv4 *continues* to work just fine, and will for a long time
> to come.  In a couple of generations there may be a need for a
> "changeover", but there is no emergency pending.  It reminds me of the
> frenzy over the Y2K "issue", which turned out to be largely.... hype.

While I agree the Y2K issue was overhyped, part of the reason it turned out
to be largely hype was because a whole lot of folks spent a lot of time
figuring out and updating their systems to prevent it from being worse.

I should probably try to move this side discussion to a more appropriate
echo, but I am not sure what that would be.  The Y2K echo is long gone. ;)

Mike


 * SLMR 2.1a * "The Metric System is the tool of the Devil!" - Granpa S
--- SBBSecho 3.28-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 10/0 1 103/705 104/117 119 105/81 106/201 114/10 124/5016
SEEN-BY: 128/187 129/14 153/757 7715 154/10 30 50 110 700 203/0 214/22
SEEN-BY: 218/0 1 215 610 620 700 860 220/20 30 221/0 6 226/18 30 44
SEEN-BY: 226/50 227/114 229/110 206 317 400 426 428 550 616 664 700
SEEN-BY: 229/705 240/1120 5832 263/1 266/512 280/464 5003 5006 5555
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 423/120 460/58 467/888 633/280 712/848
SEEN-BY: 770/1 902/26 2320/0 105 304 5020/400 545
PATH: 2320/105 154/10 280/464 103/705 218/700 229/426