perhaps the most surprising to me is the apparent willingness to enter credit card info online in 1999. I wasn't around for this period but wasn't the conventional wisdom back then that this was insecure? hence PayPal?
The Passport Payment (2000)
21–30 of 55 posts
Re: The Passport Payment (2000)
#22perhaps the most surprising to me is the apparent willingness to enter credit card info online in 1999. I wasn't around for this period but wasn't the conventional wisdom back then that this was insecure? hence PayPal?
Re: The Passport Payment (2000)
#23Re: The Passport Payment (2000)
#24Could you imagine doing this today? You'd probably get lawyers making you sign agreements saying your payment of the domain renewal is not a ownership interest in the domain and threatening to take you to court for renewing their domain.
Re: The Passport Payment (2000)
#25I'm confused, how did he pay for someone else's domain? Was there no authentication?
Back then, control was authenticated as necessary for the proper functioning, but even today I see no reason why renewal should have to be gated behind login walls. Actually, I'd even prefer it not to be, because you might, in a pinch, be prevented from paying for them yourself electronically, having to call in a favor and promise to pay back as soon as you see that friend. Or you just prefer to pay someone cash for…
Re: The Passport Payment (2000)
#26perhaps the most surprising to me is the apparent willingness to enter credit card info online in 1999. I wasn't around for this period but wasn't the conventional wisdom back then that this was insecure? hence PayPal?
Re: The Passport Payment (2000)
#27Earlier quoted context omitted.
It used to be that nameserver changes with TLDs were measured in days, not minutes. Even today some TLDs continue to operate this way.
What are reasonable timeframe expectations for nameserver changes now?
Re: The Passport Payment (2000)
#28According to the story, it took somewhere between 13 and 19 hours for passport.com to resolve properly after he renewed it for Microsoft. Is that normally how long it takes to reactivate a domain name that has gone into a renewal grace period, or was something different back then? Perhaps the NXDOMAIN response was cached by ISPs for an especially long time because it was such a frequently visited hostname?
NXDOMAIN is often cached for much longer because it's assumed not to change soon. Sometimes, as in this case, that's a wrong assumption.
Re: The Passport Payment (2000)
#29perhaps the most surprising to me is the apparent willingness to enter credit card info online in 1999. I wasn't around for this period but wasn't the conventional wisdom back then that this was insecure? hence PayPal?
People who used mail orders before the internet might remember that the options included sending a cheque along with the order form or filling in your credit card details on the order form (that's a paper form that you send in the post), and I think that this is still the case. So I don't think that average people really saw sending card details online any differently. I even remember being asked for my card details by email!
Re: The Passport Payment (2000)
#30Earlier quoted context omitted.
NXDOMAIN is often cached for much longer because it's assumed not to change soon. Sometimes, as in this case, that's a wrong assumption.
I thought NXDOMAIN results were cached for as long as the TTL in the parent SOA record?