11–20 of 26 posts
Earlier quoted context omitted.
That's fine, you just route to /dev/null everything that goes to the anonymised address; the email headers either won't be re-written or will be re-written a la RFC 5321. Either way you'll be able to easily identify emails sent to the anon email address and dump them on the floor.
As well as any legitimate emails coming to you regarding your domain.
Earlier quoted context omitted.
That's far better than the current system. Atm I have to expose my email domain, which means some spammers just fire a broadside of this crap. When it comes from an anonymized email forwarder, I can easily just redirect it into the spam folder.
What purpose does the Whois email serve if most people want to directly send it to their spam box? Seems like they should just scrap it.
Clickbait title. This is out for community review, nothing is final yet. https://www.icann.org/news/blog/data-protection-privacy-upda...
Earlier quoted context omitted.
That's far better than the current system. Atm I have to expose my email domain, which means some spammers just fire a broadside of this crap. When it comes from an anonymized email forwarder, I can easily just redirect it into the spam folder.
What purpose does the Whois email serve if most people want to directly send it to their spam box? Seems like they should just scrap it.
Earlier quoted context omitted.
Think so? "The public WHOIS would include an anonymized email address or a web form from which messages could be forwarded to the registrant email address."
That's fine, you just route to /dev/null everything that goes to the anonymised address; the email headers either won't be re-written or will be re-written a la RFC 5321. Either way you'll be able to easily identify emails sent to the anon email address and dump them on the floor.
Earlier quoted context omitted.
As well as any legitimate emails coming to you regarding your domain.
I don't think I ever received legitimate forms of coherent communication over my WHOIS emails.
Given that blog authors increasingly rely on Twitter for feedback (which I don’t use), I occasionally check whois to send notifications about dead links, rendering issues, etc.
Anyone else think things like this, dns, ssl authority, and lots more a better areas to focus blockchain tech toward?
Any real, reliable blockchain solution is not going to be the decentralized authority model that Bitcoin has, it’s going to be a tiered trust authority in the same way that SSL roots work today. You’re going to end up with very similar governance models and the same organizations, just implemented in blockchain.
I think some of the important impacts of blockchain are yet to be recognized: I do think it will force us to fundamentally think about what consensus and rule of law means in any given scenario, and that will have some pretty outsized social impacts — especially in the way we run organizations.
We will have to be far more deliberate about how we design our governance models, but I worry they will become so complex as to grow beyond the possibility of oversight...
Earlier quoted context omitted.
What purpose does the Whois email serve if most people want to directly send it to their spam box? Seems like they should just scrap it.
What if there’s something illegal, violating copyright, etc. on the site? Or to take a less legal example, what if someone’s site is hacked? You need some way of getting in touch with the owners.
Atleast in my area websites are also required to carry legal contact information somewhere on the site, which is far easier to secure against spammers than the WHOIS database.