3 ms·
I would like to read the article, but it seems aggressively paywalled in a manner that appears distinctly akin to those porn-scam redirects that you come across
by dijit 3y ago
I would like to read the article, but it seems aggressively paywalled in a manner that appears distinctly akin to those porn-scam redirects that you come across on the internet.
(with the fake notifications from snapchat and tiktok)
I think this is an unfortunate consequence of the heading image of the article.
- RugnirViking 3y agoI believe that is the point. It's supposed to look like an overwealming barrage of messages
- c420 3y agohttps://archive.ph/3SNw5 https://archive.ph/3SNw5 Edit: I'm pretty sure those notifications are part of the story. To offer the reader a slice of a 13 y.o. girls existence.
- Animats 3y agoDoesn't help. Mostly blank.
- c420 3y agoScroll down a bit, it looks like the archive truncates the above mentioned notifications making it look like dead space.
- jdbernard 3y agoEven at the archive link the styling hides most of the text. Firefox Reader mode make it visible.
- greenyoda 3y agoThis is what worked for me, on the original article page (not the archive), using uBlock Origin (uBO): - In the uBO dashboard, make sure you've selected "I am an advanced user" (which allows you to block specific domains). - In the uBO UI, click "all" at the top to show all the domains, then block the following domains: meter-svc.nytimes.com and samizdat-graphql.nytimes.com. (Click on the column to the right of the domain name; it should turn red to indicate it's now blocked.) (You can make these changes permanent by clicking on the lock icon in the uBO UI.) After reloading the page, I was able to see the entire article. (Tested in Firefox and Chrome.)
- foogazi 3y agoIt’s an NYT interactive article emulating phone notifications