4 ms·

> You need to enable JavaScript to run this app. What app? Why don’t folks do the bare minimum in their <noscript> elements to actually describe what it is tha

> You need to enable JavaScript to run this app. What app? Why don’t folks do the bare minimum in their <noscript> elements to actually describe what it is that I’m missing out on.

RockRobotRock 3y ago
"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting."
- toastal 3y ago
  So we just sweep basic accessibility and best practices under the rug because it’s common to screw it up? A little public shame should inspire the webmaster and comment readers to double-check their websites.
eimrine 3y ago
I ran the app and I see some countdown timer with 51 hours left which proposes me to do something I am struggling to understand. Also it has some plain-text faq but you know, nobody is storing just a plain text and it was made in such a way that every point is spoilered. There is indeed no reason to disallow seeing the faq for no-javascript users. upd: I have discovered a link to off-the-app documentation: https://github.com/ethereum/kzg-ceremony https://github.com/ethereum/kzg-ceremony
- toastal 3y ago
  Well, the purpose of this site is to provide information and it’s not a web app. The goal of such site should be to make that info as accessible as possible with no reason to involve anything more complicated than absolutely necessary--not just towards users but also bots/scrapers for SEO. That generic <noscript> text is commonly from create-react-app or its ilk which should be reserved as technology for web apps. This is yet another example of a landing page that could+should be static pages with minimal JavaScript for progressive enhancement.
x-complexity 3y ago
> > You need to enable JavaScript to run this app. > What app? Why don’t folks do the bare minimum in their <noscript> elements to actually describe what it is that I’m missing out on. Javascript is needed in order to generate random entropy client-side. This specific interface requires mouse movement, a secret phrase, & randomly generated entropy from the client itself.
- toastal 3y ago
  1. Why aren’t they saying this in their <noscript> 2. There’s a lot of content on the page that should be purely static like the FAQs. We can see using a non-Google search like https://search.brave.com/search?q=kzg+ethereum+ceremony https://search.brave.com/search?q=kzg+ethereum+ceremony and see the SEO for all that data is missing because it requires JS without a good reason.
  - x-complexity 3y ago
    > 1. Why aren’t they saying this in their <noscript> > 2. There’s a lot of content on the page that should be purely static like the FAQs. We can see using a non-Google search like https://search.brave.com/search?q=kzg+ethereum+ceremony https://search.brave.com/search?q=kzg+ethereum+ceremony and see the SEO for all that data is missing because it requires JS without a good reason. https://github.com/zkparty/trusted-setup-frontend https://github.com/zkparty/trusted-setup-frontend Occam's razor: Because they didn't think they'd need to put any additional message other than "Please enable JS", since almost everyone enables it. It's likely they were "build the use case first" when going through with it, and that addressing "no JS" & SEO were not high on that priority list.
    - toastal 3y ago
      Hanlon’s razor or ignornace is more likely than that. This message comes with the default framework and someone didn’t know they should check (and we should fault the framework for not throwing a build exception for missing noscript rather than inserting a useless one). You can sum up what the site is and what’s missing in 1–3 sentences and have a massively better noscript experience, but this is the sort of thing that needs to be in project requirements. If you add these to your requirements to a project, you'll ultimately find the path of least resistance was to choose a framework/mindset that didn’t involve at unnecessary virtual DOM no 95% of the time render static (not dynamic) content. Adding a message to enable JS to add to the entropy gives users a simple, actionable message.

> You need to enable JavaScript to run this app. What app? Why don’t folks do the bare minimum in their <noscript> elements to actually describe what it is that I’m missing out on.

RockRobotRock 3y ago

"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting."

toastal 3y ago
So we just sweep basic accessibility and best practices under the rug because it’s common to screw it up? A little public shame should inspire the webmaster and comment readers to double-check their websites.

eimrine 3y ago

I ran the app and I see some countdown timer with 51 hours left which proposes me to do something I am struggling to understand. Also it has some plain-text faq but you know, nobody is storing just a plain text and it was made in such a way that every point is spoilered. There is indeed no reason to disallow seeing the faq for no-javascript users. upd: I have discovered a link to off-the-app documentation: https://github.com/ethereum/kzg-ceremony https://github.com/ethereum/kzg-ceremony

toastal 3y ago
Well, the purpose of this site is to provide information and it’s not a web app. The goal of such site should be to make that info as accessible as possible with no reason to involve anything more complicated than absolutely necessary--not just towards users but also bots/scrapers for SEO. That generic <noscript> text is commonly from create-react-app or its ilk which should be reserved as technology for web apps. This is yet another example of a landing page that could+should be static pages with minimal JavaScript for progressive enhancement.

x-complexity 3y ago

> > You need to enable JavaScript to run this app. > What app? Why don’t folks do the bare minimum in their <noscript> elements to actually describe what it is that I’m missing out on. Javascript is needed in order to generate random entropy client-side. This specific interface requires mouse movement, a secret phrase, & randomly generated entropy from the client itself.

toastal 3y ago
1. Why aren’t they saying this in their <noscript> 2. There’s a lot of content on the page that should be purely static like the FAQs. We can see using a non-Google search like https://search.brave.com/search?q=kzg+ethereum+ceremony https://search.brave.com/search?q=kzg+ethereum+ceremony and see the SEO for all that data is missing because it requires JS without a good reason.
- x-complexity 3y ago
  > 1. Why aren’t they saying this in their <noscript> > 2. There’s a lot of content on the page that should be purely static like the FAQs. We can see using a non-Google search like https://search.brave.com/search?q=kzg+ethereum+ceremony https://search.brave.com/search?q=kzg+ethereum+ceremony and see the SEO for all that data is missing because it requires JS without a good reason. https://github.com/zkparty/trusted-setup-frontend https://github.com/zkparty/trusted-setup-frontend Occam's razor: Because they didn't think they'd need to put any additional message other than "Please enable JS", since almost everyone enables it. It's likely they were "build the use case first" when going through with it, and that addressing "no JS" & SEO were not high on that priority list.
  - toastal 3y ago
    Hanlon’s razor or ignornace is more likely than that. This message comes with the default framework and someone didn’t know they should check (and we should fault the framework for not throwing a build exception for missing noscript rather than inserting a useless one). You can sum up what the site is and what’s missing in 1–3 sentences and have a massively better noscript experience, but this is the sort of thing that needs to be in project requirements. If you add these to your requirements to a project, you'll ultimately find the path of least resistance was to choose a framework/mindset that didn’t involve at unnecessary virtual DOM no 95% of the time render static (not dynamic) content. Adding a message to enable JS to add to the entropy gives users a simple, actionable message.