Reading view

There are new articles available, click to refresh the page.

Meet Mercy and Anita – the African workers driving the AI revolution, for just over a dollar an hour

Social media content and AI training data are processed in outsource centres in the global south, where long hours, low pay and exposure to disturbing material are the norm

Mercy craned forward, took a deep breath and loaded another task on her computer. One after another, disturbing images and videos appeared on her screen. As a Meta content moderator working at an outsourced office in Nairobi, Mercy was expected to action one “ticket” every 55 seconds during her 10-hour shift. This particular video was of a fatal car crash. Someone had filmed the scene and uploaded it to Facebook, where it had been flagged by a user. Mercy’s job was to determine whether it had breached any of the company’s guidelines that prohibit particularly violent or graphic content. She looked closer at the video as the person filming zoomed in on the crash. She began to recognise one of the faces on the screen just before it snapped into focus: the victim was her grandfather.

Mercy pushed her chair back and ran towards the exit, past rows of colleagues who looked on in concern. She was crying. Outside, she started calling relatives. There was disbelief – nobody else had heard the news yet. Her supervisor came out to comfort her, but also to remind her that she would need to return to her desk if she wanted to make her targets for the day. She could have a day off tomorrow in light of the incident – but given that she was already at work, he pointed out, she may as well finish her shift.

Continue reading...

💾

© Photograph: Yannick Tylle/Getty Images

💾

© Photograph: Yannick Tylle/Getty Images

FarmVille at 15: how a cutesy Facebook game shaped the modern internet

On its 15th anniversary, the creators of FarmVille reflect on the compulsive cartoon farm sim that paved the way for a data-driven world

Facebook users of a certain age may remember a particularly forlorn farm animal popping up in their feeds during the platform’s heyday. The lonely cow would wander into FarmVille players’ pastures with its face twisted into a frown and its eyes shimmering with tears. “She feels very sad and needs a new home,” an accompanying caption read, asking you to adopt the cow or message your friends for help. Ignore the cow’s plea and it would presumably be left friendless and foodless. Message your friends about it, and you’d be accelerating the spread of one of the biggest online crazes of the 2010s.

Released 15 years ago, FarmVille was nothing short of a phenomenon. More than 18,000 players gave it a go on its first day, rising to 1 million by its fourth. At its peak in 2010, more than 80 million users logged in monthly to plant crops, tend animals and harvest goods for coins to spend on decorations. Celebrities professed their obsession, McDonald’s created a farm for a promotion, and long before artists released music on Fortnite, Lady Gaga debuted songs from her sophomore album through the cartoon farm sim. Not bad for a game that was stitched together in five weeks.

Continue reading...

💾

© Photograph: David J Green/Lifestyle/Alamy

💾

© Photograph: David J Green/Lifestyle/Alamy

CocoaPods Vulnerabilities Could Hit Apple, Microsoft, Facebook, TikTok, Snap and More

CocoaPods vulnerabilities Apple

CocoaPods vulnerabilities reported today could allow malicious actors to take over thousands of unclaimed pods and insert malicious code into many of the most popular iOS and MacOS applications, potentially affecting "almost every Apple device." E.V.A Information Security researchers found that the three vulnerabilities in the open source CocoaPods dependency manager were present in applications provided by Meta (Facebook, Whatsapp), Apple (Safari, AppleTV, Xcode), and Microsoft (Teams); as well as in TikTok, Snapchat, Amazon, LinkedIn, Netflix, Okta, Yahoo, Zynga, and many more. The vulnerabilities have been patched, yet the researchers still found 685 Pods “that had an explicit dependency using an orphaned Pod; doubtless there are hundreds or thousands more in proprietary codebases.” The widespread issue is further evidence of the vulnerability of the software supply chain. The researchers wrote that they often find that 70-80% of client code they review “is composed of open-source libraries, packages, or frameworks.”

The CocoaPods Vulnerabilities

