joesuf4

New New here is that the original Conjecture is now established as a pair of Corollaries.

Final revision to appear on arXiv on Tuesday.

Knee-jerk dynamism and crowd-following has led to catastrophic risks and unreasonable costs to those who build and operate online systems. Orion is taking a more considered approach and is developing static content technology that blurs the traditional distinction in responsiveness between static and dynamic systems. I think Joe is onto something with this approach, and I am eager to see where he can take it. – Paul Vixie, Internet Pioneer

What you want is bidirectional sync with git, so you can use Agentic AI locally and git push your changes.

What you want is Orion.

Just use double-dollar for everything as the Editor.md developers originally introduced in 2015. Simple, painless, and intelligent.

Using a single-dollar is asinine.

You are such a bore. Read the motivating preamble in Gruber's spec- that's the part the GFM standardization process stayed faithful to.

Up until Microsoft got involved.

Boring, useless content. You must love the sound of your own voice when you read back the nonsequiturs you have offered in this comment section.

Ok, sycophant

There is absolutely no point to your post. We are discussing GFM, which is also linked to in the article you didn't read.

Seven years ago? Who cares?

Yawn.

They are not supported by GitHub’s GFM, and you are being incredibly bad faith about this fact.

If you are comfortable calling Markdown a futile exercise in avoiding proprietary control of a universal, simple document format for wide interoperability across natural languages, programming languages, and monopoly interests, then you and I are Microsoft vs Sun over Java in the 1990s.

Yawn. Nobody uses it to parse GFM unless they are over 60.

The spec is linked to in the article. Do you know how to click on a link, or do you use Braille?

Great, but Jupyter notebooks aren’t written in Markdown.

Next?

Updated again, and translated to 11 languages besides English.

Peace.

If it really was this simple GitHub would have publicized this spec instead of being intentionally vague and opaque about it.

But you know what’s best.

Naive, and cloistered. Not a great look. Maybe 5 people and their friends use Pandoc, so it doesn’t have to be robust.

Idiotic take. Clearly you didn’t click on the link.

Besides, I updated the article for clueless people like you, so give it another shot.

I’m an engineer, not an influencer.

Learn the difference by dealing with substance, not personability.

Besides, nobody gives a crap about Wikipedia file formats. They are not specs that others may implement independently.

GFM is a spec, not a vendor format.

Perhaps I should say syntax, but really how are you supposed to know what is meant when someone writes $1.50, $2.00 or $\text{more}$.

Wrong. As the article states, MathJax has nothing to do with Markdown. Never did. For that matter, neither did KaTeX. It just inteprets text some grammar parser delivers to it and delivers MathML.

The embrace and extend problem appears when you incorporate LaTeX’s grammar into Markdown.

I guess you qualify as one of those sycophants I spoke of towards the end.

Secure SSG engine w/ Incremental Builds and online CMS markdown editor.

Built in KaTeX / Asymptote / Mermaid support.

See

https://blogs.sunstarsys.com/joe/apache-considered-harmful

for the permalink.

Most customers are running it behind a proxy server as part of their middle-tier webapp stack, so this isn't even a tiny fraction of the existing user base.

And despite the decade-long warfare against its userbase by the community of glorified morticians at Apache HTTPd Server Project, it still has a growing customer-base!

Here's a list of sites who announce mod_apreq2 in their ServerTokens.

There are literally thousands of others who do not advertise the version number out of security concerns.

https://webtechsurvey.com/technology/mod_apreq2

FYI:

https://projects.apache.org/committee.html?httpd#:~:text=Joe...

Are you involved with the ASF at this point? You certainly are peevish, vapid, and territorial enough to be chair of some dead end project like HTTPd.

What I would have done differently:

1/ report the Google Fuzz Report to the actual development team, to coordinate and collaborate on a solution.

2/ not take three whacks at a security release just to fix the same vulnerability

3/ not attempt to ship whimsical patches in a security release

4/ not patch the test suite to lie to voters about the viability of a release candidate.

5/ ship a hotfix immediately after users report the bugs on 2.17