"Claudia" (https://claudia.gallery/wiki/) can also be used to explain the various reasons this sucks, and someone did.
> Claudia explains the hazards of believing she is either sentient or infallible, the myopia of AI utopianism, and how gatekeeping and the "asymmetries of fluency" can be wielded against an unsuspecting world.
The difference is that Apple Support Community has always been actively and objectively bad, rife with incorrect and outdated information. Anything mining it for answers will provide worse answers.
You're not wrong. As much as I deeply respect the mission and accomplishments of Internet Archive, keeping it discoverable by search engines and LLMs is a net-negative IMHO.
"They were full of people asking questions and not getting useful answers, with many responses given by users who were more motivated to gain karma in the forum’s user-ranking system than to help." — Jason Snell (https://sixcolors.com/link/2026/11/ding-dong-the-apple-suppo...)
Note that Archive Team is not the same as the Internet Archive. They're related and Archive Team stuff ends up in the IA but they're separate and have different missions.
> As much as I deeply respect the mission and accomplishments of Internet Archive, keeping it discoverable by search engines and LLMs is a net-negative IMHO.
But Internet Archive isn't discoverable by search engines? I think it isn't anyway, I've literally never seen a Wayback Machine link in Google so I assume it's on purpose.
There's no robots.txt on web.archive.org and it seems to come up with you use `site:` modifiers, so I think it's just ranked very low. Probably on purpose but probably not on IA's part.
I agree that unweighted "solutions" from random (and often incorrect) people with good intentions may well lead many down wrong paths... but that having those paths preserved and clearly described is of value in and of itself.
Are you seriously suggesting that we curate the entire internet for misinformation, just so that the LLMs can indiscriminately crawl it all? Would it not make more sense for LLMs not to be so trusting?
As I understand it (and count that I will be proven wrong if not), Strands Decider is an LLM, just a discriminative example instead of a generative one.
"Transformative nature" is just one of several factors that go into deciding if something is fair use. Also, fair use is decided case by case in the courts, so one can't say that "training LLMs on copyrighted materials is fair use".
Model vendors know this isn't fair use, given that they're self-censoring the training and/or generation of copyrighted materials by entities big enough to hurt them. As usual, the rest of us have no recourse other than bend over and take it.
> Also, fair use is decided case by case in the courts,
> Model vendors know this isn't fair use
Pick a lane dude. Either it's possible for us to make legal analysis and best guesses or uhh "we have no idea it's up for the courts to decide!"
Yes we know it's up for the courts to decide. And people are making argument about what those courts will do.
That's how legal analysis works.
Yes, it is perfectly possible to talk about fair use and follow existing guidelines on it and the government has already make statements that this stuff is likely transformative.
> …the government has already make statements that this stuff is likely transformative.
Incorrect.
"…the [Copyright] Office rejects two common arguments about the transformative nature of AI training. As noted above, some argue that the use of copyrighted works to train AI models is inherently transformative because it is not for expressive
purposes. We view this argument as mistaken. […] Nor do we agree that AI training is inherently transformative because it is like human learning. To begin with, the analogy rests on a faulty premise, as fair use does not excuse all human acts done for the purpose of learning." — Copyright and Artificial Intelligence,
Part 3: Generative AI Training, United States Copyright Office
And again, the degree to which training and output is transformative is just one of several factors that courts consider when deciding if something is protected as fair use.
Out of curiosity, what prompted you to make this when agent-browser.dev and lots of other alternatives already exist? "Because it's fun" is absolutely a legitimate answer, but I couldn't tell from the README what I might be missing.
It can, but it can also use your personal browser (Chrome and Safari, haven’t tried Firefox).
> Chrome for Testing is the default browser. You can also attach to a running Chrome with --cdp or --auto-connect (CDP mode), select the Lightpanda or Obscura engine with --engine, drive Mobile Safari in the iOS Simulator, or use a cloud browser provider such as Browserbase, Browserless, Browser Use, Kernel, or AgentCore.
On one end of the spectrum you've got presumably you, who brings a sketch or prototype to engineering, and has a reasonable discussion about what can or cannot be made production ready on what timeline, with what budget.
On the other end you've got people who bring a half baked prototype to a couple engineers, demand it be in production next week, and then escalate and make a big scene when there's pushback.
No engineers tend to complain about the former. The latter is stressful as hell
A useful middle of that spectrum is when the person bringing the prototype also brings an understanding of what the Stakeholders need quantified it, and quantify the product level too. Quantify Security, Portability, scalability, etc.
It does wonders; check out MyJackfruit if that sounds like good ideas.
It requires both sides to play nice. Engineers have to be relaxed about it but the folks asking engineers for things need to accept that it's not as simple as the prototype may make it seem. If there is mutual understanding and respect things go well. If there is any hint of us vs them mentality, it goes sideways.
It's fine if everyone realizes they are rough sketches, specs, or prototypes. But programmers have hubris, developed through many years of writing shitty code they have to burn to the ground. Other professionals often don't have that hubris. The power of writing code goes straight to their head. Programmers are trying to write the least code possible to do what they need to do, because they know every single line is a liability. A company liability, and a personal liability, because they're the one that will have to fix it when things go wrong. I think people who are not programmers don't always understand that, and they are extra isolated from it because ultimately they don't maintain or fix their stuff. Some other poor soul does, so out of sight out of mind.
> Claudia explains the hazards of believing she is either sentient or infallible, the myopia of AI utopianism, and how gatekeeping and the "asymmetries of fluency" can be wielded against an unsuspecting world.
https://www.youtube.com/watch?v=Z6_ENp_fO_Y
reply