bolster
Joined 14 years ago
Joined 14 years ago
Last I checked, that wasn't how citations worked.
I only sampled one data point (2017 AMD EPYC Rome Clock rate) which was significantly off, because in 2017 it was the Naples chipset that was released, and, unless 2017 was desperate enough to clock from 2.2Ghz to 3Ghz on the regular (Boost up to 3.2Ghz), the 'research' was a fair bit off...
Doesn't undermine or contradict the authors (bots?) point, but a strange way to provide 'evidence' for an argument.
I could see a solid usecase for a duress script that clears all these and requires 'standard' reauth, so that at least you're back to a 'defence in depth' style. Also, in the 'Pushover' example, I can't imagine many attackers waiting to plug the thing in before starting the ~pipe wrench~ credentials discussion.
Yup, that was an innovation in 2018... (Greetings from the EU)
Disappointed that this appears to be US only. would love to use a few of these for monitoring our Hackerspace!
Actually I'm also involved in mobile ad hoc security research so might try and 'acquire' a few of these for testing out some collaborative network theories on our quadcopters... but can't do that as current delivery status stands!
Good luck with certification.
It's not about defining what experience people get, it's that as they are coming into your site, they get the right experience for your content on their device, regardless of whether they were given a desktop link on a mobile device or visa versa.
As demonstrated in the diagram, this is punishing people who strip the tails off incoming links so the link example.org/stories/good-news-everyone gets directed to m.example.org and the user is left with the mobile experience, but the wrong content.
bolster.online