Re:Stealing private documents through a bug in Google Docs
by Jabbles on Monday December 28, 2020 @10:00AM
(#25559652)
It is unlikely they wouldn't have checked other products as part of the fix. So I'm going to ask for more proof that you "tested this out".
[ Parent
| on HN ]
[dead]
Re:Stealing private documents through a bug in Google Docs
by tptacek on Monday December 28, 2020 @01:24PM
(#25561612)
You can't comment like this on HN; accusing other commenters of having secret conflicts of interest is the HN Guideline 'dang corrects most often here:
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
Re:Stealing private documents through a bug in Google Docs
by jtbayly on Monday December 28, 2020 @03:47PM
(#25563043)
Doesn’t seem like an accusation of a conflict of interest to me. Just pointing out who has the burden to test. Since one is paid by the company, it does make sense for testing the company’s products would be his responsibility first.
Whereas the previous comment was accusing the other one of lying about testing it.
Re:Stealing private documents through a bug in Google Docs
by tptacek on Monday December 28, 2020 @04:01PM
(#25563164)
Did I miss the place on this thread where the person we're talking about said they worked for Google?
Re:Stealing private documents through a bug in Google Docs
by jtbayly on Monday December 28, 2020 @05:46PM
(#25564169)
Nope. Sorry. I messed up. Thought I saw the same person commenting who he already said they worked at Google.
Re:Stealing private documents through a bug in Google Docs
by alisonkisk on Monday December 28, 2020 @04:19PM
(#25563345)
An employee of X is better suited to investigate a bug in X than a non-employee is