Shared dashboards#

The account owner can share a read-only link to a site. An editor or a viewer cannot create, list, extend, or revoke one.

Choose the panels: traffic, sources, pages, goals, notes, funnels, campaigns, alerts, and live. Leave the From and Through dates blank to let the viewer pick a period, or set both dates to lock the range. A rolling range is the last 1 to 366 days and moves with the site clock. A fixed range needs both dates. A password, a passcode, an expiry, and a view limit are optional. The expiry is a date, or a preset of 7 or 30 days. The view limit is how many times the link can open. Leave it empty for no limit. A country, device, or source can lock the link to that segment. The widget is a visitors chart, a counter, or a visitors-today count.

The token is shown once, on the page that created or rotated it. It is stored as a hash. That same page shows a share card: the title, the short link, a QR code, and the expiry. The picture is an SVG drawn by this server. A named link gets its own card, titled with the recipient. ANTICS_PUBLIC_URL, when it is an origin, is written in front of the short link. The card prints by itself.

A new password is stored as argon2id. An older salted hash still opens, and a correct password replaces it with argon2id. A visitor who enters that password gets a cookie named antics_unlock. It is HttpOnly, Secure, and SameSite=Strict, and its path is /d/ plus that share. It lasts four hours and opens only that share. The server signs it with ANTICS_UNLOCK_SECRET, which must be at least 32 characters. The signature covers the share id, the passphrase version, and the expiry. The stored password hash is not the key. A missing or short secret refuses the cookie. Replacing or clearing the password bumps that version and makes older cookies stop working. Too many wrong passwords on one link, or from one IPv4 /24 or IPv6 /48, are turned away. Those attempts are counted separately from passcode attempts. A passcode is stored as argon2id. The plaintext is not stored. A visitor enters it once on a small page, and a correct passcode sets a short-lived cookie for that link only. The cookie is HttpOnly, Secure, and SameSite=Strict. It lasts four hours. Replacing or clearing the passcode makes older cookies stop working. The list shows a lock when a passcode is set. A wrong passcode does not count as an open, and too many wrong attempts from one address or on one link are turned away. The attempt list is capped per link. A full list drops the oldest entries, so one link cannot crowd out the others. An editor or a viewer cannot set one. An expired or revoked link does not open even when the cookie is still present. Rotate replaces the token. Revoke removes one link. Revoke all removes every link for the site. Extend expiry pushes an existing expiry later by 7 or 30 days, or to a later date, and keeps the same link. The row is read again in that write. An expiry that has already passed is refused. Revoke that link and issue a new one. A revoked link stays revoked. A public view, a password upgrade, and a save also read the row again in that write, so a revoke in between does not put the token back. The save form sends the time it was loaded. If the link changed after that, the save is refused and asks you to reload. Saving an expired link is refused, and the save does not clear that expiry. The list has one-click buttons for 7 days and 30 days, and a revoke button. Set expiry replaces the date on a share or a named link. The new time has to be after now. An expiry that has already passed is refused. Revoke that link and issue a new one. Shorten 7 days pulls an existing expiry earlier when that result is still after now. When it would not be, the button is disabled. To close a link now, revoke it. A named link can gain or clear its view limit after it is issued. An expiry change and a view limit change read the row and write it in one commit, and the token stays. The page lists every link on the account that expires in the next 3 days. Revoke expired removes links that are already past their expiry, and that share takes its named links with it. Revoke unused shows the shares that have never been opened, and only when every named link on that share is unopened too. Confirming removes that list. The open counts are checked again in the same write. Those deletes drop the id index. Both take effect on the next request. A link can be changed without rotating it. Changing the view limit does not rotate the link. Pause closes the public page without retiring the token. Resume opens that same link. A paused share pauses its named links too. Pausing one named link leaves the share and the other named links open. The public page answers the same as an unknown link. The list shows Open, Paused, Expired, or View limit reached, and the views used out of the cap when one is set. It also shows when the link was created, when it expires, how many times it opened, and the last open. It also lists each view, unlock, failed password attempt, and lockout. The network column is the visitor’s IPv4 /24 or IPv6 /48, the same mask as a viewer. An older line may still show an IPv6 /64. A raw address is not stored. Wrong passwords are counted per link and per that same network. The wait grows after each failure, and then the link locks. A correct password clears the failure count for that link and that network. The network is the connecting peer, unless that peer is in ANTICS_TRUSTED_PROXY_CIDRS. A trusted peer uses the rightmost address in X-Forwarded-For that is not itself a trusted proxy, and uses CF-Connecting-IP only when that chain has no such address. An empty list uses the peer, and a header from an untrusted peer does not change the network. A lockout is its own line in the log. The account owner’s signed-in session is not counted and is not locked out. Download access CSV saves those rows. The log keeps the newest 128 events. The settings page shows eight at a time, newest first, with newer and older links. Each share and named link also keeps a visit log: the UTC time, the route (page, widget, JSON, or live), the outcome (opened, expired, paused, or not available), and the referrer host. An address, a user agent, and the token are not stored. The settings page shows 20 at a time, newest first, and Download visit CSV saves every stored row. A refused visit is recorded only when the share exists, and it is not counted as an open. The visitor still sees the same unavailable page as an unknown link. ANTICS_SHARE_VISIT_DAYS is how many days to keep, from 1 to 3660, and it defaults to 90. Older lines are dropped when a visit is recorded, at boot, and every hour. Each link also shows a visit timeline: the last 14 UTC days as a bar sparkline, like the daily opens chart. Each bar is labeled with the date and the count, and a table of those days is included for a screen reader. The count appears when a day is hovered or focused. the last visited time, and the number of stored visits. A paused visit and an expired visit count. An address, a user agent, and the token are not on the timeline. A link that expires within three days wears an Expiring soon badge and a single Extend 7 days button. Download counts saves one row per link: the name, the visits, the last visit, and the expiry. A named link is its own row. The token is not in the file. Someone who is not the owner does not receive it. A viewer can leave a short note or a reaction on a panel that the link shows. A reaction is Useful, Unclear, or Thanks. A note is 1 to 280 characters. The page shows the note with HTML escaped. No account is required. The note is stored on that share. A raw address, a user agent, and the token are not stored. A new share starts with comments off, and so does a new named link. The owner turns comments on for that one link. The public page sets a viewer cookie to a fresh id signed with that share’s salt. A visit that still sends the older shared id receives a new one. Two comments a minute and five notes are accepted from one signed viewer. One IPv4 /24 or IPv6 /48 can leave ten times that, twenty a minute and fifty notes, so clearing the cookie does not open a fresh cap forever. A cookie the viewer invents uses that network limit. The link accepts eight a minute. A full log of 80 comments refuses the next one and keeps the older comments. The owner sees the notes on the settings page, newest first, with counts of comments, hidden notes, and blocked viewers. The owner can hide one, show it again, delete one, or block that viewer id. Hiding keeps the note on the owner page and leaves it off the public page. Blocking stops that viewer id from leaving another note. Each of those actions is kept in an audit list on the settings page. Turning comments off keeps the notes already stored and hides them from the public page. An expired, revoked, paused, or closed link does not take a new note. A named link keeps its own notes. The settings page shows what arrived since the owner last looked: new comments, including hidden ones, and visits that opened. An expired, paused, or unavailable visit is not a read. The newest few are listed. Mark as seen stores the time on that share. A later comment or opened visit shows up again. The time is not part of the link signature, and the page does not send mail. A named link keeps its own time. An address, a user agent, a mark, and the token are not shown. The settings page shows a visit summary for that share: a sparkline of visits per day for the last 30 UTC days, the first visit, the last visit, and unique visitors. The visitor mark lasts one UTC day, so the same person on another day counts again. A browser that sends no cookie is the same masked prefix the tracker uses for a visitor bucket: an IPv4 /24 or an IPv6 /48, with an IPv4-mapped address masked as IPv4, and that UTC day. The id is the same until midnight and a different id after, so the next day adds one viewer and the same day does not add another. Two addresses in one prefix are one viewer that day. The raw address is not the id. An address is not shown. A paused or expired visit is stored after the response is sent, and it uses the same per-link rate limit as an open. Past that limit the visit is not stored. The visitor still sees the same page. A full queue drops the visit instead of waiting. A link that has reached its view limit shows a closed page. That page does not say the view limit closed the link, and a valid unlock cookie does not open it. An expired link shows “This link has expired.” and that visit is counted. An expiry that is not a timestamp is expired. A link that is both expired and at its view limit still shows that expired page, and the visit is counted. A paused link stays unavailable even when it has also expired, and that visit is not counted. A revoked link and an unknown link stay unavailable, and a wrong signature stays unavailable even when the link has expired. An owner can also issue a named link for one person, such as Reviewer A. That link has its own view limit, expiry, and revoke. It copies the panels and the dates, and it does not ask for the share’s password. The access history and the CSV name that recipient. Each named link on the share page shows the first view, the last view, the views used against its cap, and a sparkline of views per day. Revoke this recipient removes that link and leaves the others. The named link also offers Extend 7 days, Extend 30 days, Shorten 7 days, Set expiry, and Save view limit. Saving a view limit does not rotate the link. An empty view limit clears the cap. A CSV cell whose first character after Unicode whitespace is =, +, -, @, a tab, or a carriage return is quoted and prefixed with an apostrophe. The same quoting is used for an export cell and a conversion cell. Revoking the share revokes its named links in the same write. A named link is kept only when the parent is still present and unexpired. It stops opening when the parent is missing. An expired parent shows the expired page, and that visit is counted on the named link. A parent that is paused stays unavailable even when that parent has also expired, and the named link is not counted. A named link that has its own expiry stays unavailable when its parent is paused or gone, and that visit is not counted. The public page, the widget, the live view, and the JSON return no dashboard data for an expired, capped, or revoked link. Those checks run before a password is tried, so a dead link does not record an unlock attempt or a lockout. An expired visit is counted. A paused link, a revoked link, an unknown link, a capped link, and a wrong password are not. The list also downloads a CSV of the last 30 days. Each row is the day, the opens, and the unique viewers that day. The file does not include an address, the salt, or the token. The used count is stored after the passphrase succeeds. Several reservations can share one write. A failed read or a cancelled request gives that count back. A wrong password does not take a count. A link that has already reached its cap answers 410 before the password form. A viewer who opened it during the cookie window can still refresh. The first open sets a cookie named antics_open for 30 minutes. It is HttpOnly, Secure, and SameSite=Strict, signed with ANTICS_UNLOCK_SECRET and the label antics-open-session-v1, over the share id and the expiry. A live poll or a JSON refresh that sends it does not take another count. A missing secret leaves every refresh counted. The per-day series is still written at most once a minute. The owner list also shows opens per day for the last 30 days and how many distinct viewers opened the link in that window. A viewer is a hashed cookie, or, when the browser sends no cookie, the masked prefix for that UTC day. The prefix is an IPv4 /24 or an IPv6 /48, and an IPv4-mapped address is masked as IPv4. The id is the same until midnight and a different id after. The raw address is not stored. That count is a lower bound too: the mark list stops at 256, and marks still waiting in memory are lost on restart.

