Random tidbits

[JimTheFrog]

In the FAQ for "pwned" you mention leetspeak but don't define it. You might want to either define it (inline or as another FAQ) or link to a definition, e.g. Wikipedia.

Please make sure the FAQ is searchable (browser Ctrl-F is fine), and if the found item is in a collapsed FAQ it automatically expands.

More FAQs:

• What's an infostealer? (or maybe that will be part of your "stealer log" or "malware" FAQ)
• What's a hash?
• Is there a list of clear text pwned passwords?

The "About us and what we do" heading at the top of the privacy policy made me think I'd clicked on the wrong button and ended up on the "About" page.

What?! You put Twitter ahead of Bluesky? ;-)

P.S. Github serves the HTML files as text, which is a pain if we haven't forked the repo, but I found a very handy preview function that makes it easy to browse the static web pages: https://htmlpreview.github.io/?https://raw.githubusercontent.com/HaveIBeenPwned/ux-rebuild/main/web/index.html (details at https://github.com/htmlpreview/htmlpreview.github.com).

[troyhunt]

Partially addressed in #84

[JimTheFrog]

Request for searchable FAQ addressed in #87. Very nice.

[sdayman]

I've looked through the templates, and it does not look like you have Custom Error templates for the handful of Cloudflare default error pages:
https://developers.cloudflare.com/rules/custom-errors/reference/error-page-types/

The one error page template I see looks more like a Worker exception page, and has links to other parts of the site, which aren't going to work if the user is facing a different type of error.

[troyhunt]

Hey @sdayman, coming back to this finally now that I have time. Have you seen any of these pages returned by HIBP? Just trying to figure out where to prioritise, and if it's even worth doing (always a bit wary about relying on error pages from the origin for errors on the edge).

[JimTheFrog]

My two cents (since I'm on the thread) are that other than 5XX these are all unlikely errors (country block, rate limit, WAF etc.) and aren't worth building custom pages for. In the presumably rare case that they occur, the default browser error display should suffice.

[troyhunt]

Yep, that's pretty much my conclusion too. Unless it's shown with some regularity, it's not worth changing.

[sdayman]

Have you seen any of these pages returned by HIBP?

No, I've never seen them on your site. I use a very basic template, and slightly alter them for each type of error…just in case.

In the presumably rare case that they occur, the default browser error display should suffice.

It won't be the generic browser error. It'll be Cloudflare's generic block/error page, and it'd be very off-brand.

You can also use them if a Worker ever throws an exception, heaven forbid. (Custom Error Page for a 500 error).
https://developers.cloudflare.com/rules/custom-errors/

Yep, that's pretty much my conclusion too. Unless it's shown with some regularity, it's not worth changing.

Probably a super low priority. It was just a thought. Thanks for reviewing!

[troyhunt]

Thanks @sdayman, I appreciate the input. I think for now in the context of the current backlog that might be premature optimisation so I'll park this for now but if we ever see a generid error message popping up with any regularity, that'll be the time to do this.