I decided to go with applying the compile-step to all client-side scripts options.
Nonetheless this might be nice to have 😉
The thing is, it's nearly pointless to go to great lengths to stop users from reading your content. You want the Googlebot to be able to scrape your content, instead of your paywall, or in the case of client-side overlays, any reasonably competent client-side dev would just locate the element in DOM and delete it
But I suppose the thing is over 95% of the population wouldn't even go as far as to clear their cookies, so something simple like cookies would actually work facepalm
I suppose the thing is over 95% of the population wouldn't even go as far as to clear their cookies
Me too. I wouldn't clear cookies, I'd just press
Ctrl + W.
Ok so perhaps not a paywall per se. But a registration reminder via a light box or some form. Gentle encouragement plugin or something.
@a_5mith How about a global widget that asks everyone to register?
I'm also suggesting a widget.
Maybe a widget-plugin that adds a template to hide until a specific amount of topics got visited and to provide the amount for the widget-contents (taking care of uniqueness).
You've already read 16 different topics. Wouldn't you mind to register?
Maybe just a guest-statistics plugin that collects (and provides to templates) some information like that for each single guest.
@julian That is horrible and I wish people would stop doing it!
Easy to bypass though
Cookies with a redirect.
If the user can't be bothered to register, then they probably can't be bothered to clear their cookies.
How about a giant sidebar ad with a message that says "Sign in to remove this ad, registration is free!"
Anon users rack in some extra $ and more people end up signing up. Win-win
Not a fan of ads. Adblock being popular and all that.
What if its a giant "I NodeBB" banner then?