The same page shows the total views, the last viewed time, and the referrer domain of each admitted view. Only the domain is kept. A full URL, a path, a query, and an address are not stored, and there is no per-visitor row. A missing referrer is Direct. A value that is not an http or https hostname is Other. Days older than the 30-day window roll into Earlier. When a day has more domains than the list can show, the rest roll into Other. A view is counted after the signature and the pause check. An expired visit is counted too, and only the domain is stored. A paused link, an unknown link, a bad signature, and a wrong password do not add a referrer.

A new public page is /d/{token}.{signature}. A link stored before signatures were required still opens from the token alone. A missing signature or a wrong signature does not open. The page is rate-limited and marked noindex. A new embed uses the signed path:

<iframe src="/d/{token}.{signature}/widget" title="Visitors" width="320" height="220" style="border:0" referrerpolicy="no-referrer"></iframe>

Use height 140 for a counter and 120 for visitors today. The chart and the counter use the locked range, or the last 30 days. Visitors today counts the current local day and needs the traffic panel.

The page, the widget, and the JSON carry counts and labels: a page path, a referrer domain, a goal name, and a note. They do not include a visitor identifier or the raw events. A note on the shared page does not name who wrote it. When the notes panel is on, the visitor chart draws those notes as markers. An alerts panel lists fired alerts by day and metric, and those markers sit on the visitor chart when notes or alerts are on. A tag on the public page limits the notes and the markers. The widget stays a visitor chart. The live panel shows visitors in the last 5 and 30 minutes, one bar per minute, and the current pages, referrers, and countries. Its list is recent pages and events, not a trail of one visitor. A link with no password refreshes that panel every few seconds. The widget does not include it.