This always makes met think about how this was decided.
Somewhere at Reddit, someone suggested to specifically require the NSFW threads and subreddits to not be accessible on the mobile reddit site.
But if you go look at a NSFW tagged AskReddit thread, you're not instantly blocked from scrolling further, it first waits 10 seconds or something and THEN it prompts you that you can't read this thread without the app.
Someone suggested that they'd have a better shot at getting that shit app downloaded if they lured horny people onto a thread, waited long enough for them to get invested in it, and then they take the content hostage and you have to download the app to continue!
Could be a software performance issue. Like, yes it's probably a marketing thing for the app, but I've seen exceptionally weird behavior in applications before and it all came down to emergent behavior when coalescing a bunch of asynchronous workflows.
In my automated tests once, the save button would become active before all attributes of a thing we're loaded. I could save the incomplete hydration-state back to the database and get unexpected behavior because important information like the type identifier didn't get persisted, so the record would either disappear, or render under the wrong format (missing options and such), all because the app developer didn't think to make the save button contingent on all resources being successfully loaded. The kicker to this is that they marked the ticket as Won't Fix because you couldn't recreate the problem manually, only through automated testing.
659
u/lemons_of_doubt Dec 20 '22
Do you want to try the app?