CydeWeys

39 ms·

541.
by CydeWeys 3y ago
Why are you connecting to a printer that's on your LAN using a .dev domain on the entire Internet in this example? Also, if this is really a problem, use a different TLD?
542.
by CydeWeys 3y ago
Now you're talking about something completely different though. Connecting to a printer over LAN is not at all the same as a Web browser talking to a third party webserver over WAN.
543.
by CydeWeys 3y ago
http is insecure and should not be used. Not always using https would defeat the entire purpose of the added security, not least because a MitM attacker could block only the https packets and then force a silent downgrade to insecure http.
544.
by CydeWeys 3y ago
We announced we were doing this way back in 2017 and have stuck to it. It's just surprising that so few others have joined us. https://security.googleblog.com/2017/09/broadening-hsts-to-s...
545.
by CydeWeys 3y ago
Lyft shareholders have already lost the vast majority of their investment. And I think we should have better motives here than punitive maliciousness.
546.
by CydeWeys 3y ago
Economy of scale exists, though. I don't think there's any subset of its current markets that Lyft can reduce itself down to and be profitable.
547.
by CydeWeys 3y ago
Right but if you're not hosting Web content then you wouldn't want it linkified in a Web context. If you're using it for something else, e.g. SMTP, then you'd represent the domain name differently as username@your.doma
548.
by CydeWeys 3y ago
The point is, if Lyft goes out of business, it has the same effect on the market for rideshare prices as an acquisition does, so why not allow the merger so it's less disruptive and more employees get to keep their jobs?
549.
by CydeWeys 3y ago
Yes, I was more talking about the older ccTLDs for more real countries.
550.
by CydeWeys 3y ago
Those are fake domain names. They don't resolve in the root DNS nameservers. This is one of the many reasons that "alternate roots" are terrible and will never be widely adopted.
551.
by CydeWeys 3y ago
That's not remotely how ICANN works though. Everything always takes many years and has a million different discussions, processes, veto points, etc.
552.
by CydeWeys 3y ago
This is just flat out not how ICANN actually operates, though.
553.
by CydeWeys 3y ago
I work in this industry and know the people making these decisions and I'm not aware of anyone in favor of releasing the RFC 2606 reservations.
554.
by CydeWeys 3y ago
Except that it's not, and never was, because it was never expressly reserved for this purpose. And it was particularly unreasonable to use for testing since 2012 when multiple applications were submitted to ICANN to create it as a gTL
555.
by CydeWeys 3y ago
The standard gTLD registry operator contract does not allow ICANN to unilaterally yank delegated TLDs.
556.
by CydeWeys 3y ago
Nope. Not even .su which continues to exist more than three decades after the country it represents ceases to exist. The time to comment on new gTLDs was a decade ago.
557.
by CydeWeys 3y ago
And, you know, the existence of countries, that speak different languages...
558.
by CydeWeys 3y ago
Those 4 reserved labels in that RFC are not going to be released, period.
559.
by CydeWeys 3y ago
.test will not become a gTLD. See RFC 2606.
560.
by CydeWeys 3y ago
You'd be throwing a warning on nearly every domain name, including this very site we're on right now. What would be the point? Domain names are different from file system paths, full stop.
561.
by CydeWeys 3y ago
Its five year anniversary is this month, in fact. https://blog.google/products/registry/5-apps-you-should-know...
562.
by CydeWeys 3y ago
Fun fact about the application details is that they aren't binding, and ICANN actually encourages taking formerly closed domains and opening them up for general registration.
563.
by CydeWeys 3y ago
g and space are both home finger keys though. Question mark is not nearly so easy to type. I think "g " might win out. To get it to work I think you need to configure g as a bookmark shortcut though, so it's not built-in.
564.
by CydeWeys 3y ago
I would say it's the other way around, no? Common file extensions are offenders for copying ccTLDs that already existed.
565.
by CydeWeys 3y ago
Devil's advocate -- what exactly is the attack vector here, even for TLDs that share names with executable file extensions? .com already exists, the biggest one of them all, and that doesn't seem to cause problems? https:/&
566.
by CydeWeys 3y ago
Nice. I usually just wrap it in double quotes, but this is slightly easier.
567.
by CydeWeys 3y ago
un.zip isn't registered, it's a globally reserved term on all gTLDs for the United Nations. You can query WHOIS/RDAP to see that it's not registered.
568.
by CydeWeys 3y ago
If it's a relative path then it's not a TLD. It's only a TLD when it's part of a domain name.
569.
by CydeWeys 3y ago
> They're not ccTLDs though, but TLDs bought by a registrar. Registry, not registrar.
570.
by CydeWeys 3y ago
For what it's worth, .us is the ccTLD for the United States, and policies for it like "You can't hide your WHOIS info" would be set by the US government, not by GoDaddy. GoDaddy Registry as the backend registry service

More ›