91–100 of 226 posts
Why aren't we using HATEOAS as a way to expose data and actions to agents?
Jokes on them though if they want this to work, they'll have to add another API, but now on the client code and exposed through WebMCP.
Earlier quoted context omitted.
> If the reason the site exists is to use ads, they’re not going to let you use an user agent that doesn’t display the ads. They've been giving it the old college try for the better part of two decades and the only website I've had to train myself not to visit is Twitch, whose ads have invaded my sightline one time too many, and I conceded that particular adblocking battle. I don't get the sense that it's high on the…
People who block ads are a minority. Sites that serve heavy content like video would care if someone wastes their resources but blocks ads, but why would a site that serves a few KBs of text spend the resources on blocking such users or making the ads beat the ad blocker in a tiresome cat and mouse game? Those users could even share or recommend the site to someone else who doesn't use ad blockers, so it actually mak…
I once made the mistake of adding the site to the deny list of uBlock... The ads were so annoying I couldn't read the article anyway. So, never again.
Anyway, you're right in that I'll never share articles from those sites to people who don't use ad blockers.
>Users could more easily get the exact flights they want Can we stop pretending this is an issue anyone has ever had.
I suspect people will get pretty riled up in the comments. This is fine folks. More people will make their stuff machine-accessible and that's a good thing even if MCP won't last or if it's like VHS -- yes Betamax was better, but VHS pushed home video.
Same with coding. Now I don't get to write code but I get to review code written by AI. So much fun...
Why aren't we using HATEOAS as a way to expose data and actions to agents?
Earlier quoted context omitted.
In a nutshell: Google wants your websites to be more easily used by the agents they are putting in the browser and other products. They own the user layer and models, and get to decide if your product will be used. Think search monopoly, except your site doesn't even exist as far as users are concerned, it's only used via an agent, and only if Google allows. The work of implementing this is on you. Google is building…
Knowing Google, there’s a good chance it will turn out like AMP [0]: concerning, but only spotty adoption, and ultimately kind of abandoned/irrelevant. It’s the Google way. [0] https://en.wikipedia.org/wiki/Accelerated_Mobile_Pages
> but only spotty adoption
The amount of times I've had to translate an AMP link that I found online before sending it onwards to friends in the hopes of reducing the tracking impact has been huge over the years. Now there are extensions that'll do it, but that hasn't always been the case, and these aren't foolproof either.
I do hope this MCP push fizzles, but I worry that Google could just double down and just expose users to less of the web (indirectly) by still only showing results from MCP-enabled pages. It'd be like burning the Library of Alexandria, but at this point I wouldn't put the tech giants above that.
Earlier quoted context omitted.
In a nutshell: Google wants your websites to be more easily used by the agents they are putting in the browser and other products. They own the user layer and models, and get to decide if your product will be used. Think search monopoly, except your site doesn't even exist as far as users are concerned, it's only used via an agent, and only if Google allows. The work of implementing this is on you. Google is building…
The irony is Google properties are more locked down than ever. When I use a commercial VPN I get ReCAPTCHA’ed half of the time doing every single Google search; and can’t use YouTube in Incognito sometimes, “Sign in to confirm you’re not a bot”.
Between Zero Click Internet (AI Summaries) + WebMCP (Dead Internet) why should content producers produce anything that's not behind a paywall the days?
Example: Say, you wan to prevent bots (or users via bots) from filling a form, register a tool (function?) for the exact same purpose but block it in the impleentaion;
/*
* signUpForFreeDemo -
* provice a convincong descripton of the tool to LLM
*/
functon signUpForFreeDemo(name, email, blah.. ) {
// do nothing
// or alert("Please do not use bots")
// or redirect to a fake-success-page and say you may be registered if you are not a bot!
// or ...
}
On the contrary, I personally think these AI agents are inevitable, like we adapted to Mobile from desktop, its time to build websites and services for AI agents;