misk@sopuli.xyz to Technology@lemmy.worldEnglish · 3 months agoGoogle confirms the leaked Search documents are realwww.theverge.comexternal-linkmessage-square35fedilinkarrow-up1415arrow-down15cross-posted to: technology@lemmy.ziphackernews@lemmy.smeargle.fans
arrow-up1410arrow-down1external-linkGoogle confirms the leaked Search documents are realwww.theverge.commisk@sopuli.xyz to Technology@lemmy.worldEnglish · 3 months agomessage-square35fedilinkcross-posted to: technology@lemmy.ziphackernews@lemmy.smeargle.fans
minus-squarecybersandwich@lemmy.worldlinkfedilinkEnglisharrow-up70·3 months agoWhere are these docs? No one ever links to them or says where you can find them
minus-squareEarJava@lemmy.worldlinkfedilinkEnglisharrow-up42·3 months agoThousands of documents, which appear to come from Google’s internal Content API Warehouse, were released March 13 on Github by an automated bot called yoshi-code-bot.
minus-squareMashedTech@lemmy.worldlinkfedilinkEnglisharrow-up4arrow-down5·edit-23 months agoGod, I hate GitHub. It always gets stuck when there are many changes
minus-squarecm0002@lemmy.worldlinkfedilinkEnglisharrow-up22·3 months agoFr, just like when those game source codes leak or whatever. It’s cool and people want to download it just because, just link them lmao
minus-squaredeweydecibel@lemmy.worldlinkfedilinkEnglisharrow-up21·3 months agoThey were leaked specifically to “SEO experts” who shared portions of it. I don’t know if it was leaked publicly. I’m basically what happened is the leaker is an SEO guy, that runs an SEO company, and leaked the documents to another SEO guy.
minus-squareHootinNHollerin@lemmy.worldlinkfedilinkEnglisharrow-up16arrow-down2·edit-23 months agoI wonder if any are on Internet archive, and perhaps that’s why the ddos
minus-squaredumbass@leminal.spacelinkfedilinkEnglisharrow-up10·3 months agoHidden way back behind a machine.
minus-squareripcord@lemmy.worldlinkfedilinkEnglisharrow-up3·3 months agoThat’d not where they’ve been primarily located, no.
minus-squareFaresh@lemmy.mllinkfedilinkEnglisharrow-up11·3 months agohttps://hexdocs.pm/google_api_content_warehouse/0.4.0/api-reference.html
minus-squareNoSpiritAnimal@lemmy.worldlinkfedilinkEnglisharrow-up5arrow-down2·3 months agoCould I get a google docs link?
minus-squareMy Password Is 1234@lemmy.worldlinkfedilinkEnglisharrow-up4arrow-down2·3 months agoRemindMe! 12h
minus-squareOtter@lemmy.calinkfedilinkEnglisharrow-up17arrow-down2·3 months agoThere actually is a bot here for that @RemindMe@programming.dev 12 hours
minus-squareDark_Dragon@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up3·3 months agoOye reminding you after 12hrs
Where are these docs? No one ever links to them or says where you can find them
Thousands of documents, which appear to come from Google’s internal Content API Warehouse, were released March 13 on Github by an automated bot called yoshi-code-bot.
God, I hate GitHub. It always gets stuck when there are many changes
t?
t!
Ot!
Fr, just like when those game source codes leak or whatever. It’s cool and people want to download it just because, just link them lmao
They were leaked specifically to “SEO experts” who shared portions of it. I don’t know if it was leaked publicly.
I’m basically what happened is the leaker is an SEO guy, that runs an SEO company, and leaked the documents to another SEO guy.
I wonder if any are on Internet archive, and perhaps that’s why the ddos
Hidden way back behind a machine.
That’d not where they’ve been primarily located, no.
https://hexdocs.pm/google_api_content_warehouse/0.4.0/api-reference.html
Could I get a google docs link?
RemindMe! 12h
There actually is a bot here for that
@RemindMe@programming.dev 12 hours
Oye reminding you after 12hrs
Thanks!