Re:Grammarly shared its tokens with all websites
by knute on Tuesday February 06, 2018 @09:24AM
(#16316350)
It seems like it would be more fair for the headline to use the past tense.
Re:Grammarly shared its tokens with all websites
by dang on Tuesday February 06, 2018 @01:15PM
(#16318133)
Agreed; edited. Explained at https://news.ycombinator.com/item?id=16318122.
Re:Grammarly shared its tokens with all websites
by nascar_is_bad on Tuesday February 06, 2018 @11:03AM
(#16317099)
Gotta get that HN karma tho
Re:Grammarly shared its tokens with all websites
by ghostbrainalpha on Tuesday February 06, 2018 @11:36AM
(#16317365)
You are getting down votes because HN has a policy that the HN Title should match the Title on the link to prevent editorializing in almost all cases.
This prevents users from creating click bait headlines to get that karma tho, the majority of the time. Cases where the actual title is the click bait like this one, are the unintended consequence of that policy.
Re:Grammarly shared its tokens with all websites
by dang on Tuesday February 06, 2018 @01:14PM
(#16318122)
That's true, except the guideline reads "Please use the original title, unless it is misleading or linkbait" and you can argue that once a vulnerability is fixed, implying it's still there is misleading. So we often edit those titles to past tense once that's more accurate. Same with "$site is down" -> "$site was down".
Re:Grammarly shared its tokens with all websites
by zeven7 on Tuesday February 06, 2018 @01:25PM
(#16318207)
HN seems like the kind of place where there could be exceptions to the policy when there's good reason.
Re:Grammarly shared its tokens with all websites
by AltCtrl on Tuesday February 06, 2018 @09:11AM
(#16316280)
I was trying to reproduce the bug when I got to that line... nice to see it fixed quickly.
Re:Grammarly shared its tokens with all websites
by tedivm on Tuesday February 06, 2018 @02:07PM
(#16318601)
They probably should have waited to let Google know they fixed it though, as Google releases the bug details immediately when a fix is made rather than waiting to give people a chance to upgrade before it's made public.
Re:Grammarly shared its tokens with all websites
by gpvos on Tuesday February 06, 2018 @06:09PM
(#16320842)
Tavis notes that users should have been auto-updated to the fixed versions by now.
Re:Grammarly shared its tokens with all websites
by joncrane on Tuesday February 06, 2018 @04:42PM
(#16320116)
Maybe they knew what they were doing and had a fix tee'd up for when they were found out?
Re:Grammarly shared its tokens with all websites
by nikojn on Tuesday February 06, 2018 @06:16PM
(#16320879)
Why would they wait to patch a massive vulnerability in their site that's just waiting to shower them in negative press?
> Grammarly had fixed the issue and released an update to the Chrome Web Store within a few hours, a really impressive response time.
Nice to see a company take this kind of thing appropriately seriously (although of course it should never have happened in the first place).