Английская Википедия:Bard (chatbot)
Шаблон:Short description Шаблон:Use American English Шаблон:Use list-defined references Шаблон:Use mdy dates Шаблон:Infobox software
Bard is a conversational generative artificial intelligence chatbot developed by Google. Initially based on the LaMDA family of large language models (LLMs), it was later upgraded to PaLM and then to Gemini. Bard was developed as a direct response to the meteoric rise of OpenAI's ChatGPT, and was released in a limited capacity in March 2023 to lukewarm responses before expanding to other countries in May.
LaMDA was developed and announced in 2021, but was not released to the public out of an abundance of caution. OpenAI's launch of ChatGPT in November 2022 and its subsequent popularity caught Google executives off-guard and sent them into a panic, prompting a sweeping response in the ensuing months. After mobilizing its workforce, the company launched Bard in February 2023, with the chatbot taking center stage during the 2023 Google I/O keynote in May.
Background
Шаблон:Further In November 2022, OpenAI launched ChatGPT, a chatbot based on the GPT-3 family of large language models (LLM).[1][2] ChatGPT gained worldwide attention following its release, becoming a viral Internet sensation.[3] Alarmed by ChatGPT's potential threat to Google Search, Google executives issued a "code red" alert, reassigning several teams to assist in the company's artificial intelligence (AI) efforts.[4] Sundar Pichai, the CEO of Google and parent company Alphabet, was widely reported to have issued the alert, but Pichai later denied this to The New York Times.[5] In a rare move, Google co-founders Larry Page and Sergey Brin, who had stepped down from their roles as co-CEOs of Alphabet in 2019, were summoned to emergency meetings with company executives to discuss Google's response to ChatGPT.[6] Brin requested access to Google's code in February 2023, for the first time in years.[7]
Earlier in 2021, the company had unveiled LaMDA, a prototype LLM,[8][9] but did not release it to the public.[10] When asked by employees at an all-hands meeting whether LaMDA was a missed opportunity for Google to compete with ChatGPT, Pichai and Google AI chief Jeff Dean stated that while the company had similar capabilities to ChatGPT, moving too quickly in that arena would represent a major "reputational risk" due to Google being substantially larger than OpenAI.[11][12] In January 2023, Google sister company DeepMind CEO Demis Hassabis hinted at plans for a ChatGPT rival,[13] and Google employees were instructed to accelerate progress on a ChatGPT competitor, intensively testing "Apprentice Bard" and other chatbots.[14][15] Pichai assured investors during Google's quarterly earnings investor call in February that the company had plans to expand LaMDA's availability and applications.[16]
History
Announcement
On February 6, 2023, Google announced Bard, a conversational generative artificial intelligence chatbot powered by LaMDA.[17][18][19] Bard was first rolled out to a select group of 10,000 "trusted testers",[20] before a wide release scheduled at the end of the month.[17][18][19] Bard is overseen by product lead Jack Krawczyk, who described the product as a "collaborative AI service" rather than a search engine,[21][22] while Pichai detailed how Bard would be integrated into Google Search.[17][18][19] Reuters calculated that adding ChatGPT-like features to Google Search could cost the company $6 billion in additional expenses by 2024, while research and consulting firm SemiAnalysis calculated that it would cost Google $3 billion.[23] The technology was developed under the codename "Atlas",[24] with the name "Bard" in reference to the Celtic term for a storyteller and chosen to "reflect the creative nature of the algorithm underneath".[25][26]
Multiple media outlets and financial analysts described Google as "rushing" Bard's announcement to preempt rival Microsoft's planned February 7 event unveiling its partnership with OpenAI to integrate ChatGPT into its Bing search engine in the form of Bing Chat,[27][28] as well as playing "catch-up" to Microsoft.[29][30][31] Microsoft CEO Satya Nadella told The Verge: "I want people to know that we made them dance."[32] Tom Warren of The Verge and Davey Alba of Bloomberg News noted that this marked the beginning of another clash between the two Big Tech companies over "the future of search", after their six-year "truce" expired in 2021;[27][33] Chris Stokel-Walker of The Guardian, Sara Morrison of Recode, and analyst Dan Ives of investment firm Wedbush Securities labeled this an AI arms race between the two.[34][35][36]
After an "underwhelming" February 8 livestream in Paris showcasing Bard, Google's stock fell eight percent, equivalent to a $100 billion loss in market value, and the YouTube video of the livestream was made private.[29][37][38] Many viewers also pointed out an error during the demo in which Bard gives inaccurate information about the James Webb Space Telescope in response to a query.[39][40] Google employees criticized Pichai's "rushed" and "botched" announcement of Bard on Memgen, the company's internal forum,[41] while Maggie Harrison of Futurism called the rollout "chaos". Pichai defended his actions by saying that Google had been "deeply working on AI for a long time", rejecting the notion that Bard's launch was a knee-jerk reaction.[42] Alphabet chairman John Hennessy acknowledged that Bard was not fully product-ready, but expressed excitement at the technology's potential.[43]
A week after the Paris livestream, Pichai asked employees to dedicate two to four hours to dogfood testing Bard,[44] while Google executive Prabhakar Raghavan encouraged employees to correct any errors Bard makes.[45] 80,000 employees responded to Pichai's call to action.[20] In the following weeks, Google employees roundly criticized Bard in internal messages, citing a variety of safety and ethical concerns and calling on company leaders not to launch the service. Seeking to prioritize keeping up with competitors, Google executives decided to proceed with the launch anyway, overruling an unsympathetic risk assessment report conducted by its AI ethics team.[46] After Pichai suddenly laid off 12,000 employees later that month due to slowing revenue growth, remaining workers shared memes and snippets of their humorous exchanges with Bard soliciting its "opinion" on the layoffs.[47] Google employees began testing a more sophisticated version of Bard with larger parameters, dubbed "Big Bard", in mid-March.[48]
Launch
Google opened up early access for Bard on March 21, 2023, in a limited capacity, allowing users in the U.S. and UK to join a waitlist. Unlike Microsoft's approach with Bing Chat, Bard was launched as a standalone web application featuring a text box and a disclaimer that the chatbot "may display inaccurate or offensive information that doesn't represent Google's views". Three responses are then provided to each question, with users prompted to submit feedback on the usefulness of each answer. Google vice presidents Sissie Hsiao and Eli Collins framed Bard as a complement to Google Search and stated that the company had not determined how to make the service profitable.[49][50][51] Among those granted early access were those enrolled in Google's "Pixel Superfans" loyalty program,[52] users of its Pixel and Nest devices, and Google One subscribers.[53]
Bard is trained by third-party contractors hired by Google, including Appen and Accenture workers, whom Business Insider and Bloomberg News reported were placed under extreme pressure, overworked, and underpaid.[54][55] Bard is also trained on data from publicly available sources, which Google disclosed by amending its privacy policy.[56] Shortly after Bard's initial launch, Google reorganized the team behind Google Assistant, the company's virtual assistant, to focus on Bard instead.[57] Google researcher Jacob Devlin resigned from the company after claiming that Bard had surreptitiously leveraged data from ChatGPT;[58] Google denied the allegations.[59] Meanwhile, a senior software engineer at the company published an internal memo warning that Google was falling behind in the AI "arms race", not to OpenAI but to independent researchers in open-source communities.[60] Pichai revealed on March 31 that the company intended to "upgrade" Bard by basing it on PaLM, a newer and more powerful LLM from Google, rather than LaMDA.[61] The same day, Krawczyk announced that Google had added "math and logic capabilities" to Bard.[62] Bard gained the ability to assist in coding in April, being compatible with more than 20 programming languages at launch.[63][64] Microsoft also began running advertisements in the address bar of a developer build of the Edge browser, urging users to try Bing whenever they visit the Bard web app.[65] Google is working to integrate Bard into its ChromeOS operating system and Pixel devices.[66][67]
Updates
Bard took center stage during the annual Google I/O keynote in May 2023,[68] with Pichai and Hsiao announcing a series of updates to Bard, including the adoption of PaLM 2, integration with other Google products and third-party services, expansion to 180 countries, support for additional languages, and new features.[69] In a stark contrast to previous years, the Google Assistant was barely mentioned during the event.[68] The expanded rollout did not include any nations in the European Union (EU), possibly reflecting concerns about compliance with the General Data Protection Regulation.[70] Those with Google Workspace accounts also gained access to the service.[71] Google attempted to launch Bard in the EU in June, but was blocked by the Irish Data Protection Commission, who requested for a "data protection impact assessment" from the company.[72] In July, Google launched Bard in the EU and Brazil, added support for dozens of new languages, and introduced multiple new personalization and productivity features.[73][74] An invite-only chatroom ("server") on Discord was created in July, consisting of users who heavily use Bard. Over the next few months, the chatroom was flooded with comments questioning the usefulness of Bard.[75]
Reflecting on Bard's launch in an interview with Wired in September, Pichai acknowledged that Google had been "cautious" to release LaMDA because of "the responsibility that comes with getting it right", complimenting OpenAI for ChatGPT's launch and firing back at Nadella's comment about making Google dance.[76] Google released a major update to the chatbot later that month, integrating it into many of its products through "extensions", adding a button to fact-check AI-generated responses through Google Search, and allowing users to share conversation threads.[77] Google also introduced the "Google-Extended" web crawler as part of its search engine's robots.txt indexing file to allow web publishers to opt-out of allowing Bard to scan them for training.[78] Online users later discovered that Google Search was indexing Bard conversation threads on which users had enabled sharing. Google stated that this was an error and quickly moved to rectify the leaks.[79]
In October, during the company's annual Made by Google event in which it announced the Pixel 8 series and the Pixel Watch 2, Hsiao unveiled "Assistant with Bard", an upgraded version of the Google Assistant which was deeply integrated with Bard, following in the footsteps of Amazon's approach with Alexa.[80] When the U.S. Copyright Office solicited public comment on potential new regulation on generative AI technologies, Google joined with OpenAI and Microsoft in arguing that the responsibility for generating copyrighted material lay with the user, not the developer.[81] Accenture contractors voted to join the Alphabet Workers Union in November, in protest of suboptimal working conditions,[82] while the company filed a lawsuit in the U.S. District Court for the Northern District of California against a group of unidentified scammers who had been advertising malware disguised as a downloadable version of Bard.[83][84]
Gemini
Шаблон:Main On December 6, 2023, Google announced Gemini, a multimodal and more powerful LLM touted as the company's "largest and most capable AI model".[85][86] A specially tuned version of the mid-tier Gemini Pro was integrated into Bard, while the larger Gemini Ultra was set to power "Bard Advanced" in 2024.[87][88] The Wall Street Journal reported that Bard was then averaging around 220 million monthly visitors.[89] Google ended its contract with Appen in January 2024,[90] while Bard gained the long-awaited ability to generate images the next month, powered by Google Brain's Imagen 2 text-to-image model.[91]
Reception
Bard received mixed reviews upon its initial release.[92] James Vincent of The Verge found Bard faster than ChatGPT and Bing Chat, but noted that the lack of Bing-esque footnotes was "both a blessing and a curse",[51] encouraging Google to be bolder when experimenting with AI.[93] His colleague David Pierce was unimpressed by its uninteresting and sometimes inaccurate responses,[94] adding that despite Google's insistence that Bard was not a search engine, its user interface resembled that of one, which could cause problems for Google.[95] Cade Metz of The New York Times described Bard as "more cautious" than ChatGPT,[96] while Shirin Ghaffary of Vox called it "dry and uncontroversial" due to the reserved nature of its responses.[97]
The Washington Post columnist Geoffrey A. Fowler found Bard a mixed bag, noting that it acted cautiously but could show Internet-influenced bias.[98] Writing for ZDNET, Sabrina Ortiz believed ChatGPT and Bing Chat were "more capable overall" in comparison to Bard,[99] while Wired journalist Lauren Goode found her conversation with Bard "the most bizarre" of the three.[100] After the introduction of extensions, The New York TimesШаблон:' Kevin Roose found the update underwhelming and "a bit of a mess",[101] while Business InsiderШаблон:'s Lakshmi Varanasi found that Bard often leaned more into flattery than facts.[102]
In a 60 Minutes conversation with Hsiao, Google senior vice president James Manyika, and Pichai, CBS News correspondent Scott Pelley found Bard "unsettling".[103] Associate professor Ethan Mollick of the Wharton School of the University of Pennsylvania was underwhelmed by Bard's artistic ineptitude.[104] The Times later conducted a test with ChatGPT and Bard regarding their ability to handle tasks expected of human assistants, and concluded that ChatGPT's performance was vastly superior to that of Bard.[105] NewsGuard, a tool that rates the credibility of news articles, found that Bard was more skilled at debunking known conspiracy theories than ChatGPT.[106]
See also
References
Further reading
External links
Шаблон:Google LLC Шаблон:Differentiable computing Шаблон:Natural language processing
- ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокChatGPTForbes
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокChatGPTVerge
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокSeriousThreat
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCodeRed
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокPichaiCodeRed
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокLarrySergey
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCode
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокLaMDA
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокLLM
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокUnreleased
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAllHandsCNBC
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAllHandsVerge
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокDeepMind
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокApprenticeBardCNBC
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокApprenticeBardAP
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокInvestorCall
не указан текст - ↑ 17,0 17,1 17,2 Ошибка цитирования Неверный тег
<ref>
; для сносокAnnounceLATimes
не указан текст - ↑ 18,0 18,1 18,2 Ошибка цитирования Неверный тег
<ref>
; для сносокAnnounceWSJ
не указан текст - ↑ 19,0 19,1 19,2 Ошибка цитирования Неверный тег
<ref>
; для сносокAnnounceForbes
не указан текст - ↑ 20,0 20,1 Ошибка цитирования Неверный тег
<ref>
; для сносокPichaiMemo
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокKrawczykFortune
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокKrawczykCNBC
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокBillionDollar
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAtlas
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокEtymologyNYT
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокEtymologyWired
не указан текст - ↑ 27,0 27,1 Ошибка цитирования Неверный тег
<ref>
; для сносокAIBattleVerge
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAIBattleBarrons
не указан текст - ↑ 29,0 29,1 Ошибка цитирования Неверный тег
<ref>
; для сносокCatchUpRecode
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCatchUpInformation
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCatchUpWaPo
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокDance
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокSecretWars
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAIWarsGuardian
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAIWarsRecode
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAIWarsWaPo
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWebbSydney
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWebbWSJ
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWebbReuters
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWebbPCMag
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокMemgen
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокChaos
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокHennessy
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокDogfood
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокRaghavan
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокEthics
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокLayoffs
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокBigBard
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWaitlistNYT
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWaitlistWaPo
не указан текст - ↑ 51,0 51,1 Ошибка цитирования Неверный тег
<ref>
; для сносокWaitlistVerge
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокPixelSuperfans
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокPixelNestOne
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокContractorsBI
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокContractorsBloomberg
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокPublicData
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAssistant
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокDevlinClaims
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокDevlinDenial
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокOpenSource
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокPaLM
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокMath
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCodingReuters
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCodingTC
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокEdge
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокChromeOS
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокPixel
не указан текст - ↑ 68,0 68,1 Ошибка цитирования Неверный тег
<ref>
; для сносокCuriousCase
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокIO2023
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокEUNoLaunch
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокWorkspace
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокEUDelay
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокJulyUpdateBBC
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокJulyUpdateWSJ
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокDiscord
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокGoogle25
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокExtensions
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокExtended
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокLeaks
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAssistantWithBard
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокCopyright
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокUnion
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокMalwareReuters
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокMalwareTime
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокGeminiCNN
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокGeminiCNBC
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокGeminiArs
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокGeminiAP
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокGeminiWSJ
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокAppen
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокImagen
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокReviews
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокExperimentation
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокVergeReview
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокNotSearch
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокNYTReview
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокVoxReview
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокRightWrongWeird
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокBadWay
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокBizarre
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокErratic
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокFlattery
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносок60Minutes
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокTesters
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокHumanAssistant
не указан текст - ↑ Ошибка цитирования Неверный тег
<ref>
; для сносокConspiracy
не указан текст