4 ms·
No fix citing "internal communication difficulties", perhaps Google could use, I don't know, some kind of tool. I too work for a huge company, and oddly enough
by coldcode 7y ago
No fix citing "internal communication difficulties", perhaps Google could use, I don't know, some kind of tool. I too work for a huge company, and oddly enough we also have communications difficulties sometimes despite all of our tools. But we not a technology company, seems like a Google should be better at this.
- the_duke 7y ago"internal communication difficulties" does not mean "I can't talk to the person", it means political infighting or the responsible team doesn't care/see it as a problem.
- AJ007 7y agoThere is probably a long winded explanation somewhere how this is actually a feature and not an exploit.
- chrismorgan 7y agoWell, how are you going to fix it without removing important features like submitting pages to the index? There are no perfect XSS auditors; you can fairly consistently work around Chrome’s, which is why they’re giving up on it now. I don’t see any realistic solution to this problem.
- londons_explore 7y agoI can imagine the search teams response now... "If your site has an XSS, then anyone can make any content appear on that domain... So why's it so bad if anyone can also make anything appear on the domain in Google Search? - we're just reflecting reality. Next you guys will report that you wrote a comment in hackernews and that appeared on google search too!"
- eadmund 7y ago> No fix citing "internal communication difficulties", perhaps Google could use, I don't know, some kind of tool. That's the problem: half the team was using Google Hangouts, the other half of the team were using Google Meet, and three random guys are using Allo.
- cbsks 7y agoDon't forget the one stubborn person still using Wave