🛠 Building the Responsible AI Toolkit.
Today at #GoogleIO, we announced a new dataset exploration tool, Know Your Data! Learn how to integrate Responsible AI practices into your ML workflow in this session with @LudovicPeran and @catherina_xu.
Watch → https://t.co/v73rx9jJWR
@SlackHQ@rootlyhq@SlackHQ do you make it a point to work with plagiarists (especially repeated plagiarists) often? That seems like an awkward combination, and not one you'd want to get behind. https://t.co/Fu0r42IYJF
@AskeBay what is it going to take for eBay to do the right thing here? Phone team claims they resubmitted my affidavit, that was 4 days ago. Fraudulent buyer has multiple histories of defrauding eBay sellers, which eBay has let continue to happen. Do I need to involve news media?
@AskeBay I am a victim of buyer return fraud. It is an extremely clearcut, readily & multiply verifiable case. At every turn, customer support has taken the easy (but incorrect) resolution. I submitted a signed affidavit; email team claims I never sent, phone team claims I did.
@reesencybias & I led a @googlesre team that landed a data pipeline w/ huge #covid19 health wins. The whole product team used cutting-edge privacy tech to respect our users; so we're pleased to receive the @futureofprivacy Award for Research Data Stewardship in our @lifeatgoogle!
We’re honored to have been recognized with the second-annual FPF (@futureofprivacy) Award for Research Data Stewardship for our #COVID19 Community Mobility Reports and Aggregated Mobility Research Dataset. https://t.co/px14moQS73
We’re honored to have been recognized with the second-annual FPF (@futureofprivacy) Award for Research Data Stewardship for our #COVID19 Community Mobility Reports and Aggregated Mobility Research Dataset. https://t.co/px14moQS73
🛠 Building the Responsible AI Toolkit.
Today at #GoogleIO, we announced a new dataset exploration tool, Know Your Data! Learn how to integrate Responsible AI practices into your ML workflow in this session with @LudovicPeran and @catherina_xu.
Watch → https://t.co/v73rx9jJWR
@tbreisacher It's absolutely weird that the company has fired people for many reasons. (My friend Laurence Berland is one direct example in my life.) But decoupling: there have been 0 people who have been doing Reliability on this subject at Google, ever, before, so it's _starting_ with 20%.
@tbreisacher Hey @tbreisacher I'd be thrilled if you were like "yay it's possible to spend your 20% time on this at Google!" or I'd also be completely understanding if it was "How can 20% possibly be enough?!" However the emoji-that-doesn't-exist, I hope you enjoy the site and file bugs!
@jhscott@timnitGebru@mmitchell_ai Thank you! btw the "send feedback" top corner link to the github issues queue and email list is, I promise, completely read, so if you see anything wonky, please hit us up!
@jhscott@timnitGebru@mmitchell_ai Absolutely, Jacob. +1 to your yes/and but, no question there. I'm proud of the work we did on this tool, and I understand @mmitchell_ai specificially had influence on several portions of its design based on some dev chatter I saw.
@dsmilkov We were and are so happy to help, @dsmilkov! As we like to say in @googlesre, "When SRE show up, it's to put jetpacks on things that deserve to be scaled."
The launch effort was truly a fun team effort, including but not limited to: @MoVonLagos, @hmiomiso, Arthur Hyun, Chris Forker, Giselle Font, Sterling Stein, @dsmilkov, @nsthorat, @LudovicPeran, @m_pellat, our friends in L7 routing SRE, and many other #GooglePAIR folks :)
@baytrojan03@cole_e_thornton@SCCgov Looks like I just got another broadcast message pointing to an https://t.co/8MJ9euWt4I URL. Amazingly, the site did not fall over. I will declare victory here, whether or not my unreplied email to sccgov webteam or gratuitous tagging of @sccgov did anything. I'll take it!
@baytrojan03@cole_e_thornton@SCCgov Since this the third or fourth time their site has buckled this year alone from their own self-inflicted laserbeaming, I've reached out to a webmaster and some network engineers at @SCCgov in the hopes they want to try out using a CDN. 🤷
@wwb@SCCgov Looks like I just got another broadcast message pointing to an https://t.co/8MJ9euWt4I URL. Amazingly, the site did not fall over. I will declare victory here, whether or not my unreplied email to sccgov webteam or gratuitous tagging of @sccgov did anything. I'll take it!
@wwb@SCCgov Since this the third or fourth time their site has buckled this year alone from their own self-inflicted laserbeaming, I've reached out to a webmaster and some network engineers at
@SCCgov in the hopes they want to try out using a CDN. 🤷♂️