The newly discovered vulnerabilities – one of which (CVE-2024-38366) received a 10 out of 10 criticality score – actually date from a May 2014 CocoaPods migration to a new 'Trunk’ server, which left 1,866 orphaned pods that owners never reclaimed. The other two CocoaPods vulnerabilities (CVE-2024-38368 and CVE-2024-38367) also date from the migration. For CVE-2024-38368, the researchers said that in analyzing the source code of the ‘Trunk’ server, they noticed that all orphan pods were associated with a default CocoaPods owner, and the email created for this default owner was unclaimed-pods@cocoapods.org. They also noticed that the public API endpoint to claim a pod was still available, and the API “allowed anyone to claim orphaned pods without any ownership verification process.” “By making a straightforward curl request to the publicly available API, and supplying the unclaimed targeted pod name, the door was wide open for a potential attacker to claim any or all of these orphaned Pods as their own,” wrote Reef Spektor and Eran Vaknin. Once they took over a Pod, an attacker would be able to manipulate the source code or insert malicious content into the Pod, which “would then go on to infect many downstream dependencies, and potentially find its way into a large percentage of Apple devices currently in use.” Earlier in 2014, a change was committed to the CocoaPods ‘Trunk’ source code implementing MX record validation for registered emails. The changes created a new attack path that was identified by analyzing the registration flow, resulting in the CVE-2024-38366 vulnerability. The changes created a new verification process for the user-provided email address using the third-party Ruby gem package rfc-822, which can be attacked in a few ways, potentially resulting in attacks that could “dump pod owners’ session tokens, poison client’s traffic or even shut down the server completely.” In CVE-2024-38367, the researchers found they could spoof XFH headers to engineer a zero-click account takeover by defeating email security boundaries. “Using this method, we managed to take over the owner accounts of some of the most popular CocoaPods packages,” the researchers said. “Potentially we could have used these accounts for highly damaging supply chain attacks that could impact the entire Apple ecosystem.”

DevOps Teams: Get to Work

While the vulnerabilities have been patched, the work for developers and DevOps teams is just getting started. Developers and DevOps teams that have used CocoaPods in recent years - particularly before October 2023 - "should verify the integrity of open source dependencies used in their application code,” the E.V.A researchers said. “The vulnerabilities we discovered could be used to control the dependency manager itself, and any published package.” Downstream dependencies could mean that thousands of applications and millions of devices were exposed over the last few years, and close attention should be paid to software that relies on orphaned CocoaPod packages that do not have an owner assigned to them. Developers and organizations should review dependency lists and package managers used in their applications, validate checksums of third-party libraries, perform periodic scans to detect malicious code or suspicious changes, keep software updated, and limit use of orphaned or unmaintained packages. "Dependency managers are an often-overlooked aspect of software supply chain security," the researchers wrote. "Security leaders should explore ways to increase governance and oversight over the use these tools."

Zuckerberg Disses Closed-Source AI Competitors as Trying To 'Create God'

Mark Zuckerberg has criticized the notion of a singular, dominant AI in a new interview. He argued against the idea of AI technology being "hoarded" by one company, taking aim at unnamed competitors who he suggested view themselves as "creating God." Zuckerberg advocated for open-source AI development, emphasizing the need for diverse AI systems reflecting varied interests. He likened the future AI landscape to the current ecosystem of phone apps, content creators, and businesses, where no single entity dominates. Meta announced early U.S. tests of AI Studio, software enabling creators to build AI avatars for Instagram messaging. These AIs will be clearly labeled to avoid confusion. Zuckerberg stressed the importance of empowering many to experiment with AI, stating, "That's what culture is, right? It's not one group of people getting to dictate everything for people."

Read more of this story at Slashdot.

SCOTUS nixes injunction that limited Biden admin contacts with social networks

SCOTUS nixes injunction that limited Biden admin contacts with social networks

Enlarge (credit: Christopher Furlong / Staff | Getty Images News)

On Wednesday, the Supreme Court tossed out claims that the Biden administration coerced social media platforms into censoring users by removing COVID-19 and election-related content.

Complaints alleging that high-ranking government officials were censoring conservatives had previously convinced a lower court to order an injunction limiting the Biden administration's contacts with platforms. But now that injunction has been overturned, re-opening lines of communication just ahead of the 2024 elections—when officials will once again be closely monitoring the spread of misinformation online targeted at voters.

In a 6–3 vote, the majority ruled that none of the plaintiffs suing—including five social media users and Republican attorneys general in Louisiana and Missouri—had standing. They had alleged that the government had "pressured the platforms to censor their speech in violation of the First Amendment," demanding an injunction to stop any future censorship.

Read 30 remaining paragraphs | Comments

❌