I think technically a URL/URI is only supposed to contain ASCII characters, and certain things that expect URL input will want ASCII only. However, all modern browsers can convert from Unicode to punycode (in the domain name) and percent-encoding (in the path). So I don't really understand why browsers only let you copy the percent-encoded form easily.
When visiting the page (at least on Firefox), the location bar displays the intended characters, but when copying it you get the percent-encoded form. If the reason for percent-encoding was just to make scams more obvious, shouldn't the form shown in the browser interface also be URL-encoded?
By the way, it seems like that is a much stronger argument when applied to domian names than when applied to the part of the URL after the slash.
The USSR was not part of the Axis. Quite the opposite. (Although they did have a non-aggression pact with Germany before the start of the war, that did not last long.)
Which just goes to show that many Americans aren't really aware of how the Soviets were crucial to winning that war.
It is true to that they joined the Allies, and the Eastern Front was very important to defeat of Nazi Germany, but let’s be honest when the Molotov-Ribbentrop Pact ended: after Stalin and Hitler coordinated a joint invasion of Poland.
To act like the Soviet Union was Ireland or Switzerland at the start of the war, is disingenuous. Stalin and Hitler made a secret plan to carve out an Eastern European sphere of influence, not unlike the Japanese sphere of influence in East Asia.
The irony of course is that Stalin still got his sphere influence, albeit through the Treaty of Yalta.
They seem to have that warning on every single page of catalog.archives.gov. That solution seems much easier than figuring out whether each individual item requires a warning or not.
OP is onto something - the mesage should reflect that in such case.
One thing I learned at work preparing countless PPTs and bug reports is that people will misunderstand or overinterpret whatever you write, so better write precisely in an idiot-proof manner and provide context.
I personally would move this to be the navy-colored navigation bar. It could be reasonably understood that this section does not directly represent the item shown at the page. Similar stuff should be together, after all - and that bar links to e.g. accessibility statement, which is also a kind of meta-content.
- Non-tech-savvy users might not instantly recognize example.xyz as a domain name. When you discuss your site in person, you might have to explain the TLD, whereas with .com, .net, .org, this isn't an issue.
- If the same domain name but with a more popular TLD exists, people might accidentally go there instead.
- Some outdated validation code (such as a regex to match valid email addresses) might not recognize the TLD, especially if it's one of the long ones. I'm not sure if this problem actually exists, but it could.
