rename privacy "private" → "unlisted"; enable GPS for unlisted
- "unlisted" = not shown in the public feed, but GPS track, timeseries and detail JSON are all accessible by direct URL (security by obscurity) - "private" accepted as legacy alias everywhere (backward compat with existing data on disk) - New writes from Strava sync / ZIP upload / sidecar use "unlisted" - Only "no_gps" now suppresses the GPS track - isUnlisted() helper in format.ts used by all Svelte/Astro components - SCHEMA.md and CLAUDE.md document the privacy model and the distinction between "unlisted" and "no_gps"
This commit is contained in:
@@ -124,7 +124,7 @@ needed to render an activity card in a feed — no timeseries, no full track.
|
||||
| `avg_cadence_rpm` | integer\|null | no | Average cadence (rpm for cycling, spm for running). |
|
||||
| `avg_power_w` | integer\|null | no | Average power in watts. |
|
||||
| `source` | string\|null | no | Origin of data. See **Source values**. |
|
||||
| `privacy` | string | yes | One of: `public`, `blur_start`, `no_gps`, `private`. |
|
||||
| `privacy` | string | yes | One of: `public`, `blur_start`, `no_gps`, `unlisted`. (`private` is a deprecated alias for `unlisted`.) |
|
||||
| `mmp` | array\|null | no | Mean Maximal Power curve — `[[duration_s, avg_watts], ...]`. |
|
||||
| `best_efforts` | array\|null | no | Best efforts by distance — `[[distance_km, time_s], ...]`. |
|
||||
| `best_climb_m` | number\|null | no | Best single climb in metres (Kadane's algorithm). |
|
||||
@@ -165,12 +165,21 @@ timestamp alone is sufficient: `2024-06-01T073012Z`.
|
||||
|
||||
### Privacy levels
|
||||
|
||||
| Level | GPS track published | Timeseries lat/lon | Stats in index |
|
||||
| Level | GPS track published | Timeseries lat/lon | Shown in feed |
|
||||
|---|---|---|---|
|
||||
| `public` | Full track | Included | Yes |
|
||||
| `blur_start` | First/last 200 m removed | Trimmed | Yes |
|
||||
| `no_gps` | Not published | Not included | Yes |
|
||||
| `private` | Not published | Not included | No (not in index at all) |
|
||||
| `public` | Full track | Included | Yes — everyone |
|
||||
| `blur_start` | First/last 200 m removed | Trimmed | Yes — everyone |
|
||||
| `no_gps` | Not published | Not included | Yes — everyone |
|
||||
| `unlisted` | Full track | Included | No — owner only (via direct URL) |
|
||||
| `private` | *(deprecated alias for `unlisted`)* | Included | No — owner only |
|
||||
|
||||
**`unlisted`** activities are not shown in the public feed but are fully accessible
|
||||
by direct URL — the GPS track, timeseries, and detail JSON are all served as normal
|
||||
static files. This is "security by obscurity": knowing the URL is sufficient to
|
||||
access the activity. If you need true data exclusion, use `no_gps` for GPS removal
|
||||
while keeping stats public, or delete the activity entirely.
|
||||
|
||||
The legacy `private` value is accepted everywhere `unlisted` is valid.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user