Please don’t tell me we are willing to make it easier for AI to read our content than we are to make it easier for humans to read our content. Better idea: make your UI always prioritize the content.
Serve Markdown to AI Agents with Accept Headers
101–105 of 105 posts
Re: Serve Markdown to AI Agents with Accept Headers
#102Earlier quoted context omitted.
> Let's say you want to plan a trip to Thailand with your family. You could use the fancy AI to do it for you, or you could build a stupid frontend with minimal natural language understanding. It's giving https://news.ycombinator.com/item?id=8863#9224
> It's giving Except it isn't. Someone else could build that stupid frontend, and essentially create a better booking.com. Or you could ask the robot to make you a stupid frontend. It remains true that a well-designed MCP server goes wildly against the interests of sites like booking.com.
Even something as simple as a recipe blog. That one is already solved by chatbots, and it’s glorious. I never have to look at a shitty recipe site full of ads with the recipe buried beneath a mile of fake stories again. LLM finds some, reads reviews, I pick one, if it’s good import to paprika, and that’s that.
There’s at least a chance that enough people demand it, combined with AI hype, that we could end up with a slightly better experience.
And if not, then there’s always the brute force approach of something like grok bot
Re: Serve Markdown to AI Agents with Accept Headers
#103Re: Serve Markdown to AI Agents with Accept Headers
#104Re: Serve Markdown to AI Agents with Accept Headers
#105Please don’t tell me we are willing to make it easier for AI to read our content than we are to make it easier for humans to read our content. Better idea: make your UI always prioritize the content.
It's more along the lines of "Oh, hey there, you look like a bot, here are details on how to use our monetized mcp".
More likely though is that nothing will change here, because people will abandon it as soon as there is a paywall.