[geeklog-devel] Help regarding Feature Request #1606, identifying a page refresh

[Tom]

I see an article view (as determined by Geeklog) as generic check on how
popular the article is.

I am not too worried about unique views or my own views for the matter which
this report brings up 

http://project.geeklog.net/tracking/view.php?id=1572

since it is only a few views in the total number of views for an article
over time.

IMO this is starting to get too complicated. If we start worrying about
stuff like this then how about non users like search engines, twitter, and
other bots that visit articles for a variety of reasons...

Just my 2 cents :-)

Tom

PS If an admin is wondering the true popularity of his article then maybe
this is where Facebook like, Twitter and Google plus buttons are needed for
articles... like what Ben has done at Geeklog France (http://geeklog.fr/)


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Sandeep kaur
Sent: May-19-13 9:48 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] Help regarding Feature Request #1606,
identifying a page refresh

On Sun, May 19, 2013 at 6:14 PM, Rishabh Raj <rishabhr123 at gmail.com> wrote:
> Hello,
>      This is regarding discussion about a feature request #1606.
>      http://project.geeklog.net/tracking/view.php?id=1606
>
<snip>
> Any other ideas as to how to identify a page-refresh ?
>
I think there is no solution other than setting a cookie so that you can
check whether the user have visited the site or not.

--
Sandeep Kaur
E-Mail: mkaurkhalsa at gmail.com
Blog: sandymadaan.wordpress.com
_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel