You probably don't need a screener form anymore. You can run software in the background that can predict—to a reasonable degree—if you've actually read an article or not. It could watch things like time on page, scroll behaviors, etc. This is basically how Google's reCAPTCHA works. If it passes, show a share button. If not, don't.
This is probably tougher on desktop browsers where the user can just grab the URL and paste it anywhere they want.
Hey! I see what you are saying, but I like the concept of adding a friction layer to the share of articles. I like the idea of making it a little bit harder compared to what it is now. I think it could help to develop a different perspective on article sharing!
Ha, I actually did this today. I skimmed the article and share it with my personal experience. Half the time, I try to be that "Redditor" that summarizes the article in their comment, so you don't have to read it.
That's the kind of people we need :)
Reminds me of this story - making sure people have read the article before commenting: https://arstechnica.com/gaming/2018/03/how-a-norwegian-comment-section-turned-chaos-into-order-with-a-simple-quiz/
Liked the title. Shared & didn't read! /s
interesting concept, but i'd be concerned about scaling this since each article would require a bespoke captcha question.
you could also simply hide share button until user clicks through, similar to how facebook displays related stories.