Very nice :)

Hello. Nice idea, but there are some problems: - on mobile the interface is hard to use - I think it would be much easier if the sections would be displayed full size, without scroll - why does the SVG include css style and loads the font? It doesn't look like it is used - the stroke size is 0, I think you don't need a color for it - maybe use currentColor so that the color can be changed

Thank you for your feedback. I will continue to improve on the issues mentioned above.

Wouldn't it be more semantically meaningful if you would use "...api/store/<hash>" with GET and PUT? That way you would also get better caching.

I like your idea of switching the endpoint specifically for caching, would be a great improvement for the service. This does run on Next.js which offers some sort of caching out of the box. When it becomes a problem, it will definitely be necessary. Thanks for the suggestion!

How?

The whole point of WEI is that the site can choose to block any combination of browser and OS they see fit, in a reliable way (currently, browsers can freely lie). CURL and friends will almost immediately be branded as bots and banned - that's the stated objective.

It is more severe than that. The design favors a whitelist approach: Only browsers that can get the attestation from a "trusted source" are allowed. Browsers that cannot, don't.

The one not working has a space after the colon. It's even in the section taking about this :)

no, it doesn't.

It looks like it's damaged in the English translation/version.

In a few other languages I checked it has :)

Does this require some special test environment (special OS, special builds of firefox/chrome)?

Because for me chrome vs firefox (both 115)

  - ubuntu desktop: 148(+-2.2) vs 126(+-6.5)
  - android phone: 95.8(+-2.0) vs 78.5(+-4.3)

So it looks like chrome is faster and delivers a more stable performance while firefox is slower and more inconsistent on performance

Extensions can have a measurable effect on the benchmark, be sure both browsers have no extension, or the same extensions with the same configuration.

Chrome has ublock and very few others, Firefox only ublock

I suppose it is about nightly 117

Adding my anecdotes: on an M2 mac mini

  - chrome 114: 472 ± 30
  - firefox 115: 390 ± 22
  - firefox 117: 420 ± 12

Small update: Firefox 117 on Android phone 75.4(+-6.4) so still there

The linked graph is for Firefox Nightly (currently 117) running on Windows.

I get 260 for chrome & 160 for firefox on win 10.

It looks like a scam app praised by 2 accounts created for this :)

Disagree. Though I definitely forwarded the link to my indie hackers groups to help with support if they like it.

You could be more impressed that some web pages manages to guess that the browser you use, that presents itself as a desktop browser, is in fact a mobile browser :)

Mine is not presenting itself as a desktop browser. It just has a smaller screen than what the designer expected. iPhone SE

A JS version adapted from https://notfunatparties.substack.com/p/wordle-solver

https://pdanpdan.github.io/wordle-solver/

main code in https://github.com/pdanpdan/wordle-solver/blob/master/src/li...

PostgreSQL?

It's not a consumer product.