News for hackers. Stuff that matters.
Re:HSTS for new TLDs by emehrkay on Saturday July 19, 2014 @09:30AM (#8057422)
"I can't speak for Firefox and Safari but I think it's safe to assume that Firefox"

Maybe one of these Firefoxes should say Chrome

Re:HSTS for new TLDs by cdh on Saturday July 19, 2014 @10:12AM (#8057512)
It is a bit confusing, but I'm not sure that this is actually an error. It sounds like he may be in a position to directly make that change to Chrome, but is trying to clarify that his thoughts on Firefox and Safari are his, and he can't speak on their behalf. When you read it that way, it makes sense.
Re:HSTS for new TLDs by schoen on Saturday July 19, 2014 @12:28PM (#8057898)
What's more, Firefox previously adopted a related thing that agl invented (HSTS preloads in general), so he has personal experience of their being amenable to this sort of thing.
Re:HSTS for new TLDs by tptacek on Saturday July 19, 2014 @01:00PM (#8058021)
The Chrome SSL team works very closely with that of Firefox.
Re:HSTS for new TLDs by iancarroll on Saturday July 19, 2014 @07:21PM (#8059103)
not to mention Firefox pretty much uses the HSTS preload list that Chrome does.