Not sure what pisses me off more. That, or the music autoplaying.

Or breaking the back button

People just need to know when to use replaceState instead of pushState.

https://developer.mozilla.org/en-US/docs/Web/API/History/rep...

pushState maybe sometimes used but replaceState should never be used.

Seriously, many times I was on a website where scrawling introduce you to new article but it also replace the URL oh, now I wanted to go back to the original article because I wanted to share with you but I couldn't. at least with a push State I could retrace my steps and not rely on the developer guessing where I might have been going.

Be nice if there was a DNS that blackholes websites that break the back button.

OH yeah! A DNS that would crawl the website, launch a VM with a couple browsers to see if the backbutton is broken.

breaking the back button is an absolute sin. What could be the possible use case for anyone to break the back button this way?

Sorry guys, I didn't expect so much interest from the audience. I've updated the website, hope it's better now :)

Hey tsomctl, sorry for the inconvenience. We've updated the website. Removed the autoplay. I hope it works better now.

Thank god for iOS safari. Quiet as a mouse.

Hey, We didn't expect such huge feedback, and the website was made just for fun without any testing. We know that the webpage is clunky. Moreover, we're hosting it on a limited free Firebase tier. Sorry for the inconvenience.

I’m sorry the parent comment was so aggressive but I think their sentiment does have merit.

This is particularly true on mobile where trying to use the back buttons once I finished reading became particularly confusing because mobile browsers hide parts of the URL.

If it’s any consolation, you are not the first nor will you be the last person who has ever done this. Directly mutating history has costs that are not always readily apparent. The advice not to do so is not an old wive’s tale.

Thank you. We've updated the website. It's a simple landing page now, and I hope it works better now.

Well, maybe on other browsers... on Safari, on a wide screen, I still had to maximize the window to see all the text. At a "mere" 1200px wide, half the text was under the knob.

Same on Firefox at 1530 px.

What about the fact that half the text not only graphic, but also covered by the graphic, so it's impossible to read.

It's a pity the project itself is so neat. Makes me feel bad about referring to it as such a remarkably horrible web experience.

yeah, I also cannot scroll it with my finger. I had to connect a mouse to my touch screen computer just to scroll the page.

See? If you owned a Knob, you could have used it as a scroll wheel, and you wouldn't have had to connect your mouse! ;)

Right :D.

Sorry for the inconvenience. We've updated the website. Removed the autoplay, scroll should work fine now. I hope it works better now.