While we're already breaking the HN guidelines—"Please don't complain about tangential annoyances—e.g. article or website formats"—let me just say that the scrolljacking on this article is awful.

I've not intentionally implemented any scrolljacking (I'm using the default obsidian template), but I'm curious what you mean as I also don't see where the scrolljacking would happen. Could you elaborate on the way in which the user experience is awful now, so I can improve it?

onScroll in https://publish.obsidian.md/app.js?4bb6aa9a821f975db2a1

Try the page down key.

this is fixed now!

It's not.

page down should work now, maybe you need to hard refresh?

Define "should work". It's still scrolljacking. I don't get my native browser smooth scrolling down a page.

What browser are you using? Can you describe the issue? Typically scroll jacking is when you hook on scroll to forcefully scroll the page to something, but that's not happening here.

> What browser are you using?

Safari

> Typically scroll jacking is when you hook on scroll to forcefully scroll the page to something, but that's not happening here.

That's literally what's happening here. Open the web inspector, and set a breakpoint on the scroll event.

Bah, cats have a place in programming articles, regardless of seriousness

Also the “highschool poem”-type writing style is quite jarring but forgiven when he acknowledged it at the end of the article.

> Also I decided to try writing this thread in the style of a linkedin influencer lol, sorry about that.

This was not intended to be a serious article, like something you'd submit for publication in an ACM journal.

The last sentence is: "(Also I decided to try writing this thread in the style of a linkedin influencer lol, sorry about that.)"

The tone of the article has given away the fact that the article is not serious. At least not the way it's presented. You want something serious? Go read the pdf.

And I don't mind at all. Without this article, I probably will never know what's in the paper and how they iterated. I'll likely give up after reading the abstract -- "oh, they solved a problem". But this article actually makes much more motivating to read the original paper, which I plan to do now.

I'm happy to have spread the good word! Note that when you read the paper, some implementation details are slightly different than my description. For instance, they always store the recursive real form of the real part of each number, even when the symbolic part perfectly describes it. I removed this redundancy to try to simplify it for twitter, but I hope it doesn't confuse those who go on to read the paper afterwards.

Cats rule our world. So nothing wrong about it.