Thanks for the detailed and thoughtful reply! I agree that in both of the scenarios you mentioned, this API does provide better usability.
I guess what feels wrong to me is the implicitness of this feature, I'm not sure whether clicking on something is going to add to history or not (until the back button breaks, then I really know).
Well, if I wanted to return to the parent screen in a single page application, I'd click on the back button in the app itself. No need to prevent me from back tracking in the exact order of my browsing should I need it.
I especially hate YouTube's implementation, I can never know the true state on my older PC during whatever it's trying to accomplish, often playing audio from a previous video when I backspace out. I resort to opening every link in a new tab.
Please explain the legitimate uses. Not once I have ever encountered a website that does something useful by modifying the behavior of my browsing history.
The Affinity suite was made free to use, with optional paid "AI" features behind a subscription. The betrayal was probably against the promise of a perpetual license sustained not by subscription.
Trigger warnings are not there for some scientific effect. I view them as courtesy for consumers to have an chance to opt out of possibly unwanted experiences beforehand.
Wow, perhaps Nintendo/Konami actually learned this tactic from IBM, threatening smaller game developers with patents when their case for copyright is too weak...
That's like saying online banking is doomed because rubber-hose cryptanalysis exists. The defense does not have to stop 100% of the exploits to be effective.
I hate kernel level anti-cheats but they do provide friction and reduce cheating.
https://en.wikipedia.org/wiki/One_Hundred_Thousand_Whys