Quote from: Yrth on Today at 09:08:05 AM

Quote from: mikeywith on November 26, 2021, 10:27:17 PM

It's funny that they expect everyone to be on telegram, they should have sent out emails right after this shit happened, anyway, mining is going alright, heck, this is less scary than my experience with Poolin a while back, the pool was working just fine but my hashrate was showing zero.

I logged into the .net site and was unable to make any changes to the payout addresses as the email verification never came. They are probably having the same issue with their email server.

I was however able to withdraw all mined coin to previously setup payment addresses.

I did a quick look at the email that came in on Friday about the name going from .com to .net and it did not have any SPF / DKIM / DMARC information in it so there are a lot of email services that may just blackhole the email not even accept it.

What those acronyms mean:
SPF = https://en.wikipedia.org/wiki/Sender_Policy_Framework
DKIM = https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail
DMARC = https://en.wikipedia.org/wiki/DMARC

On a related note, things like this are why everyone should use DNSSEC, but for some reason trying to get people to do it is an uphill fight.
I do it on the 2 domains that I have that matter. But not on the rest. Getting others to do it is just about impossible.
There was even a discussion about a year ago on the bitcoin core github about making DNSSEC required for the seed nodes that went nowhere.
Would not have made much of a difference on what happened here, but in general it's a good thing.

DNSSEC = https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions

-Dave