On the flip side, most ISP operated edge DNS servers ignore low TTLs below their desired threshold now as a means of reducing load, I've seen some force a 24hr minimum.

There are ways to do VPNs from dynamic endpoints that don't require dynamic DNS. IPSec supports xauth for just this purpose.

Come to think of it, I'm getting emails from VMWare asking for permission to get further emails from them as well...

It's not just MS, OpenSRS (Based out of Canada) has just done away with their email notification for system outages as well. They're now providing an RSS feed or you can periodically check their blog. Their solution for those who liked email alerts, a third party service that watches the RSS feed and emails on updates...

A reboot isn't a power cycle... and at least on the Intel's if you go with an enterprise model they stay in RO mode. It's certainly something to consider, I'd hope for an appliance design the estimated write volume would be taken into consideration also so you would never plan for the drive to reach that point in the appliance's life span?

The drive did go into read only, until power cycled. As documented.

I get the planned obsolescence gripe, but it didn't lock out until over twice it's advertised write capacity had been burned through, and again, at no time did it corrupt data. You light the fuse with the first write and advance towards the time bomb with each additional one, so planned or not the drive only has a finite life span. Would you prefer the Samsung's failure mode instead?

Actually, if you read the article...

None of the drives died at their 200TB rated endurance, although the Samsung DID fail a data retention test. The Intel let go at 700+ TB of writes along with two other drives, but did so with plenty of advance warning and died in a way as to allow for one last read off of the data without corrupting it with a bad write. Hard to fault them there.

If there is enough bandwidth that there is no congestion or queing required, QoS is useless.

And QoS isn't needed if you have enough bandwidth in place in the first place.

And that is why DMARC is a bad standard that hopefully the net as a whole rejects. They purposely avoided the RFC process. RFCs may not be 'internet law' but if everyone decides to start going their own way, we're going to end up back in the olden days of IM with everyone stuck in balkanized little e-mail fiefdoms unable to contact other fiefdoms. Would sir like to sign up for Google's Internet, Microsoft's, Yahoo's? Pick one, and hope your friends pick the same.

Breaking normal mailinglist behavior... DMARC is based on a misinterpretation and misuse of email headers.

Not entirely true. While they don't collect funds collected via taxes, they also don't PAY taxes on many things, like say property taxes for their offices, sorting facilities, etc. So they indirectly are Government funded, at the state and municipality level.

With the way DMARC is being implemented, I don't think there is a way for a listserve to be 'DMARC compliant'.

Instead I've had to tell those with Yahoo and Hotmail accounts to go away and not to come back until they get an account with a non DMARC nutter service.

You're assuming they can dispose of the material for $0 per ton instead. I believe that you'll find is not the case.

Of course, this is ignoring the INCREASE in accidents this will cause by people looking forward, staring at a screen rather than backwards while backing up, missing little details like traffic to the left and right, etc. I'd be much happier if they mandated a minimum visibility spec out the back than cameras, we're now mandating distracted backing up... blech.

(Side note, I won't be riding a motorcycle on the street ever again, too many idiots not paying attention at the wheel now, this isn't going to help.)