I also have a similar side project planned for a revamp. Successfully made a v1 with grease monkey (vanilla JS) + stylish back in maybe 2016. Super dangerous to keep firefox 56 running only for this front-end. Just need to do the v2 then migrate to latest librewolf.

I want to redo the whole thing in Vue, client side routing with build step. The problem is that

• site is not open source
• no API doc (but I already made my own)
• required log-in (no sensitive info)
• some route request must be made from that domain due to CORS

My goal is not to change the UI but wipe the whole page and start over with custom API call instead. V1 do this by visiting a 404 route to stop unnecessary load and use my own URL param for the API call. For bonus cringe I used local storage for database.

Ended up having to use userscript, and now I’m kinda stuck with how to mash Vite build and tamper/violent monkey together :(
Do you have any suggestion or resource I can learn more on this?

If you use QMK you’re in luck.

https://github.com/daniel5151/qmk_firmware/blob/discipline/keyboards/coseyfannitutti/discipline/keymaps/prilik/keymap.c#L145
https://github.com/ridingqwerty/qmk_firmware/blob/cfd632e021f2460c50dd9e283426cc6e28c9a475/users/ridingqwerty/process_records.c#L297

Thank you. After thinking about it overnight, I realized I asked a wrong question. Your answer still helps greatly and get me more than half way to satiate my curiosity.
Tolerance grade and example objects that require different grade/minimum pi accuracy is what I was looking for.

TIL there is a closer approximation than 22/7

Thank you, I already skimmed through that article before posting. Maybe I failed to put my question into words properly.

I want examples similar to pool/fence circumference in the article. Along the line of “We’re building x, and this is the worst rounding we can go, one fewer digit and it will be off by y”

Misinformation may reduce repeat visit, that part, I have no idea if google take into account when they rank the result. Domain/page age also plays a role. But what about other “problems”? If I try to de-optimize every items on that guide, will it speed up the de-rank as well?

Regarding SEO, What’s stopping maintainers from vandalizing their own fandom page?

It would not be difficult to make a bot to update fandom page with a convincing but slightly wrong info, after a few hundred iterations, it’s all useless. Go look at what google recommend and do complete opposite. I’m convinced this will bomb ranking and put whatever wiki they migrated to at the top.