Intrigued... out of curiosity, what would your implementation look like ie. what would the criteria be, and what would be displayed?
| [reply] |
I'm still meditating.
Maybe visits in the last 52 weeks?
We have different timespans for best nodes,
Week month year.. So maybe just a count?
Should be something simple... To implement and to understand.
But maybe I'm the only one with this problem?
update
After more mediation this might be too much big brother ... just a frequency calculated from the last n visits (average) may be enough. Like described here for instance.
| [reply] |
Perhaps average number of visits per month based on the last year, or avg per week over the last three months? This scrambles the data a bit and doesn't seem too big-brotherish (imho). Note that we already have the "Last here" ability, so I don't think a system such as this one that you've proposed is infringing on anyone any more than what we currently do.
What I wouldn't like is anything that displays the date/time (beyond the said "Last here"), as I'm sure some people visit PM from work where they possibly shouldn't be doing.
| [reply] |
Maybe visits in the last 52 weeks?
But that requires you to first define what constitutes a "visit". The existing "last here" function is easy - it's almost certainly just the timestamp of your last page load, with no need for any concept of how to divide up a collection of page loads into a set of discrete "visits".
| [reply] |
But maybe I'm the only one with this problem? :) No, but other people are more content with the nature of these things ... reach out, maybe you get an answer today/week/month, maybe never, but its all you can do, its life
| [reply] |
This may be considered an invasion of privacy. Also, a complete history, even obscured in averages, may be too much information for people to give out.
Hmm... We already have last here. Howsabout adding a (hidden) number to store the last here when it gets updated (by the calculation, and only on login, and only once per calendar day), and simply report next to the current last here, if it is greater or less than the last "last here."
For example, say i don't login for the weekend, so just before i do, my last here is ~2.5 days. When i login on Monday, the "2.5 days" would be stored (and hidden), my last here would show 0 seconds, and "less than". When i logged in on Tuesday, "1 day" would overwrite the (hidden) 2.5, and it would show 0 seconds "less than", and so on. On Sunday, my "last here" would show "2 days" and "greater than." This hides the login schedule, but shows a enough info about the last two visits.
OTOH, we could rename the site to perlbook.org, add a friending system, and replace the voting system with a "like"ing system. PB, would now be famous again (all due respect to Marcellus Gilmore Edson,) and the IPO would generate billions. With that kind of money, we could put out Perl 6 and pay a full-timer to tell everyone why the site should not be updated.
| [reply] |
