It turns out that Threads\u2019 recently introduced keyword-searching abilities won\u2019t work for all topics. The app is currently blocking searches for a number of \u201cpotentially sensitive\u201d words, including \u201cvaccines,\u201d \u201ccovid,\u201d and other variations of words that have previously been linked to misinformation on Meta\u2019s platform.<\/p>\n
The limits, which were first reported by The Washington Post<\/ins><\/em><\/a>, <\/em>are an apparent attempt to prevent controversial content from spreading on Meta\u2019s newest app. The company has blocked a number of covid and vaccine-related terms, including \u201ccovid,\u201d \u201ccoronavirus,\u201d \u201ccovid-19,\u201d \u201cvaccines\u201d and \u201ccovid vaccines,\u201d as well as other terms associated with potentially unsavory content like \u201cgore,\u201d nude,\u201d and \u201csex.\u201d<\/p>\n <\/p>\n The company confirmed it was blocking searches in a statement to The Post<\/em>, calling it a temporary measure. \u201cThe search functionality temporarily doesn\u2019t provide results for keywords that may show potentially sensitive content,\u201d a spokesperson said. Adam Mosseri, the head of Instagram who also oversees Threads, tweeted<\/ins><\/a> that the company was \u201ctrying to learn from last [sic] mistakes and believe it’s better to bias towards being careful as we roll out search.\u201d<\/p>\n Meta\u2019s history shows the company has good reasons to be cautious about search on Threads. Instagram search has been widely criticized as a vector for misinformation and its ability to lead users down conspiratorial rabbit holes. The app\u2019s search was particularly weaponized<\/ins><\/a> during the early days of the pandemic, when it promoted conspiracy-touting anti-vax accounts in its top results for simple queries like \u201cvaccine\u201d and \u201c5g.\u201d<\/p>\n At the same time, it\u2019s telling that Meta is now opting to block all searches containing \u201cpotentially sensitive\u201d keywords, even posts that don\u2019t contain rule-breaking content. It\u2019s also a notably more aggressive approach than the social media company has taken in the past.<\/p>\n While Meta has previously limited search functionality on both Facebook and Instagram, the company has typically intervened when search terms were explicitly linked to rule-breaking content, like specific hashtags related to QAnon. In other cases, the company has worked to clean up search results for topics like vaccines, and pushed in-app PSAs directing users to official resources.<\/p>\n As The Washington Post<\/em> points out, the result of the total block on covid-related search terms is that users are also prohibited from looking for information, resources and conversations that don\u2019t break the platform\u2019s rules, which could be a barrier to those seeking advice or credible information from experts.<\/p>\n Meta\u2019s caution also underscores just how quickly the company rushed the development of Threads. The app was released just five months<\/ins><\/a> after a small group of Instagram engineers started working on the project. The quick turnaround meant that Threads launched with several basic features missing<\/ins><\/a> from the service. And while Meta has said Threads has the same safety policies of Instagram, it hasn\u2019t disclosed many details about its plans to moderate content on the Twitter-like app, where posts look and feel very different.<\/p>\n This article originally appeared on Engadget at https:\/\/www.engadget.com\/meta-is-blocking-potentially-sensitive-topics-from-threads-search-231028963.html?src=rss
It turns out that Threads\u2019 recently introduced keyword-searching abilities won\u2019t work for all topics. The app is currently blocking searches for a number of \u201cpotentially sensitive\u201d words, including \u201cvaccines,\u201d \u201ccovid,\u201d and other variations of words that have previously been linked … Continue reading
\n
\nSource: Engadget – Meta is blocking \u2018potentially sensitive\u2019 topics from Threads search<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"