Add rotN (ie rot13) as an option to repair content obfuscated by anti-reader mode measures
Categories
(Toolkit :: Reader Mode, defect, P3)
Tracking
()
People
(Reporter: emceeaich, Unassigned)
Details
(Whiteboard: [ passive-aggressive-adtech ][reader-mode-readability-algorithm])
See the Denver Post and https://twitter.com/raganwald/status/1209633739573223425
|
||
Comment 1•4 years ago
|
||
Do we know how common this is? I imagine the Denver Post didn't pay people who work for it to do this, but it's some off-the-shelf tool that they and other publications make use of...
FWIW, trying with e.g. https://www.denverpost.com/2020/06/18/us-supreme-court-daca-colorado/ , if I click the button before the "you're reading this in private mode and that's not allowed" popup appears, I get un-obfuscated content. If I wait for the popup, and hit refresh in reader mode, I can still see the original article anyway.
If we knew the language the article was written in, we could probably detect and fix this kind of thing relatively easily (because of letter frequency) but of course, they could choose to just fill it with something other than rot13 next...
Description
•