Also the cpluscplus example. It throws structured data in a completely unreadable format and ads paddings to the navigation where they are surely not needed.
It's not showing x minutes AND y seconds, it's x minutes OR y seconds. Minutes is just there for someone who doesn't need precision and can let the API handle the rounding. Seconds is for people who want to do more advanced stuff.
You're not the first person to make that kind of mistake, and I assumed it was an obvious enough "attack" that trying to communicate it privately wasn't required.
Though I now have an extra if statement in my code to detect and log this type of 'hacking' attempts in addition to some others, the code was never vulnerable to this in the first place. No file contents are displayed at any time anyway.
Thanks for sharing! The point here isn't just calculating the reading time based on a WPM metric, it's fetching a remote page, analyzing it to find the main content and then doing the maths, among other stuff taking into account any images.
I'm aware of it, thanks. The current approach isn't really that flexible. For example, I've seen the NY Times and The Atlantic not working. I've considered some different potential fixes but haven't implemented them yet. Thanks!
