google suggests that error 1001 is a cloudflare-side DNS configuration problem with the domain (which is CNAME'd to target.substack-custom-domains.com, which is cloudflare-hosted). CNAMEs to cloudflare seem to require special care.
I relaunched Knowledge.Dev, and now I also generate free PDF books in Typst. I can say that even today, Typst's capabilities can fully replace LaTeX, while being incredibly convenient to use. All in all, I'm excited to share the results of my work over the past year.
I have been watching for Typst for more than a year but there are still things Typst can not do as easily as LaTeX, see https://qwinsi.github.io/tex2typst-webapp/impl-in-typst.html for examples. So, I do not agree with the statement that Typst can fully replace LaTeX, at least, for now.
Other than the product itself, there are ecosystem issues as well. LaTeX has mature support in editors such as Emacs. However, support for Typst in Emacs is still in development. Thus, for now, I will keep using LaTeX, but I would keep Typst as an option.
That page has a reasonable re-creation, with trivial usage at call-sites, of each missing feature though? The only one that looks a bit revolting is the large pipe example
Getting an SSL cipher version mismatch error.
To add more detail, https://knowledge.dev/ loads fine but https://press.knowledge.dev/ does not.
Clearly they didn't pay for the premium version.
To be more specific about the error (yes the http is intentional, https immediately fails a ssl handshake, but http gives a possibly useful error):
> $ curl -i http://press.knowledge.dev
> HTTP/1.1 409 Conflict
[...cloudflare headers...]
> error code: 1001
google suggests that error 1001 is a cloudflare-side DNS configuration problem with the domain (which is CNAME'd to target.substack-custom-domains.com, which is cloudflare-hosted). CNAMEs to cloudflare seem to require special care.
I relaunched Knowledge.Dev, and now I also generate free PDF books in Typst. I can say that even today, Typst's capabilities can fully replace LaTeX, while being incredibly convenient to use. All in all, I'm excited to share the results of my work over the past year.
I have been watching for Typst for more than a year but there are still things Typst can not do as easily as LaTeX, see https://qwinsi.github.io/tex2typst-webapp/impl-in-typst.html for examples. So, I do not agree with the statement that Typst can fully replace LaTeX, at least, for now.
Other than the product itself, there are ecosystem issues as well. LaTeX has mature support in editors such as Emacs. However, support for Typst in Emacs is still in development. Thus, for now, I will keep using LaTeX, but I would keep Typst as an option.
That page has a reasonable re-creation, with trivial usage at call-sites, of each missing feature though? The only one that looks a bit revolting is the large pipe example
I'll be interested to take a look once the site is back up!
Pulled out good ol' wireshark. It's the server that's erroring on the TLS handshake.