01-02-2019
Well, we don't need to invoke on login, because sometimes a user will not logout for days or weeks.
We can invoke when user views any page, but I guess the best is "showthread" because anyone who is looking at a thread, is "active"...
Regarding your badging logic, I thought you were going to write badge logic for consecutive days active, no?
Your logic seems to only count days, consecutive days or not....
Is that want you want? Just counting days? Not consecutive days?
3 More Discussions You Might Find Interesting
1. What is on Your Mind?
Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid:
https://www.unix.com/members/1-albums215-picture991.png
The prototype HTML code for this layout:
<style>
.fa-badge-grid {
font-size: 1.5em;
}
.row {
... (38 Replies)
Discussion started by: Neo
38 Replies
2. What is on Your Mind?
Dear All,
Here is the current status of the badging system:
The Beta 1 phase of the new badging system is close to completion.
42 prototype badges have been "allocated"
6 prototype badge slots are held in reserve
The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies
3. What is on Your Mind?
I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT DEBIAN
calendarserver_purge_events
CALENDARSERVER_PURGE_EVENTS(8) BSD System Manager's Manual CALENDARSERVER_PURGE_EVENTS(8)
NAME
calendarserver_purge_events -- Darwin Calendar Server event clean-up utility
SYNOPSIS
calendarserver_purge_events [--config file] [--days number] [--dry-run] [--verbose] [--help]
DESCRIPTION
calendarserver_purge_events is a tool for removing old events from the calendar server. By default, events older than 365 days are removed,
but the user can specify the number of days in the past to use as a cut-off. Repeating events that have any occurrences after the cut-off
day are not removed.
calendarserver_purge_events should be run as a user with the same priviledges as the Calendar Server itself, as it needs to read and write
data that belongs to the server.
OPTIONS
-h, --help
Display usage information
-f, --config FILE
Use the Calendar Server configuration specified in the given file. Defaults to /etc/caldavd/caldavd.plist.
-d, --days NUMBER
Specify how many days in the past to retain. Defaults to 365 days.
-n, --dry-run
Calculate and display how many events would be removed, but don't actually remove them.
-v, --verbose
Print progress information.
FILES
/etc/caldavd/caldavd.plist
The Calendar Server configuration file.
SEE ALSO
caldavd(8)
BSD
June 17, 2009 BSD