nostr:npub1mpqz4zlc45a9p5gspy4fgk4fauytl897ktegczu2nq68z60n729sghx8f8 nostr:npub1vrvcpqkvwyqwcyqsn0537szd5t9g0n9dyzvglw242c5cqh6em98q7797jm 
Alas, no.

It was one of those - ALL companies must respond with their certification statement about their products being compatible with Y2K.

I did a quick search - I can't seem to find an online source for that.

I will also note that Y2K problems started in 1995 or so - in credit card processing when the expiration date of the card was 2000 or later.

They continue to pop up in 2010, 2020 (y2k+20) where code worked around the problem instead of fixing it too.