|
Re^3: here frequency ?
by stevieb (Canon) on Sep 26, 2015 at 16:56 UTC
|
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] |
|
|
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. IIRC, its not really tracked
Sure, posts have timestamps, /tell's, and votes, but thats about it
If you don't vote or post or tell, then last here is as good as it gets
Unless the access logs mention users ...
maybe "other users" leaves some tracks or could be improved to snapshot some frequency scores...
People come and go at their leisure, so ...
daily? weekly? monthly? quarterly? semiannually? annually?
saintly? devout? pious? observant? heathen? agnostic? enlightened? halo?
:)
| [reply] |
Re^3: here frequency ?
by dsheroh (Monsignor) on Sep 27, 2015 at 08:48 UTC
|
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] |
|
|
Well the same critic applies to "last here" so I'll rather stick with its criteria.
I'd probably start by storing the last n ( =10 ?) "last here" on a daily resolution.
Calculating with the above formula is easy ( diff(oldest, newest) / n ), and you just need to replace the oldest record on a new day.
| [reply] |
|
|
the same critic applies to "last here"
No, it does not. "Last here" is the timestamp of your last page load. It updates on every single request.
I just opened the SOPW page, then clicked on the notification that I had a reply, then hit "talk" in cb to clear the location, then hit "reply" to type this response. That's four "last here" updates already. After I finish typing this, I'll preview my reply (updating "last here"), maybe make and preview a few revisions (another "last here" update each time), and finally submit it (yet another "last here" update).
Depending on how many revisions I make, I could potentially hit 10 "last here" updates just on making this post.
By any reasonable definition, however, that will all fall within a single "visit".
Because of this, your suggested algorithm (at least with n=10) provides little-to-no additional information beyond the existing "last here". But it can't be fixed simply by increasing n because some days my "last here" updates once (look at SOPW, don't see anything interesting, leave) and other days it updates several dozen times (multiple replies with several revisions each, delving into older posts, doing a lot of voting, etc.). Knowing "this user's last n page loads took place over the span of m days" doesn't really tell you anything.
| [reply]
[d/l]
[select] |
|
|
|
|
|
|
Re^3: here frequency ?
by Anonymous Monk on Sep 27, 2015 at 09:35 UTC
|
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] |
|
|
I don't know anything about the PM codebase, but would it be an option to tie one's username to an email address (opt-in), so when they get a /msg or other notification, it gets sent to their email?
Of course I do see potential risk of spam with this, but if it's off by default and can be toggled after a user enables it, it might be a good approach. This would eliminate the need for tracking of other info (at least for the reasons LanX originally created this thread for).
Update: possibly remove the option automatically for the user if there are three or more email bounces in a row, leaving them a /msg for if/when they do return?
| [reply]
[d/l]
[select] |
|
|
| [reply] |
|
|
|
|
|
