Live data from Hacker News

The Website Specification

specification.website

131–140 of 236 posts

Re: The Website Specification

#131
post #85
post #50

Earlier quoted context omitted.

I too want to go back to that, but I fear most consumers/potential visitors to your website have been conditioned to expect flashy web by this point and so it's a self reinforcing paradigm.

Nothing has changed. The "flashy web" of the 2000s was ... Flash. Corporates paid premium rates to Flash Designers who couldn't write a line of HTML.

Oh God I hated that. I'm not entirely sure why I hate it so much more than over-Javascripted sites. It feels even more alien.

Re: The Website Specification

#133
post #19

Earlier quoted context omitted.

With how bloated and ad-ridden websites have become, I'd love the pure text version for us humans - let the agents deal with stuff intended for us. But I also have my doubts we'll see that. Regarding the bad actors point, that's been possible for a long time - e.g. serving up different content for search engine crawlers than the user sees when they click through. If I remember correctly, there was a time Google penal…

This is what reader mode is. It exists purely because most websites are unreadable.

I know about reader mode but rarely use it. Perhaps I feel like any web site that needs it doesn't have anything worth reading.

Re: The Website Specification

#134
I think the presentation may fail to land because, on the surface, it is nearly wholly AI-generated, but also after reading through many of the entries, everything besides the Agent section seems to clearly communicate solid web hygiene and I wouldn't mind sending this to a burgeoning web developer.

It is ironic though that the site itself fails to employ even its own "required" practices, but that's more of an aside.

Re: The Website Specification

#135
post #11

"Agent Readiness" will likely age as well as "Web 4.0 Blockchain Integration" has. (To be entirely clear, not because agents won't be a relevant thing, although certainly I have my doubts, but because I believe even if they are a relevant thing, requiring special allowances from sites undermines the whole point, and such things will only end up used by bad actors to mismatch what agents see to what humans see, and so…

Agent readiness seems like an entirely helpful step. People aren't using blockchains on my websites but they are using AI, and AI do not need to use websites like humans. Humans want to see a good-looking website, even just raw HTML. An agent doesn't even need that, ideally they would just see the content of the page in markdown. Why not have an agent version? It saves the client agent and the website host time and m…

> Why not have an agent version?

Why have one? There are no benefits, and innumerable downsides.

> It saves the client agent and the website host time and money.

I do not care about the users' budget, if they don't want to spend a trillion dollars they can just read a website like everyone used to.

As for my own hosting budget, the AI scraper bots consume 2 or more orders of magnitude more bandwidth than the AI agents, it's utterly irrelevant to aid them.

> Also, part of agent readiness on this website is the AI equivalent of SEO

SEO is dead.

Click-through rates have crumbled. AI bots and agents don't provide ad impressions, so revenues are crashing as well.

And the flood of AI slop has made Google significantly more aggressive in "shadowbanning" anything that even remotely looks like what the AI sloppers are doing at any given moment.

Re: The Website Specification

#136
Cool. I just dropped the following prompt on the Claude iPhone app and got a nice report out of it:

Look at the part of the website at my first link, that describes how to do an audit using their guidelines, then after that, run such an audit on my website at the second link.

https://specification.website/

Www.my-personal-squarespace-site-not-a-real-url.com

Re: The Website Specification

#137
post #44

I'd love best practices around, say, login forms, e.g.: - use standard input field names password managers recognize - disable autocompletion and autocapitalization on the login field - if it's an email, use the correct HTML5 input type - don't have a form with just a login email and force the user to click to enter the password - follow NIST SP 800-53, e.g. no SMS 2FA and no arbitrary password rotation and compositi…

> many sites that have a form with only one input don't automatically focus on it.

That's reasonable to do when that form is the reason a page exists but otherwise it's best to not mess with the user's focus.

Re: The Website Specification

#138
post #18

Earlier quoted context omitted.

Yeah, the entire suite of proposed "standards" catering to agents looks like a temporary measure to duct-tape over the limitations and token costs of today's agents. They'll churn as quickly as Anthropic, Google, OpenAI et al. can release new versions of their frontier models.

> Yeah, the entire suite of proposed "standards" catering to agents looks like a temporary measure to duct-tape over the limitations and token costs of today's agents. That's fine. We need a fix for today's problems today.

> That's fine. We need a fix for today's problems today.

No, we don't. It is Anthropic, Google, OpenAI et al. who need a fix for those problems today. Let them deal with it.

Post reply on HN