Grindr pays £26M to settle UK privacy class action
Apple is facing a £2 billion ($2.7 billion) London lawsuit brought on behalf of app developers over its app tracking rules, with the iPhone maker accused of abusing its power to unfairly impose greater restrictions on third parties.
[…]
Lawyers bringing the new lawsuit against Apple, though, say the feature imposed stricter requirements on third-party app developers than on Apple’s own services, giving its advertising ecosystem a competitive advantage.
Via Ben Lovejoy:
The latest lawsuit has an interesting twist: it’s being brought by Ann Pope, who was previously a senior official with the regulator behind today’s case.
The company told Reuters it was “bound by the exact same requirements as all developers.”
However, regulators across Europe including in France, Italy and Poland have investigated ATT. Germany’s competition regulator, the Federal Cartel Office, last month determined that Apple was favoring its own apps over those from external developers.
The EU is saying “you’re big enough that you have to treat your other business models like third parties” and Apple replies with “but we know we’re solid, so that makes no sense!”
Previously:
Apple has agreed to make changes to its App Tracking Transparency feature in Germany, according to the country’s competition regulator.
[…]
In Germany, Apple has agreed to remove “possibly discouraging symbols and wording” from the App Tracking Transparency prompt, the regulator said. Apps will also be “given more scope to explain to users what significance personalized advertising has for their offering and their business model,” and the “freedom to combine the consent request required by Apple with the consent requests required under data protection law.”
The FCO’s objection appears to be that Apple’s existing prompt is making app tracking sound scarier than it really is. The iPhone maker will make eight changes in order to address this – including removal of the word “track.”
The regulator helpfully offers an illustration of the differences between these prompts on the fourth page of its FAQs (PDF) about the case. There are many things they say could be deterrents in the App Tracking Transparency dialog, and I do not think Apple would deny that they are suggesting that users opt out of tracking. The definition of “tracking” Apple uses is self-serving, which would not matter so much if it did not also have a parallel desire to grow its advertising business.
[…]
A particularly damning finding in that comparison, to my eyes, is the way Apple puts “Ask App Not to Track” as the topmost button in the App Tracking Transparency dialog, but puts the option to “Turn Off Personalised Ads” at the bottom of it its own advertising prompt.
Previously:
A US federal judge has sided with Google, ruling that the company will not have to sell its online advertising exchange (previously known as AdX). The US Department of Justice (DOJ) sought this remedy in the long-running ad tech antitrust trial, which Google lost in 2025. However, the remedies imposed upon Google for that loss are shaping up to be minimal.
[…]
While divesting the ad exchange would have been the most serious penalty, the government also asked for fines and court-ordered changes to Google’s business practices. It’s likely that the DOJ will get a lot of that, but we don’t know the specifics yet. Judge Leonie Brinkema has sealed the order for 14 days, giving the parties a chance to request redactions.
[…]
After all these years of hearings, appeals, and decisions, Google’s market power will remain largely unchanged going forward.
Previously:
The settlement between Google and Epic that aimed to put to rest the companies’ long-running antitrust battle is being withdrawn, and that means third-party app stores are coming to the Play Store.
[…]
While Apple suffered little penalty in its Epic case, Google was tripped up by its anti-competitive management of the supposedly open Android ecosystem. Google used its market position to discourage device makers from promoting or pre-loading non-Google app stores and attempted to hide that conduct. The remedies set by Judge James Donato included lower fees, mirroring Google Play apps in other stores, and most vitally, placement of alternative app stores in Google Play.
[…]
Google and Epic were set to return to court on July 16 to argue in favor of the settlement. However, the writing may have been on the wall. In a recent expert analysis provided to the court, MIT economics professor Nancy Rose noted that the settlement was “unlikely to enable Google Play’s potential competitors to overcome their long-standing network-effect disadvantage in a timely manner.”
[…]
Under the terms of Judge Donato’s original injunction, these stores will have access to the full catalog of Google Play apps by default. […] Google will also require approved stores to block malware, respect intellectual property, and include mechanisms to update and uninstall apps.
My guess is that all the big app developers will opt out of this. Games, though, maybe not?
Previously:
Liu downloaded the circuit schematic from Apple in March, two months after he left the company. Liu used the schematic to run a simulation using electrical engineering tool LTspice, and then messaged people telling them he ran the simulation for power conversion development work.
[…]
Liu used the Apple schematic on a Mac mini that later synced to the MacBook he took from Apple, which is why Apple knows about it. Apple now wants to investigate the Mac mini and other devices Liu still has in his possession.
Apple says the “shocking evidence” is proof that its trade secrets are in active use and evidence is being destroyed, which is why expedited discovery is needed.
The first point seems really bad for OpenAI. On the fourth point, I’m not sure what Apple is alleging here — I think they’re alleging that Liu took an Apple internal engineering app with him over to OpenAI?
William Gallagher and Mike Wuerthele (MacRumors):
OpenAI has responded to Apple’s latest filing about the theft of confidential information, by filing its own rebuttal which again accuses the company of trying to stop employees leaving. According to Reuters, OpenAI is now also calling out Apple for being behind on AI.
[…]
“[Employees] can leave a company like Apple that has struggled to adopt AI and move to an exciting startup that builds innovative products,” says OpenAI in its new filing. “Apple may not like those choices. But it cannot claim those choices are unlawful, and it cannot use its own sloppy procedures to blame others for its own mess.”
On the face of it, the evidence Apple provided yesterday does appear damning. OpenAI doesn’t seem to be denying that confidential Apple information was used by the company, but rather claiming that the iPhone maker failed to properly protect it.
It sounds like there’s a lot of evidence against Chang Liu, but Apple is suing OpenAI.
Previously:
From baby-monitors to smart watches, from apps to computer programs, connectable hardware and software are omnipresent in our daily lives. Less apparent to many users is the security risk such products may present.
The Cyber Resilience Act (CRA) aims to safeguard consumers and businesses buying software or hardware products with digital elements. The CRA addresses the inadequate level of cybersecurity in many products, and the lack of timely security updates. It also tackles the challenges consumers and businesses currently face when trying to determining which products are cybersecure and in setting them up securely, making it easier to identify hardware and software with the proper cybersecurity features.
The CRA introduces mandatory cybersecurity requirements for manufacturers, covering the planning, design, development and maintenance of such products. These obligations must be met at every stage of the value chain. The CRA also requires manufacturers to handle vulnerabilities during the lifecycle of their products. Some products of particular relevance for cybersecurity may need to undergo a third-party assessment by a notified body before they are sold on the EU market.
Via Ron Elemans:
[…] the extremely heavy future requirements that are due on December 11, 2027.
For example, free security updates must be provided for at least five years without changes regarding the operating system requirements—a period that resets every time someone purchases an app of a particular version.
Here’s the text of it, which was approved in 2024.
Previously:
Richard Speed (Hacker News 3):
XCancel’s home page now contains some minimal text stating: “On Monday 24th August at 8 PM EST, we received at [sic] letter from X Corp. asking to cease and desist the service XCancel.”
It says the service has been halted “until further notice.”
[…]
Nitter provided a way for users to read posts on X without requiring an account. There was no JavaScript or ads, a user’s IP could not be tracked, and it was generally a good deal snappier than the official X client, just read-only. It was the service behind platforms such as XCancel.
The only thing surprising about this is how long it took.
Companies like X and Meta are very happy to scrape the web at unprecedented scale and without permission, but have zero tolerance for the same to be done to them by, in effect, individual users. That is not because they are protective of the creative works users have contributed to these platforms. It is simply because users are not trusted to use the platforms. X does not permit third-party readers, and neither does Instagram, because their value does not come from us using these services as we wish, but from how they dictate we must.
Previously:
Update (2026-09-07): There are currently twelve working Nitter instances (Hacker News).
Following legal advice, the Nitter project will continue.
Update (2026-09-16): XCancel (via John Gruber, Hacker News):
Unfortunately, due to a new development in the ongoing legal proceedings, we are required to suspend this service again until further notice. We can’t share more details.
xsukax (via Brent Simmons):
xsukax X RSS Generator fetches publicly accessible X profile HTML, extracts posts and media, stores them locally, and exposes the results as standards-compatible RSS feeds that can be consumed by RSS readers, automation platforms, monitoring systems, and other feed-aware applications.
Apple has again failed to earn a stay for fee calculations in its ongoing legal fight with Epic Games. Apple's case will be heard by the Supreme Court in the term that begins in October, and Apple asked the U.S. District Court for the Northern District of California to pause proceedings until then, but the court said no [PDF].
U.S. Supreme Court Justice Elena Kagan today granted Apple a one-day stay in its legal fight with Epic Games, giving Apple more time to outline the fees it wants to charge developers for linking out to purchase options on the web.
Apple tried to freeze the entire thing while they appealed to the Supreme Court – and the Supreme Court denied the freeze. But they didn’t deny hearing the case – yet. That’s why they’re pausing the proceedings for now (after Judge Gonzalez Rogers denied the same request), while they weigh Apple’s appeal. But before they do that, they’re basically likely to decide today – again, it was just a 24-hour delay – whether they should grant a longer stay. Presumably if the court thinks they’re unlikely to hear Apple’s appeal, they may not grant that longer stay. Or if they think Apple filing their number won’t harm their business, they’ll let it proceed. But Apple will argue that if the longer stay isn’t granted, it will cause major harm to their business because again, it will effectively end the App Store cut as we know it.
Juli Clover (Engadget, The Verge):
Apple today submitted a court-ordered proposal outlining the commission it believes is reasonable to collect from U.S. apps that link to purchase options outside of the App Store.
Apple is asking for half of its commission on standard apps, so apps that would pay 30 percent for an in-app purchase would pay 15 percent when linking to a web purchase option. Small Business Program participants that would normally pay 15 percent would pay 5 percent.
[…]
The appeals court suggested the commission could be limited to the direct costs of facilitating link-outs, and under that approach, the fee would be zero. Apple says a zero commission would not reflect the value that it provides developers, and its suggested commission gives it fair compensation for the App Store platform.
[…]
The district court will now evaluate Apple’s fee proposal and hear a response from Epic Games , and Apple will need to implement the fee the court sets.
Unlike cost-only based commissions, Apple’s revenue-based commissions incentivize continued investment. Apple charges developers a $99 annual fee for the Apple Developer Program. May 17, 2021 Trial Tr. at 2762:21–2763:13. This modest fee—designed to prevent fraud and expressly not intended to compensate Apple for the use of its IP-protected tools, technologies, and services (id.)—allows developers to build apps using Apple’s offerings and deliver experiences to iOS and iPadOS users worldwide.
The annual developer fee is nominal. Apple relies on percentage-based commissions to recoup and profit from its investments. See id. ¶¶ 87–93. Apple is incentivized to invest in IP- protected tools, technologies, and services that generate revenue for developers (and benefit users).
[…]
Dr. Carlton explains that “reduc[ing] Apple’s incentive to invest and provide the technology and services that benefit users and developers” would harm users and developers, as well as Apple.
I like the part where Apple’s expert argues that its normal commission rates are so high that it would still be profitable for developers to pay the proposed linking commissions on top of what they would pay to Stripe or Paddle. In other words, paying Apple for “IP” almost twice what it admits the other companies charge for “full-service, turnkey payment processing.”
If the point [of the $99] is just to prevent fraud, why do we need to keep paying $99 yearly FOREVER? Is 10 years not enough to prove I’m not a fraud?!?
If the fee doesn’t help pay for Apple IP, then it’s even more blatantly unfair that a minority of apps have to pay for ALL apps to access Apple IP. Free apps, no matter how big or how much $ they make via ads, get access to Apple IP from OUR REVENUE CUT, and not even their $99 counts.
That’s what that enormous hardware margin from customers is already supposed to be paying for — Apple IP! In the early 00’s, I gladly paid the “Apple tax” (PowerBook G4) to get access to the Mac OS X software/ecosystem, including all the Unix and dev tools. I’m not sure why anyone thinks that double-dipping is fine on all the non-Mac platforms, App Store or not.
Jeff Johnson (2):
Schiller’s [previous] testimony about the previous program is extremely misleading, because the new program began in 2008 at the same time as the App Store, so there was no previous iOS developer program, and Mac Developer ID did not begin until 2012, so Apple Developer Program membership was not actually required to distribute Mac apps!
Fourth, it appears that Steve Jobs was wrong: the $99 fee didn’t prevent developers from flooding the App Store with a lot of junk.
I want to quote another remarkable passage from Schiller’s testimony, again with questions from Apple’s own lawyer.
Q. And Mr. Jobs says, “And also just to make it a little clearer, we don’t intend to make money off the App Store. I mean, we don’t make a lot of money off iTunes, and the split with the music companies is about the same, so in the case of the iTunes Music Store, we give all the money to the content owners, and we are basically giving all the money to the developers here. And if that 30 percent of it pays for running the store, well, that will be great, but we just want to create a very efficient channel for these developers to reach every single iPhone user.” Is that a statement that Mr. Jobs made back in March 2008?
A. He did.
[…]
I won’t quote the following passage in which Schiller testifies about his internal email suggesting that Apple limit itself to $1 billion per year in profit from the App Store, hand-waving away the suggestion as merely “spurring conversation.” Of course the email also seems to contradict Schiller’s (absurd) testimony that Apple does not specifically calculate profit from the App Store, only company-wide profit. Apple’s public financial statements also appear to contradict Schiller’s claims.
Previously:
Update (2026-08-20): Marcus Mendes:
On the same day, Apple submitted another motion, asking Judge Gonzalez Rogers to order the parties to attend a settlement conference.
[…]
Epic has now responded to Apple’s motion, stating that although the company “has been, and remains today, willing to entertain any direct approach from Apple with a serious settlement proposal that would introduce competition and benefit all developers,” it “does not believe the prospects of such settlement would be meaningfully advanced through referral to a settlement conference at this juncture.”
Update (2026-09-03): Marcus Mendes:
In addition to the proposal itself, Apple submitted supporting expert reports, alongside a request to seal portions of those filings containing financial data, link-out adoption estimates, developer survey results, and other information Apple considers commercially sensitive.
Epic has now filed an opposition to Apple’s request, arguing “Apple again seeks to conceal information from the public and unnecessarily hamper proceedings.”
Anthropic will embed watermarks in the text and files generated by future models it launches in the EU, as part of its effort to comply with content and transparency rules in the bloc’s AI Act.
[…]
The move may further amplify the appeal of open weight models and alienate Claude customers, who don’t necessarily want consumers of their AI-generated content to know its provenance.
[…]
Anthropic itself is already hedging about the utility of its marking method, noting that detected marks are not conclusive evidence that Claude produced the content and that the absence of marks cannot guarantee that AI wasn’t involved in the creation of a particular piece of content.
Claude models launched in the EU on or after August 2, 2026 will support machine-readable marking at launch. Generated text will carry embedded watermarks, and generated files will include digitally signed provenance metadata where supported.
[…]
Marks will apply to output from supported Claude models across Claude Platform (API), Claude, Claude Code, Claude Cowork, and Claude Tag, and wherever Claude is offered, worldwide. Some platforms or features may not support certain marking types.
[…]
We’ll support users and other third parties to detect Claude’s marks, as the Code requires, and we’ll share details in forthcoming documentation.
Anthropic is claiming this is for compliance with an EU law but that “Marking will apply to output from supported models wherever Claude is offered, worldwide.”
This is infuriatingly opaque. I won’t speak to the “signed provenance metadata” they say they’ll be embedding in generated files like PDFs, SVGs, PNGs, and JPEGs. That’s important but it’s complex. Plain text is simple. A string of text is just one character followed by another. I presume that Claude is going to start “embedding” invisible characters/byte sequences between visible characters? What they’re claiming to do here seems impossible, frankly, and anything they attempt to embed invisibly is going to cause immediate problems.
[…]
If the “watermark” is not comprised of invisible characters but rather visible ones, how in the world does this jibe with their claim that it’s “imperceptible”? (This Reddit thread claims that’s how it will work — “It’s a form of steganography where the model subtly biases its word choice to create a statistical pattern that can be detected later.” How in the world can that be squared with “it doesn’t change the meaning, quality, or readability”?) And any sort of semantic detection like this is going to cause false-positive problems.
Previously:
Update (2026-08-17): Anthropic provides more details:
Watermarking won’t be specific to Claude. As of August 2, the EU requires AI providers serving its market to mark AI-generated content. Other major model developers have signed the same Code of Practice and will be implementing their own watermarks.
[…]
In internal testing, we’ve seen no impact of watermarking on the content, level of creativity, or readability of Claude’s text. In the SynthID-Text paper, which introduced the technique we use, Google DeepMind tested this impact by serving a model that used watermarking to a portion of their Gemini traffic and comparing thumbs-up and thumbs-down ratings. They found no statistically significant differences from the unwatermarked model. And in a controlled study, human raters comparing watermarked and unwatermarked answers side-by-side saw no difference in quality.
[…]
There are limitations to the effectiveness of watermarking. Using our key, one can only answer the question “What is the likelihood this was partly written by Claude?” It doesn’t confirm whether the text was human-written, and it can’t tell whether the text was written by a different AI (even if that other AI uses watermarking, it would have a different key; it might also use a different watermarking method altogether). Detecting a watermark also doesn’t work well on small samples, where there are fewer word choices and thus less information to go on. As a passage increases in length, confidence about Claude’s involvement increases too.
Watermarking is sparser on factual passages where there are fewer choices that can be made without decreasing the accuracy of the text. […] For the same reason, code—which in very many cases has to be exact—has generally less watermarking than some other forms of text.
John Gruber (Mastodon, Bluesky, Hacker News):
I initially guessed “invisible characters” not because I didn’t think of the semantic word-choice technique, but because I was a fool who took Anthropic at its word in their description of what they would do.
[…]
They say “imperceptible” and “doesn’t change the meaning, quality, or readability”. Their words. Not almost imperceptible. Not slightly changes the meaning, quality, or readability.
There seems to be a slight of hand here, where Google studied whether humans saw a difference in quality but then Anthropic claimed that there was no difference in meaning. Changing words will almost always change the meaning. Perhaps not in an important way, but a change is a change. Pretending otherwise is offensive to a writer. The response to this line of argument seems to be that LLMs already have randomness and that the marking changes will be within the level noise that’s already there. To me, this presents a pessimistic view of the capabilities of LLMs, contrary to Anthropic’s normal claims. The Google study was published in 2024 and didn’t test Claude. The models have changed a lot since then, but they are assuming that the precision hasn’t advanced enough to be affected, nor will it in the future. Or that when there is a tension between watermarking and quality they will pick the former. And perhaps you won’t be able to tell because everyone else will be watermarking, too.
But the very best description of the general idea behind the technique is an interactive essay by James Padolsey, “How AI Text Watermarking Works”.
[…]
This isn’t just about text one might generate with the intention of passing it off as their own natural work. This isn’t even about LLM proofreading of work written by hand. Anthropic is saying that all new Claude models are going to adulterate every single bit of text longer than 200 tokens (~150 words) they generate, including everything it presents to its users to read. So even in a private conversation between a user and Claude, which will never be read by anyone other than the user, Claude will begin making word choices in the name of marking its output in statistically predictable ways rather than maximizing clarity and precision.
[…]
Taken literally, compliant LLM terms of service must forbid users from rephrasing the output from models that comply with this regulation, because the word choices are the marks. But it’s not the European Union that is trying to impose their absurd, impractical, witch-hunt-fueling regulation on the entire world. That falls on Anthropic.
Complying with this, particularly with regard to text, is only going to create problems for honest users. Dishonest users attempting to pass off AI-generated text as their own writing (students, employees, whoever) will simply circumvent detection through non-compliant AI paraphrasing tools.
I don’t love that checking for a watermark requires submitting the text to the AI provider, and all you get back is an opaque result with no way to verify it.
James Padolsey (via John Gruber):
The move is Anthropic’s response to Article 50(2) of the EU AI Act, which requires providers to ensure that outputs are “marked in a machine-readable format and detectable as artificially generated or manipulated”.
[…]
The Act exempts standard editing, but many legitimate assistive uses require more substantial rewriting while leaving the ideas, judgment and responsibility with the human. The same thought that led to this law could have applied to calculators at the time of their inception, had their outputs revealed themselves through artefacts. Thankfully, a sum borne of the brain is treated no differently from one produced by a calculator. Likewise with spellcheckers. To make assistance suspect only once the tool becomes capable enough to compose a whole sentence is not a principled boundary. It is a moral premium placed on difficulty itself.
Anthropic has nevertheless chosen a blanket, model-level implementation that appears broader than the law’s minimum requirement. That may be convenient compliance engineering, but it discards distinctions the law expressly attempted to preserve. The result is a signal broad enough to implicate harmless and assistive use, yet fragile enough to be removed by a motivated person through substantial recomposition. It risks concentrating suspicion on ordinary and assistive users while remaining weakest against deliberate deception.
Update (2026-08-20): See also:
Without getting into the weeds, I still think Anthropic’s claim of their being no change in the meaning, quality, or readability is not accurate, using the plain meanings of those terms. If you read the papers, there are ways of ensuring that the frequencies of individual tokens or sequences of them are not affected in aggregate. But this is a different claim, and Anthropic does not specify which tradeoffs they’ve chosen there. I’m willing to grant that they can make the effect very small.
At this point, I think the most interesting question is, what will be the effects of these watermarks?
AI watermarking is security theater. There is absolutely nothing to prevent people from removing any possible watermark in text, images, video or other data. There is no way to prevent false positives, or false negatives, in detectors, either. It’s all superficial nonsense.
I find it interesting to be able to test a particular passage of text, but what am I supposed to do with that information? Even without watermark removal, a negative for a given model doesn’t tell you whether another model was used. And I’m uncomfortable with convicting someone based on a watermark given that false positives are possible and independent verification is not.
I asked Gemini about the benefits, and it said:
Regulatory Compliance and Policy
- Legal adherence: Helps major tech platforms satisfy emerging mandates requiring automated systems to label machine-generated media.
- Ecosystem tracking: Gives platforms and enterprises a high-level telemetry signal to monitor the spread of synthetic content across public channels.
Triage and Risk Mitigation
- Mass moderation: Assists automated filters in flagging bulk, unvetted bot content or spam networks where statistical trends matter more than single-file perfection.
- Provenance auditing: Provides an extra layer of metadata for digital media archives, helping investigators spot obvious clusters of AI-generated assets.
In other words, it’s not so much about individual pieces of content.
Update (2026-08-24): John Gruber:
Also, more and more, I do think this has little to do with the EU regulation and everything to do with Anthropic and Google wanting to watermark the text that Claude and Gemini generate for their own purposes, to identify text to avoid training future models on to avoid model collapse/AI inbreeding.
See also: Accidental Tech Podcast.