#185 Measure the frequency of visit of a hub
Closed: Fixed Opened by pingou.

In order to know which hub someone visits the most frequently, we need something to measure it.

It might be as simple as a counter in the people <-> hub relation table which is updated every time the user accesses this hub


Are we just making this simple for now? For example everytime the page is loaded or are we considering unique visits?

How would you define unique visits?

i like the wikepedia definition

Unique visitors refers to the number of distinct individuals requesting pages from the website during a given period, regardless of how often they visit. Visits refers to the number of times a site is visited, no matter how many visitors make up those visits. When an individual goes to a website on Tuesday, then again on Wednesday, this is recorded as two visits from one visitor.[1]

src: https://en.wikipedia.org/wiki/Unique_visitor

I don't think that the visit should be counted on daily basis, rather it would be good to just ignore the visits if the page was reloaded.

I know what it means, my question was: how do you plan to implement it?

By Ip/day ? Using cookies?

just ignore the visits if the page was reloaded.

That might be tricky. Look below for answer of my thoughts

I know what it means, my question was: how do you plan to implement it?

Oops sorry, the word define tricked me up. I would say a cookie might be our best best in this situation. Put a time stamp on it.

Some down sides to this.
1. Private browsing mode doesn't store cookies so I can artificially grow my group visits by holding refresh.
2. Cookies can expire/cleared/modified by client

  1. Private browsing mode doesn't store cookies so I can artificially grow my group visits by holding refresh

Since the idea is to use this ranking for suggesting an ordering, I think it's safe to ignore this side-effect, it would only impact you :)

That might be tricky. Look below for answer of my thoughts

Never did myself but google gives us a few suggestions.

Some down sides to this.
1. Private browsing mode doesn't store cookies so I can artificially grow my group visits by holding refresh.
2. Cookies can expire/cleared/modified by client

Don't think it would matter much.

That might be tricky. Look below for answer of my thoughts

Never did myself but google gives us a few suggestions.

Some down sides to this.
1. Private browsing mode doesn't store cookies so I can artificially grow my group visits by holding refresh.
2. Cookies can expire/cleared/modified by client

Don't think it would matter much.

In the case of spammers they can artificial grow their pages to be top rated and then when new users come by they see these spam accounts as highly rated, click on the hub, and they see stuff about Quickbooks, magic drugs, weight loss, etc... being displayed it just gives off a bad image

I think initially we just do a simple implementation but we should consider the side affect of it being abused for the future.

In the case of spammers they can artificial grow their pages to be top rated and then when new users come by they see these spam accounts as highly rated, click on the hub

No because the ranking is used for you: if you visit all the time @sayanchowdhury 's hub, then hubs may suggest that you place that hub higher in your bookmarks.
But if I log in, your ranking won't change anything to what I see :)

Ahh i wasn't fully understanding the use case for this. I suppose if the suggestion for hubs would be hard to abuse. I think we are fine then

Naive implementation is done. Where on load of a hub we increment the counter.

Next step is to use a cookie to set a timestamp.

Is every hour okay for a unique visit?

More complex implementation is done. Only increments the counter when its not a page refresh or page redirection from history. Also, added some security so its harder to abuse.

More complex implementation is done. Only increments the counter when its not a page refresh or page redirection from history. Also, added some security so its harder to abuse.

We can close this

https://pagure.io/fedora-hubs/pull-request/215

@skrzepto changed the status to Fixed

Metadata