Unpopular opinion (maybe): given the current situation, we should probably consider phasing out TLDs somehow. It's becoming more and more clear than no TLD outside those established before the '90s are actually viable for anything outside of "my small personal blog". It would also avoid people having to remember if the TLD is .net or .com, for instance (even though in my experience .net is slowly disappearing too).
The Perils of an .xyz Domain
231–240 of 282 posts
Re: The Perils of an .xyz Domain
#232I have my name .xyz and I’ve mostly given up using it for email, because I am sick of:
* “Do you mean ‘biz’” on web forms
* other forms just refusing to validate unless I disable the client-side validation
* other systems ostensibly accepting it and just never sending me anything, because it fails to validate silently in their backend
* having to put whatever I am trying to get done on hold for a few minutes when I need to read it to a human, because they’ve “never heard that one before”
Re: The Perils of an .xyz Domain
#233If I ever start a super-secret club, I now know what the domain name TLD should be. Nobody would be able to spread the secret!
Personally, I'd go for some non-printable characters. But, maybe I'm just nostalgic for when starting a directory name with ALT+255 rendered the directory inaccessible to Windows 9x...
Most, I would guess all, registrars don’t allow those characters in domain names.
Re: The Perils of an .xyz Domain
#234Earlier quoted context omitted.
Censorship is far from not limited to government action. I see this misconception a lot, and I believe it comes from Americans misinterpreting their first amendment.
I figured that might come up, but censorship whether govt. or not is seen as "oppression due to opinion". Over-aggressive TLD spam filtering is just bad logic from infosec employees.
Censorship is not limited to “oppression due to opinion”, it can be done for any reason.
Re: The Perils of an .xyz Domain
#235Earlier quoted context omitted.
It's actually worse than that. It isn't blocked because of the sender or recipient, but because of the content . That would be like the postal service reading your mail and deciding that because of an address in the text of a letter, it shouldn't be delivered.
Amusing analogy. The postal service's unwillingness or inability to do just that has severely damaged their utility. If the USPS had a junk-filtering option I'd sign up tonight. Perversely, the postal system seems to embrace junk mail (e.g. if you sign up for address forwarding the USPS sends you a fat envelope full of junk mail as a "confirmation")
The USPS will likely not do anything to disrupt one of its largest sources of revenue
Re: The Perils of an .xyz Domain
#236> initial email open rates rose from 70% to 86% I know this is common knowledge, but it still really creeps me out that companies can track this.
hey.com and icloud email blocks this by default.
Re: The Perils of an .xyz Domain
#237Earlier quoted context omitted.
You'd be getting an unbelievable amount of SMS spam if carriers weren't allowed to block messages. There's a lot of bad actors out there.
We've run into this issue with replies to texts that the user sent first. Telecom spam filtering seems to be a ridiculously primitive and wide net. I can't imagine a valid use case for dropping a text sent to a number when that number just sent you a text a few seconds before. I don't understand why SMS spam has such a big issue with false positives compared to email spam when emails are practically free to send but…
Perhaps their blocking systems are stateless, i.e they don't bother doing a lookup of communication histories because it's expensive when you're dealing with millions of texts an hour. They just run each one through a bunch of rules and drop matches.
Re: The Perils of an .xyz Domain
#238> One surprising side effect of having a .xyz domain is that the mere inclusion of .xyz inside of a text message will result in a silent delivery failure for many providers. This is wild to me. Tested it out myself and I couldn't send an SMS with a spot.xyz link to/from Google Voice T-Mobile. And no "failed delivery" notice either, just a silent failure. And yet I still get so many texts that are obviously spam or ph…
Blocking of messages/emails and blanket email server/domain/extension blacklisting is the same as a postal service not delivering mail to or from a particular entity/street/town. Doing so silently and without a valid and case-specific reason should not be legally allowed. Edit: Added "street/town" to analogy, and "case-specific" before reason
Yikes, sounds like censorship for whole TLD.
Re: The Perils of an .xyz Domain
#239The reason .xyz domains are banned is because of the amount of spam sent from that domain. In my case 100% was spam. So blacklisting it was an easy fix.
If I was owner of the .xyz TLD domain, I would be very concerned to kick out spammers because it kills the value of the .xyz TLD.
Re: The Perils of an .xyz Domain
#240Before I get into email business(I run my own email forwarding service[0]), I don't understand why provider block those domains. Then I immediately got it. The amount of spam emails from .xyz .click .faith .top is huge. And with every email comes from them, we have to run spam scanner, which isn't cheap. So we have to score those TLDs more sensitive. https://www.spamhaus.org/statistics/tlds/ can give some insight abo…
From that spamhaus link .xyz has a lower bad percentage (4.4%) than .com (5.1%) and .net (10.5%).
Maybe because .xyz is blacklisted, spamhaus doesn't see them.