3 ms·
The most important part of the article is at the bottom, google's response when questioned about it: > "The risk of confusion between domain names and file nam
by spicybright 3y ago
The most important part of the article is at the bottom, google's response when questioned about it:
> "The risk of confusion between domain names and file names is not a new one. For example, 3M’s Command products use the domain name command.com, which is also an important program on MS DOS and early versions of Windows. Applications have mitigations for this (such as Google Safe Browsing), and these mitigations will hold true for TLD’s such as .zip.
> At the same time, new namespaces provide expanded opportunities for naming such as community.zip and url.zip. Google takes phishing and malware seriously and Google Registry has existing mechanisms to suspend or remove malicious domains across all of our TLDs, including .zip. We will continue to monitor the usage of .zip and other TLDs and if new threats emerge we will take appropriate action to protect users." - Google.
Good thing google never gets any of this stuff wrong, and has a great appeal process for people flagged in error /s
- pixl97 3y ago"It's not new, it's caused a lot of problems, and we're going to make it worse" What's really stupid about this is a huge number email systems just outright block things like .com and .exe attachments of any kind to avoid direct executable content. Zip content is generally allowed, but typically scanned. Well, not to maximize user confusion we're adding a new context to one of the most common file extensions in email and downloads there is. Yay Google, thank you very much.
- thesneakin 3y agoAs a millennial user, wth is a file extension? What's a directory?