Merge branch 'docs/v2.14.0-doc-review': documentation review for v2.14.0

This commit is contained in:
Phil committed 2026-11-10 15:35:00 -07:00
commit 058b1959f9
46 files changed
+476 -216

No files matched your search

+9 -6
View File
@@ -1,4 +1,4 @@
# StarPunk configuration template (v2.10.1)
# StarPunk configuration template (v2.14.0)
#
# Copy to .env and fill in your values. DO NOT commit .env.
# Every variable here is read by starpunk/config.py. Uncommented lines are
@@ -124,10 +124,11 @@ CSRF_ENABLED=true
# WEBMENTION
# =============================================================================
# Receive webmentions at /webmention (default: true)
# Webmention endpoint at /webmention, its Link header, and showing responses
# (webmentions and backfeed) on notes; sending is not affected (default: true)
# WEBMENTION_ENABLED=true
# Background worker that verifies received webmentions and sends outgoing
# ones (default: true)
# Background worker that verifies received webmentions, sends outgoing ones,
# and sends response notifications (v2.14.0) (default: true)
# WEBMENTION_WORKER_ENABLED=true
# Seconds between queue checks (default: 10) and after an error (default: 60)
# WEBMENTION_POLL_INTERVAL=10
@@ -201,7 +202,8 @@ THREADS_USERNAME=
# SYNDICATION_POLL_INTERVAL=10
# Backfeed (v2.13.0, ADR-073): bring likes, reposts, quotes and replies to the
# crossposts back to the note as responses. Needs the read scopes above.
# crossposts back to the note as responses. Needs the read scopes above, and
# runs in the syndication worker, so at least one target must be configured.
# BACKFEED_ENABLED=false
# Stop checking a note's responses after this many days (default: 90)
# BACKFEED_MAX_AGE_DAYS=90
@@ -216,7 +218,8 @@ THREADS_USERNAME=
# apprises://apprise.example.com/KEY (an apprise-api server)
# NOTIFY_URLS=
# What to notify: reply, mention, quote, like, repost, bookmark, problems
# (a crosspost that failed for good, a silo refusing backfeed)
# (a crosspost that failed for good, a silo refusing backfeed). Names are
# case-insensitive; unknown ones are ignored.
# NOTIFY_EVENTS=reply,mention,quote,problems
# Priority of every message, added to URLs that don't set one:
# low, moderate, normal, high, emergency (Gotify also takes 0-10)
+2 -5
View File
@@ -634,7 +634,7 @@ Webmention now follows the [W3C Recommendation](https://www.w3.org/TR/webmention
- Successful uploads logged at INFO level with file details
- Removed duplicate logging in Micropub media endpoint
## [1.4.0rc1] - 2025-12-16
## [1.4.0-rc.1] - 2025-12-16
### Added
@@ -2177,7 +2177,4 @@ This is a release candidate for testing. Stable 1.0.0 will be released after tes
- ADR-007: Slug generation algorithm
- ADR-008: Versioning strategy
[Unreleased]: https://github.com/YOUR_USERNAME/starpunk/compare/v0.4.0...HEAD
[0.4.0]: https://github.com/YOUR_USERNAME/starpunk/compare/v0.3.0...v0.4.0
[0.3.0]: https://github.com/YOUR_USERNAME/starpunk/compare/v0.1.0...v0.3.0
[0.1.0]: https://github.com/YOUR_USERNAME/starpunk/releases/tag/v0.1.0
Releases are tagged `vX.Y.Z` in https://git.thesatelliteoflove.com/phil/StarPunk
+3 -3
View File
@@ -8,7 +8,7 @@ This file contains operational instructions for Claude agents working on this pr
- All Python commands must be run with `uv run` prefix
- Example: `uv run pytest`, `uv run flask --app app.py run --debug`
- There is no `pyproject.toml`: create the environment with `uv venv --python 3.14 && uv pip install -r requirements-dev.txt`
- Tests need `SESSION_SECRET` set: `SESSION_SECRET=test uv run pytest`. The full suite takes about 6 minutes, 5 of them in `tests/test_migration_race_condition.py`; add `--ignore=tests/test_migration_race_condition.py` while iterating, but run everything before a release
- Tests need `SESSION_SECRET` set. Locally, run only the tests for the area you changed (`SESSION_SECRET=test uv run pytest tests/test_<area>.py`); CI runs the full suite (about 6 minutes) on every `vX.Y.Z` tag, so don't run the whole suite yourself unless asked
- Local login without OIDC: `DEV_MODE=true` and `DEV_ADMIN_ME` in `.env`, then `/dev/login`
- Setup details: `docs/standards/development-setup.md`
@@ -50,12 +50,12 @@ When invoking the agent-developer, always remind it to:
5. **Follow git protocol**
- Adhere to git branching strategy in `docs/standards/git-branching-strategy.md`
- Create feature branches for non-trivial changes, in their own git worktree (`<prefix>/vX.Y.Z-description`, prefixes `feat/`, `fix/`, `ci/`, `docs/`)
- Create feature branches for non-trivial changes, in their own git worktree (`<prefix>/vX.Y.Z-description`, prefixes `feat/`, `fix/`, `ci/`, `chore/`, `docs/`)
- Write clear commit messages (`feat: ... (vX.Y.Z)`)
## Release Process
Follow "Release process" in `docs/standards/git-branching-strategy.md`. In short: work in a worktree on a `feat/`/`fix/` branch → bump `__version__` and `__version_info__` → `CHANGELOG.md` entry → design note in `docs/design/vX.Y.Z/` (or ADR amendment) → full test suite → commit → `git merge --no-ff` into `main` ("Merge branch '<branch>' for vX.Y.Z release") → annotated tag `vX.Y.Z` → push `main` and the tag. CI (`.gitea/workflows/build-container.yml`) runs the tests and publishes the image; production is then updated from the separate Ansible deployment repository. Back up the database before deploying a release with a migration.
Follow "Release process" in `docs/standards/git-branching-strategy.md`. In short: work in a worktree on a `feat/`/`fix/`/`chore/` branch → bump `__version__` and `__version_info__` → `CHANGELOG.md` entry → design note in `docs/design/vX.Y.Z/` (or ADR amendment) → tests for the changed area → commit → `git merge --no-ff` into `main` ("Merge branch '<branch>' for vX.Y.Z release") → annotated tag `vX.Y.Z` → push `main` and the tag. CI (`.gitea/workflows/build-container.yml`) runs the full test suite and publishes the image; production is then updated from the separate Ansible deployment repository. Back up the database before deploying a release with a migration.
Merging to `main`, tagging, pushing and deploying happen only when the project owner asks for a release.
+15 -8
View File
@@ -24,8 +24,9 @@ what changed in each release is in [CHANGELOG.md](CHANGELOG.md).
Micropub apps (consent screen, tokens, revocation, Connected Apps page)
- Admin login through any OpenID Connect provider (e.g. Pocket ID)
- [Webmention](https://www.w3.org/TR/webmention/): receiving (verified,
moderated, rate-limited) and sending; replies, likes and reposts shown on
each note
moderated, rate-limited) and sending; replies, quotes and mentions shown
on each note, with likes, reposts and replies as a line of counts with
hover cards and `<indie-action>` web actions
- [WebSub](https://www.w3.org/TR/websub/) with a built-in hub, so readers get
new posts within seconds
- [Microformats2](https://microformats.org/wiki/h-entry): h-entry, h-feed and
@@ -38,10 +39,15 @@ what changed in each release is in [CHANGELOG.md](CHANGELOG.md).
- POSSE crossposting to GoToSocial/Mastodon, Bluesky and Threads, with
`u-syndication` links back; edits and deletes follow, native likes and
boosts where the target supports them
- Backfeed: likes, reposts and replies to crossposts on GoToSocial and
Bluesky (and Bluesky quotes), and replies on Threads (with its like and
repost counts), come back as responses (`BACKFEED_ENABLED`, ADR-073)
**Operations**
- Migrations applied automatically at startup
- `/health` endpoint, `/admin/health` diagnostics, structured logs
- Notifications of new responses and crossposting problems through
Apprise (Gotify, ntfy, email…; `NOTIFY_URLS`, ADR-074)
- Fetches of user-supplied URLs are limited to public addresses, size and
time
@@ -54,7 +60,6 @@ git clone https://git.thesatelliteoflove.com/phil/StarPunk.git && cd StarPunk
cp .env.example .env # set SITE_URL, ADMIN_ME, SESSION_SECRET, OIDC_*
docker build -t starpunk -f Containerfile .
docker run -d --name starpunk -p 127.0.0.1:8000:8000 --env-file .env \
-e FLASK_ENV=production -e FLASK_DEBUG=0 \
-v ./starpunk-data:/data starpunk
```
@@ -72,8 +77,8 @@ redirect URI with your OIDC provider. Details:
uv venv --python 3.14
uv pip install -r requirements-dev.txt
cp .env.example .env # set SESSION_SECRET; add DEV_MODE=true and DEV_ADMIN_ME
uv run flask --app app.py run --debug # http://localhost:5000
SESSION_SECRET=test uv run pytest # tests (about 6 minutes)
uv run flask --app app.py run --debug # http://localhost:5000
SESSION_SECRET=test uv run pytest tests/test_<area>.py # tests for what you changed; CI runs the full suite
```
With `DEV_MODE=true`, `/dev/login` logs you in without OIDC. Never enable
@@ -86,13 +91,15 @@ All settings are environment variables (or a `.env` file), each listed with
its default in [`.env.example`](.env.example). Required in production:
`SESSION_SECRET`, `SITE_URL`, `ADMIN_ME`, `OIDC_ISSUER`, `OIDC_CLIENT_ID`,
`OIDC_CLIENT_SECRET` and `OIDC_ADMIN_SUB`. Crossposting is enabled by
setting a target's credentials.
setting a target's credentials. Backfeed is off unless
`BACKFEED_ENABLED=true`; notifications start when `NOTIFY_URLS` is set.
## Data and backups
Everything lives in the data directory (`/data` in the container): the
SQLite database, note files in `notes/`, uploaded media and logs. Back it
up regularly, and always before upgrading to a release with a migration.
SQLite database, note files in `notes/`, uploaded media, saved response
avatars in `avatars/`, the Threads token (`threads_token.json`) and logs.
Back it up regularly, and always before upgrading to a release with a migration.
## Documentation
+8 -7
View File
@@ -1,9 +1,11 @@
# Architecture Documentation Index
This directory describes the **current** design of StarPunk (v2.10.1). Per
This directory describes the **current** design of StarPunk (v2.14.0). Per
[../DOCUMENTATION.md](../DOCUMENTATION.md) it is updated at the end of each
release. Decisions and their history are in [../decisions/](../decisions/);
per-release designs and reports are in [../design/](../design/).
per-release designs and reports are in [../design/](../design/). The
original v0.x technology choices are kept in
[../design/v0.x/technology-stack-legacy.md](../design/v0.x/technology-stack-legacy.md).
## Documents
@@ -11,12 +13,11 @@ per-release designs and reports are in [../design/](../design/).
|----------|-------------|
| [overview.md](overview.md) | System overview: purpose, request flow, modules and routes, background workers, storage, auth model, URL surface, caching, security posture |
| [technology-stack.md](technology-stack.md) | Current runtime, Python dependencies, standards implemented, testing and CI |
| [database.md](database.md) | SQLite schema after migrations 001–019, migration runner and its lock, connection pool |
| [database.md](database.md) | SQLite schema after migrations 001–021, migration runner and its lock, connection pool |
| [deployment.md](deployment.md) | Container image stages, CI workflow, release process, `/data` layout, reverse proxy, all environment variables |
| [simplified-auth-architecture.md](simplified-auth-architecture.md) | Admin login via OpenID Connect and the built-in IndieAuth server that issues Micropub tokens (ADR-064) |
| [indieweb-protocols.md](indieweb-protocols.md) | How Micropub, IndieAuth, Webmention, microformats2, WebSub and the feeds are implemented, with compliance status and known gaps |
| [syndication-architecture.md](syndication-architecture.md) | Crossposting (POSSE) to GoToSocial, Bluesky and Threads: syndications table, worker, reconcile rules |
| [technology-stack-legacy.md](technology-stack-legacy.md) | Historical: the original v0.x technology choices (IndieLogin era); not current |
| [indieweb-protocols.md](indieweb-protocols.md) | How Micropub, IndieAuth, Webmention, microformats2, WebSub and the feeds are implemented (including backfeed responses, web actions and notifications), with compliance status and known gaps |
| [syndication-architecture.md](syndication-architecture.md) | Crossposting (POSSE) to GoToSocial, Bluesky and Threads: syndications table, worker, reconcile rules, backfeed of responses (ADR-073) |
## Where to start
@@ -37,4 +38,4 @@ per-release designs and reports are in [../design/](../design/).
---
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
+26 -12
View File
@@ -1,8 +1,8 @@
# Database Architecture
**Version**: 2.11.0 (2026-11-03)
**Version**: 2.14.0 (2026-11-10)
**Status**: Current. Verified against a database created by `create_app()`
with migrations 001–019.
with migrations 001–021.
StarPunk uses one SQLite file, `starpunk.db` under `DATA_PATH` (`/data` in
the container), in WAL mode. Note *content* is not in the database: it lives
@@ -73,6 +73,8 @@ Background: [ADR-031](../decisions/ADR-031-database-migration-system-redesign.md
| `017_websub_hardening.sql` | 2.10.1 | `websub_intents.request_id`, `requested_topic`, `callback_ip`; `websub_subscriptions.callback_ip` |
| `018_foreign_key_cleanup.sql` | 2.11.0 | Removes rows orphaned while foreign keys weren't enforced |
| `019_shared_rate_limits.sql` | 2.11.0 | `rate_limits` (counters shared by all processes) |
| `020_backfeed.sql` | 2.13.0 | Rebuilds `webmentions` adding `origin`, `remote_id`, the `quote` type and an index on (`target_note_id`, `origin`); `syndications.backfeed_next_at`, `backfeed_checked_at`, `backfeed_claimed_until`, `backfeed_attempts`, `backfeed_error`, `backfeed_backfill`, `likes_count`, `reposts_count`, `quotes_count` |
| `021_notifications.sql` | 2.14.0 | `webmentions.notified_at`; existing rows are marked as notified |
New migrations are numbered `NNN_description.sql`, must be safe to run inside
one transaction, and should use `IF NOT EXISTS` where SQLite allows it.
@@ -143,17 +145,20 @@ above.
### IndieWeb interactions
**`webmentions`**: received webmentions, one per (`source_url`,
`target_url`).
**`webmentions`**: received webmentions and backfed silo responses
(v2.13.0), one per (`source_url`, `target_url`).
| Column | Purpose |
|--------|---------|
| `target_note_id` | The note mentioned (SET NULL if the note is deleted) |
| `mention_type` | `reply`, `like`, `repost`, `bookmark`, `mention` |
| `mention_type` | `reply`, `like`, `repost`, `bookmark`, `mention`, `quote` |
| `author_name`, `author_url`, `author_photo`, `content_snippet` | From the source's mf2 (content sanitised) |
| `source_post_url`, `source_published` | The source entry's own `u-url` and `dt-published` |
| `validation_status` | `pending`, `valid`, `invalid`, `error` (set by the worker) |
| `moderation_status` | `pending`, `approved`, `hidden`, `deleted` (auto-approved when `WEBMENTION_AUTO_APPROVE`) |
| `moderation_status` | `pending`, `approved`, `hidden`, `deleted` (auto-approved when `WEBMENTION_AUTO_APPROVE`). `deleted` is a tombstone: deleting in the admin keeps the row, so a re-sent webmention or the next backfeed check doesn't bring it back; re-validation keeps `hidden` and `deleted` |
| `origin` | `webmention`, or the silo it was backfed from (`gotosocial`, `bluesky`, `threads`) |
| `remote_id` | Silo id of a backfed response (or of the person, for likes and reposts) |
| `notified_at` | When the owner was notified of it (v2.14.0); NULL means not yet |
| `validation_error`, `validated_at`, `received_at`, `updated_at` | Bookkeeping |
**`webmention_queue`**: outgoing webmentions, one per (`source_url`,
@@ -178,7 +183,12 @@ the note should be on that target; `remote_id` and `remote_url` identify the
remote post. `state` (`pending`, `synced`, `failed`), `version` (bumped on
every note change, so an edit made during a send is not lost), `attempts`,
`last_error`, `next_attempt_at` and `claimed_until` (a 5-minute lease that
lets any gunicorn process take the row exclusively) drive the worker. See
lets any gunicorn process take the row exclusively) drive the worker.
Backfeed (v2.13.0) adds `backfeed_next_at`, `backfeed_checked_at`,
`backfeed_claimed_until` (its own lease), `backfeed_attempts`,
`backfeed_error` and `backfeed_backfill` (set while a backfill is due), and
`likes_count`, `reposts_count`, `quotes_count`: silo-only counts (all of
Threads; elsewhere people who opted out). See
[syndication-architecture.md](syndication-architecture.md).
### WebSub
@@ -201,7 +211,10 @@ pending row of each kind. `attempts`, `next_attempt_at`, `last_error`.
**`site_state`**: key/value pairs. `content_version` is bumped whenever a
public note changes; every gunicorn process compares it to decide whether
its cached feed data is stale.
its cached feed data is stale. Backfeed keeps `backfeed_backfill_last` (spacing
backfill checks across processes), `backfeed_backfill_started` and
`backfeed_backfill_finished`; notifications keep `notify_last_error` (shown
in the admin, cleared by a successful send).
### Bookkeeping
@@ -223,7 +236,8 @@ server process enforces one shared limit. Old windows are pruned as it goes.
it goes back to the pool, rolled back first if a transaction was left
open.
- **Direct connections**: the migration runner, the FTS start-up check, the
webmention worker and sender, reply-context fetching and search helpers
webmention worker and sender, the notification sweep (`notifications.py`),
avatar upkeep (`avatars.py`), reply-context fetching and search helpers
open their own `sqlite3.connect(db_path)` connections.
- WAL mode lets readers carry on while one writer writes. The four gunicorn
processes and the worker threads share the one file; writes are short, so
@@ -233,9 +247,9 @@ server process enforces one shared limit. Old windows are pruned as it goes.
The application does not back itself up. A consistent copy needs the
database (use SQLite's online backup, e.g. `sqlite3 starpunk.db ".backup …"`,
because of WAL) together with `notes/` and `media/`; see
[deployment.md](deployment.md).
because of WAL) together with `notes/` and `media/`. `avatars/` is optional:
missing avatars are fetched again. See [deployment.md](deployment.md).
---
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
+31 -23
View File
@@ -1,6 +1,6 @@
# Deployment Architecture
**Version**: 2.10.1 (2026-11-03)
**Version**: 2.14.0 (2026-11-10)
**Status**: Current
How StarPunk is built, configured and run in production. The production site
@@ -70,21 +70,18 @@ authentication.
lower case.
4. Remove the builder and log out, even after a failure.
There is no CI on branches or pull requests; run the tests locally before
merging (see [technology-stack.md](technology-stack.md#testing)).
There is no CI on branches or pull requests. Locally, run the tests for the
area you changed; CI runs the full suite on the tag (see
[technology-stack.md](technology-stack.md#testing)).
## Release process
1. Finish the change on a branch, including the version bump in
`starpunk/__init__.py` (`__version__`, `__version_info__`) and a
`CHANGELOG.md` entry.
2. Merge to `main`.
3. Tag the merge commit `vX.Y.Z` and push the tag. CI tests, builds and
pushes the image.
4. In the Ansible-managed deployment, change the StarPunk image tag to the new
version and apply it. The container is recreated from the new image; new
migrations run automatically at start-up.
5. Check `/health` reports the new version.
Branching, version bump, changelog, merge and tagging are in
[git-branching-strategy.md](../standards/git-branching-strategy.md#release-process).
Pushing a `vX.Y.Z` tag makes CI test, build and push the image. Then, in the
Ansible-managed deployment, set `starpunk_version` to the new tag and deploy
the `starpunk` service: the container is recreated from the new image and new
migrations run at start-up. Check that `/health` reports the new version.
Rolling back means deploying the previous tag. Migrations are not reversed
automatically, so a release with a migration needs a database backup first
@@ -105,6 +102,7 @@ persistent is there; the image itself holds no state.
| `media/YYYY/MM/` | Uploaded images and their variants; `media/.tmp/` while processing |
| `logs/starpunk.log` | Application log, rotated at 10 MB, 10 files kept |
| `webmention-worker.lock`, `websub-worker.lock` | `flock` files choosing the process that runs each worker |
| `avatars/<sha256>.webp` | Saved copies of response authors' avatars (v2.13.0), served at `/avatars/`; unused ones removed weekly |
| `threads_token.json` (+ `.lock`) | Current Threads access token, refreshed daily (only with Threads configured) |
| `debug/` | Failed uploads, only with `DEBUG_SAVE_FAILED_UPLOADS=true`; cleaned up after `DEBUG_FILE_MAX_AGE_DAYS` |
@@ -161,6 +159,7 @@ unless noted.
| `INDIEAUTH_TOKEN_LIFETIME_DAYS` | `90` | Lifetime of Micropub access tokens |
| `DEV_MODE` | `false` | Enables `/dev/login`; never in production |
| `DEV_ADMIN_ME` | empty | Required when `DEV_MODE=true` |
| `CSRF_ENABLED` | `true` | CSRF tokens on admin forms, logout and IndieAuth consent; leave on |
`TOKEN_ENDPOINT` and `INDIELOGIN_URL` are v1 settings; if present they are
ignored with a warning.
@@ -190,8 +189,8 @@ ignored with a warning.
| Variable | Default | Notes |
|----------|---------|-------|
| `WEBMENTION_ENABLED` | `true` | Endpoint, `Link` header and sending |
| `WEBMENTION_WORKER_ENABLED` | `true` | |
| `WEBMENTION_ENABLED` | `true` | Endpoint, `Link` header, showing responses on notes (not sending) |
| `WEBMENTION_WORKER_ENABLED` | `true` | Verifies received and sends outgoing webmentions; saves avatars; sends response notifications |
| `WEBMENTION_POLL_INTERVAL` | `10` | Seconds |
| `WEBMENTION_ERROR_BACKOFF` | `60` | Seconds after a worker error |
| `WEBMENTION_BATCH_SIZE` | `5` | Items per pass |
@@ -219,7 +218,7 @@ starts only if at least one is.
| Variable | Default | Notes |
|----------|---------|-------|
| `GOTOSOCIAL_URL`, `GOTOSOCIAL_ACCESS_TOKEN` | empty | GoToSocial or any Mastodon-API server |
| `GOTOSOCIAL_URL`, `GOTOSOCIAL_ACCESS_TOKEN` | empty | GoToSocial or any Mastodon-API server. Token scopes: `write:statuses write:media read:search write:favourites`, plus `read:statuses read:accounts` (or `read`) for backfeed |
| `GOTOSOCIAL_NAME` | `GoToSocial` | Label in the UI and `syndicate-to` |
| `GOTOSOCIAL_VISIBILITY` | `public` | |
| `GOTOSOCIAL_MAX_CHARS` | `5000` | |
@@ -228,12 +227,22 @@ starts only if at least one is.
| `BLUESKY_SERVICE` | `https://bsky.social` | |
| `BLUESKY_NAME` | `Bluesky` | |
| `BLUESKY_MAX_CHARS` | `300` | |
| `THREADS_ACCESS_TOKEN` | empty | Long-lived token; refreshed automatically into `threads_token.json` |
| `THREADS_ACCESS_TOKEN` | empty | Long-lived token; refreshed automatically into `threads_token.json`. Backfeed also needs `threads_read_replies` and `threads_manage_insights` |
| `THREADS_USERNAME` | empty | |
| `THREADS_NAME` | `Threads` | |
| `THREADS_MAX_CHARS` | `500` | |
| `THREADS_MAX_MEDIA` | `4` | |
| `SYNDICATION_POLL_INTERVAL` | `10` | Seconds |
| `BACKFEED_ENABLED` | `false` | Bring responses to crossposts back to notes (v2.13.0); needs read scopes on the GoToSocial and Threads tokens |
| `BACKFEED_MAX_AGE_DAYS` | `90` | Days after posting to keep checking a crosspost's responses |
### Notifications
| Variable | Default | Notes |
|----------|---------|-------|
| `NOTIFY_URLS` | empty (off) | Apprise URLs, space- or comma-separated (v2.14.0) |
| `NOTIFY_EVENTS` | `reply,mention,quote,problems` | Also `like`, `repost`, `bookmark` |
| `NOTIFY_PRIORITY` | `normal` | Added to URLs that don't set a priority |
### Debugging
@@ -252,15 +261,14 @@ from the environment.
## Running locally
```bash
uv venv && uv pip install -r requirements-dev.txt
uv venv --python 3.14 && uv pip install -r requirements-dev.txt
cp .env.example .env # set SESSION_SECRET; DEV_MODE=true and DEV_ADMIN_ME for local login
flask --app app.py run # or: gunicorn app:app
uv run flask --app app.py run --debug # or: uv run gunicorn app:app
```
`compose.yaml` builds and runs the image with `./container-data` mounted at
`/data`; its image tag and `VERSION` values are out of date, so override them
or build with `podman build -t starpunk .`.
`compose.yaml` builds the image from this checkout (`starpunk:local`) and runs
it with `./container-data` mounted at `/data`.
---
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
+39 -14
View File
@@ -1,6 +1,6 @@
# IndieWeb and W3C Protocols
How StarPunk implements each protocol it speaks, as of v2.10.1, with its
How StarPunk implements each protocol it speaks, as of v2.14.0, with its
compliance status and the gaps that remain. Each section links to the
decision records and review documents behind it.
@@ -12,6 +12,8 @@ decision records and review documents behind it.
| [Microformats2](#microformats2) | Publisher and consumer | Reviewed in v2.8.0 | `templates/`, `starpunk/mf2_utils.py`, `starpunk/author_discovery.py` |
| [WebSub](#websub) | Publisher and built-in hub (own topics only) | Adversarial review in v2.10.1 | `starpunk/websub.py`, `starpunk/websub_worker.py`, `starpunk/routes/websub.py` |
| [Feeds](#feeds) | RSS 2.0, Atom 1.0, JSON Feed 1.1, OPML 2.0 | Stable | `starpunk/feeds/`, `starpunk/routes/public.py` |
| Backfeed | Responses to crossposts read from the silo APIs and stored as webmentions (v2.13.0); see [syndication-architecture.md](syndication-architecture.md#backfeed-v2130-adr-073) | ADR-073 | `starpunk/backfeed.py` |
| [Web actions](#moderation-and-display) | `<indie-action>` on the like, repost and reply counts (v2.13.2) | Markup only | `templates/partials/responses.html` |
Crossposting to other networks (POSSE) is covered in
[syndication-architecture.md](syndication-architecture.md).
@@ -19,8 +21,10 @@ Crossposting to other networks (POSSE) is covered in
## Shared infrastructure: the SSRF-safe fetcher
Webmention (fetching sources, discovering endpoints, sending), WebSub
(verification and delivery) and Micropub (downloading remote photos) all
make requests to URLs chosen by someone else. They use
(verification and delivery), Micropub (downloading remote photos), IndieAuth
(client pages), reply contexts, crosspost link cards (v2.11.0) and response
avatars (v2.13.0; except those on StarPunk's own GoToSocial) all make
requests to URLs chosen by someone else. They use
`starpunk/webmention_ssrf.py`:
- `validate_url_for_fetch()`: http(s) only. Every address from
@@ -128,7 +132,7 @@ repost, bookmark.
| `q=syndicate-to` | any token | `{"syndicate-to": [{"uid", "name"}]}` |
| `q=source&url=...[&properties[]=...]` | create/update/delete/draft | One post as mf2 JSON. Content comes back as `{"html": ...}` if it was authored as HTML. Includes `syndication` URLs and `post-status` |
| `q=source` without `url` | same | `{"items": [...]}`, drafts included, `limit` (default 10, max 50) and `offset` |
| `q=category[&filter=...]` | same | Tags in use, most used first |
| `q=category[&filter=...]` | same | Tags on notes that aren't deleted (drafts count), most used first (v2.12.1) |
Unknown or missing `q` gets 400.
@@ -171,8 +175,7 @@ Full description, scopes and gaps:
Decision: [ADR-064](../decisions/ADR-064-oidc-admin-login-and-builtin-indieauth-server.md).
Known gaps: `scopes_supported` doesn't list `draft`. There are no
introspection, userinfo or refresh tokens. The client metadata fetch
doesn't use the pinned SSRF fetcher.
introspection, userinfo or refresh tokens.
---
@@ -239,25 +242,46 @@ Verification is asynchronous (`WebmentionWorker`, poll
- Valid: `validation_status = 'valid'`. A first-time mention gets
`moderation_status = 'approved'` if `WEBMENTION_AUTO_APPROVE` (default
true), otherwise `pending`. An update keeps the admin's earlier
moderation decision.
moderation decision, including `hidden` and `deleted`.
- Source returns 4xx (including 410), or no longer links: `invalid`,
which hides it (3.2.4 deletion).
- Network error, timeout or 5xx: a mention that was valid before stays
valid with its old data. A new one becomes `error`.
- A source that is one of the note's own syndicated copies
(`syndications.remote_url`) is `invalid` (v2.8.0).
- A source that backfeed has already stored for the note is `invalid`
("Already backfed from the silo", v2.13.0).
- **Re-send on display change** (3.1.4, v2.7.2): if what the note shows
for this webmention changed, the note's own outgoing webmentions are
re-queued. That covers a new response, a changed author or snippet, or a
change of shown/hidden. Unchanged re-validations send nothing, so two
sites doing the same don't ping-pong.
**Moderation and display.** `/admin/webmentions` lists, filters, and
approves, hides or deletes mentions, one at a time or in bulk. Changes that
alter what is shown also re-send the note's webmentions. Note pages show
approved, valid mentions grouped as replies (`u-comment h-cite`), likes,
reposts and bookmarks (facepiles), and mentions. See
[Microformats2](#microformats2).
### Moderation and display
`/admin/webmentions` lists, filters (by status, including Deleted, and by
origin), and approves, hides or deletes responses, one at a time or in bulk;
it also has the Backfill button. Deleting keeps the row as a `deleted`
tombstone, so a re-sent webmention or backfeed doesn't bring it back.
Changes that alter what is shown also re-send the note's webmentions.
Note pages show approved, valid responses. Under the note, a line of counts
(♥ likes, 🔁 reposts, 💬 replies, bookmarks) opens a card on hover or focus
listing who responded and where from, including anonymous silo counts. Each
like, repost and reply count holds an `<indie-action do with>` web action
whose fallback links to the note's crossposts (v2.13.2). The Responses
section below holds replies (`u-comment h-cite`), quotes and mentions;
backfed ones say "via <silo>". See [Microformats2](#microformats2).
### Notifications (v2.14.0, ADR-074)
With `NOTIFY_URLS` set, new valid responses (received and backfed) are sent
to the owner once through Apprise by a sweep in the webmention worker, which
sets `webmentions.notified_at` (migration 021). Likes, reposts and bookmarks
are grouped per note; which kinds are sent is set by `NOTIFY_EVENTS`
(default replies, mentions, quotes and problems). Items still unsent after
24 hours are dropped. Responses found by a backfill, or by a copy's first
check on a note older than a day, are never notified.
### Sending
@@ -339,8 +363,9 @@ representative h-card, authorship, Post Type Discovery. Decisions:
| `/note/<slug>` | `h-entry`: `p-name` only when the note starts with a `# Heading` (so plain notes have no implied name); `u-photo` as direct children above `e-content`; `u-url u-uid` with `dt-published` (RFC 3339 UTC `Z`); `dt-updated`; `p-category` with `rel=tag`; `u-syndication` links; hidden `p-author h-card` |
| Replies | `u-in-reply-to h-cite` holding the cached reply context (`p-content`, `u-url`) |
| Likes / reposts / bookmarks | `u-like-of` / `u-repost-of` / `u-bookmark-of` link with "★ Liked" / "🔁 Reposted" / "🔖 Bookmarked" |
| Received responses | `u-comment h-cite` (replies: `p-author h-card` with `u-url` on an inner link, `u-photo`, `p-name`; `e-content`; `u-url`; `dt-published`), and `u-like`, `u-repost`, `u-bookmark`, `u-mention` h-cites. Faces beyond 8 are `hidden`, not omitted |
| Received responses | `u-comment h-cite` (replies: `p-author h-card` with `u-url` on an inner link, `u-photo`, `p-name`; `e-content`; `u-url`; `dt-published`), likes, reposts and bookmarks as `u-like`, `u-repost`, `u-bookmark` h-cites in the counts line card; mentions and quotes as `u-mention` h-cites |
| `/likes`, `/tag/<tag>` | `h-feed` with `p-name`, `u-url`, `p-author h-card` |
| Response counts | `/`, `/tag/<tag>` and `/likes` show each note's like, repost and reply counts, linking to its `#responses` (v2.13.4) |
Post Type Discovery gives note, article, reply, like, repost, bookmark and
photo correctly.
+55 -27
View File
@@ -1,6 +1,6 @@
# StarPunk Architecture Overview
**Version**: 2.10.1 (2026-11-03)
**Version**: 2.14.0 (2026-11-10)
**Status**: Current. Describes the system as it is in the code today.
## Purpose
@@ -10,7 +10,9 @@ owner) writes short notes, which are published as microformats2-marked HTML
pages and as RSS, Atom and JSON feeds. The site takes part in the IndieWeb:
it accepts posts from Micropub clients, issues its own IndieAuth tokens for
them, sends and receives Webmentions, pushes feed updates with WebSub, and
crossposts (POSSE) to GoToSocial, Bluesky and Threads.
crossposts (POSSE) to GoToSocial, Bluesky and Threads. Responses to those
crossposts are pulled back and shown on the note (backfeed), and the owner
can be notified of new responses.
Guiding principle: "every line of code must justify its existence". It is a
single Flask application with server-side rendering, SQLite and plain files.
@@ -39,6 +41,9 @@ Key decisions:
[ADR-067](../decisions/ADR-067-micropub-update-delete.md) (Micropub update/delete),
[ADR-068](../decisions/ADR-068-likes-and-reposts.md) (likes and reposts),
[ADR-071](../decisions/ADR-071-websub.md) (WebSub),
[ADR-072](../decisions/ADR-072-remove-metrics-dashboard.md) (metrics dashboard removed),
[ADR-073](../decisions/ADR-073-backfeed.md) (backfeed),
[ADR-074](../decisions/ADR-074-notifications.md) (notifications),
[ADR-057](../decisions/ADR-057-media-attachment-model.md) and
[ADR-058](../decisions/ADR-058-image-optimization-strategy.md) (media),
[ADR-034](../decisions/ADR-034-full-text-search.md) (search),
@@ -70,8 +75,9 @@ Key decisions:
│ starpunk.db │ │ OIDC provider, IndieAuth │
│ notes/*.md │ │ client pages, webmention │
│ media/ │ │ sources/targets, WebSub │
│ logs/, locks │ │ callbacks, GoToSocial, │
└────────────────┘ │ Bluesky, Threads │
│ avatars/ │ │ callbacks, GoToSocial, │
│ logs/, locks │ │ Bluesky, Threads, avatars, │
└────────────────┘ │ notifications (Apprise) │
└─────────────────────────────┘
```
@@ -127,12 +133,16 @@ wait for outbound network calls; the workers make them later.
| `reply_context.py` | Fetches and caches the post a reply responds to |
| `webmention_sender.py` | Extracts links from rendered notes and queues outgoing webmentions |
| `webmention_processor.py` | Validates incoming webmentions: fetch source, parse mf2, classify, sanitise content |
| `webmention_worker.py` | Background thread working the incoming and outgoing webmention queues |
| `webmention_worker.py` | Background thread working the incoming and outgoing webmention queues; also runs avatar upkeep and the notification sweep |
| `webmention_queries.py` | Webmention queries for display and moderation |
| `webmention_ssrf.py` | SSRF-safe fetcher: public-address checks, pinned connections, manual redirects, size and time limits |
| `websub.py` | WebSub publisher (discovery headers and links, `content_version`, queueing) and hub request handling |
| `websub_worker.py` | Background thread: verification of intent, content delivery, publish pings to an external hub |
| `syndication.py` | POSSE clients (Mastodon API/GoToSocial, Bluesky, Threads), reconcile logic, syndication worker |
| `syndication.py` | POSSE clients (Mastodon API/GoToSocial, Bluesky, Threads), reconcile logic, syndication worker (its loop also calls `backfeed.process_due()`) |
| `backfeed.py` | Backfeed: reads responses to crossposts from the silos, stores them as webmentions, schedules checks and backfills |
| `avatars.py` | Saves response authors' avatars as 96 px WebP files in `avatars/`; fills missing ones and removes unused ones |
| `notifications.py` | Notifications through Apprise: the sweep of new responses and immediate problem messages |
| `csrf.py` | CSRF tokens (HMAC of the session cookie) for admin forms, logout and the IndieAuth consent |
| `rate_limiter.py` | In-memory sliding-window rate limiter |
| `errors.py` | Central error handlers |
| `feeds/` | `rss.py` (feedgen), `atom.py`, `json_feed.py`, `opml.py`, `negotiation.py` (Accept header), `cache.py` (LRU + TTL feed cache with ETags) |
@@ -144,7 +154,7 @@ wait for outbound network calls; the workers make them later.
| Blueprint | File | Paths |
|-----------|------|-------|
| `public` | `public.py` | `/`, `/note/<slug>`, `/tag/<tag>`, `/likes`, `/media/<path>`, feeds, `/opml.xml` |
| `public` | `public.py` | `/`, `/note/<slug>`, `/tag/<tag>`, `/likes`, `/media/<path>`, `/avatars/<name>`, feeds, `/opml.xml` |
| `auth` | `auth.py` | `/auth/login` (GET, POST), `/auth/callback`, `/auth/logout` (POST) |
| `indieauth` | `indieauth.py` | `/.well-known/oauth-authorization-server`, `/auth/authorize` (GET, POST), `/auth/authorize/approve`, `/auth/token` (GET, POST), `/auth/revoke` |
| `micropub` | `micropub.py` | `/micropub` (GET, POST), `/micropub/media` (POST), `/media` (POST, legacy alias) |
@@ -163,20 +173,20 @@ Jinja2 templates live in `templates/`: public pages, `admin/`, `partials/`
reposts and bookmarks) and one page per HTTP error. `templates/base.html`
carries the discovery links (`rel=micropub`, `indieauth-metadata`,
`authorization_endpoint`, `token_endpoint`, `webmention`, `hub`/`self`, `me`,
feeds). Static assets are one stylesheet (`static/css/style.css`) and one
script (`static/js/preview.js`, the Markdown preview in the admin editor).
Everything works without JavaScript.
feeds). Static assets are one stylesheet (`static/css/style.css`); admin
pages have small inline scripts. Everything works without JavaScript.
## Public URL surface
| Path | Purpose |
|------|---------|
| `/` | Home page: recent published notes (h-feed); likes are kept off it |
| `/note/<slug>` | Note permalink (h-entry), with approved webmentions and reply context |
| `/note/<slug>` | Note permalink (h-entry), with approved responses (webmentions and backfed silo responses), a counts line with web actions, and reply context |
| `/tag/<tag>` | Notes with a tag |
| `/likes` | Likes |
| `/search`, `/api/search` | Full-text search page and JSON API |
| `/media/<path>` | Uploaded images and their variants |
| `/avatars/<name>` | Saved copies of response authors' avatars |
| `/feed` | Feed chosen by the `Accept` header (RSS by default; `Vary: Accept`) |
| `/feed.rss`, `/feed.atom`, `/feed.json` | RSS 2.0, Atom 1.0, JSON Feed 1.1 |
| `/feed.xml` | Legacy alias of `/feed.rss` |
@@ -191,8 +201,15 @@ Everything works without JavaScript.
| `/admin/webmentions`, `/admin/webmentions/<id>`, `…/action`, `…/bulk-action` | Webmention moderation |
| `/admin/tokens`, `/admin/tokens/<id>/revoke` | Issued IndieAuth tokens |
| `/admin/syndication/<id>/retry` | Retry a failed crosspost |
| `/admin/syndication/<id>/check` (POST) | Check one crosspost for responses now |
| `/admin/backfeed/backfill` (POST) | Check every crosspost for responses once (backfill) |
| `/admin/notifications/test` (POST) | Send a test notification |
| `/admin/health` | Full diagnostics (JSON): database, pool statistics, filesystem, disk |
| `/health` | Public liveness check (`{"status": "ok", "version": …}`); `?detailed=true` requires login |
| `/dev/login` | Development login; only when `DEV_MODE=true` |
`/`, `/tag/<tag>` and `/likes` show each note's response counts, linking to
its responses (v2.13.4).
## Background workers
@@ -202,9 +219,9 @@ coordinated through the data volume:
| Thread | Started when | Coordination | Work |
|--------|--------------|--------------|------|
| Webmention worker (`webmention_worker.py`) | `WEBMENTION_WORKER_ENABLED` and not testing | Non-blocking `fcntl.flock` on `webmention-worker.lock` next to the database. Only the holder works the queues; the others try again each poll interval. The OS releases the lock if the holder dies, and the new holder resets rows stuck in `sending`. | Validates received webmentions; discovers endpoints and sends queued outgoing webmentions, with retries; saves response avatars (v2.13.0); sends notifications of new responses (v2.14.0, `notifications.py`, ADR-074) |
| Webmention worker (`webmention_worker.py`) | `WEBMENTION_WORKER_ENABLED` and not testing | Non-blocking `fcntl.flock` on `webmention-worker.lock` next to the database. Only the holder works the queues; the others try again each poll interval. The OS releases the lock if the holder dies, and the new holder resets rows stuck in `sending`. | Validates received webmentions; discovers endpoints and sends queued outgoing webmentions, with retries; saves missing response avatars every 10 minutes and removes unused ones weekly (v2.13.0); sweeps new responses into notifications and sets `webmentions.notified_at` (v2.14.0, `notifications.py`, ADR-074) |
| WebSub worker (`websub_worker.py`) | `WEBSUB_ENABLED` and not testing | Same pattern with `websub-worker.lock` | Verifies subscription intents, delivers topic content (signed with `X-Hub-Signature` when the subscriber gave a secret), retries, expires leases; pings an external hub instead if `WEBSUB_HUB_URL` is set |
| Syndication worker (`syndication.py`) | At least one crosspost target configured, and not testing | No file lock. Rows in `syndications` are claimed with a 5-minute `claimed_until` lease by an atomic `UPDATE`, so any process may work a row but only one at a time; a `version` column keeps edits made during a send. Threads token refreshes are serialised with a lock file next to `threads_token.json`. | Creates, updates or deletes the remote post for each (note, target) pair; up to 8 attempts. Then backfeed: checks copies for responses (v2.13.0, `backfeed.py`, ADR-073) |
| Syndication worker (`syndication.py`) | At least one crosspost target configured, and not testing | No file lock. Rows in `syndications` are claimed with a 5-minute `claimed_until` lease by an atomic `UPDATE`, so any process may work a row but only one at a time; a `version` column keeps edits made during a send. Threads token refreshes are serialised with a lock file next to `threads_token.json`. | Creates, updates or deletes the remote post for each (note, target) pair; up to 8 attempts. Then, only when `BACKFEED_ENABLED`, backfeed: checks copies for responses, each claimed with a `backfeed_claimed_until` lease (v2.13.0, `backfeed.py`, ADR-073) |
All workers run inside an app context, are daemon threads (they end with the
process) and sleep for their poll interval when there is nothing to do. Under
@@ -225,9 +242,12 @@ Content is kept in files and everything else in SQLite, both under
- **Media**: `media/YYYY/MM/<uuid>.<ext>` plus `<uuid>_<variant>.<ext>`
variants, staged in `media/.tmp/` while being processed.
- **Database**: `starpunk.db` (WAL mode): note metadata, tags, media records,
sessions, IndieAuth codes and tokens, webmentions and the outgoing queue,
syndications, WebSub subscriptions and queues, caches (author h-card, reply
sessions, IndieAuth codes and tokens, webmentions (including backfed silo
responses, marked by `origin` and `remote_id`) and the outgoing queue,
syndications (with backfeed state and silo-only counts), WebSub subscriptions and queues, caches (author h-card, reply
contexts), the FTS5 index and `site_state`. See [database.md](database.md).
- **Avatars**: `avatars/<sha256>.webp`, saved copies of response authors'
avatars (v2.13.0); they can be re-fetched, so losing them is harmless.
- **Other files**: `logs/starpunk.log` (rotating), worker lock files,
`threads_token.json`, and `debug/` for failed uploads when
`DEBUG_SAVE_FAILED_UPLOADS=true`.
@@ -279,20 +299,28 @@ their credentials are set. The full list with defaults is in
- **Author h-card** (`author_profile`, 24 hours) and **reply contexts**
(`reply_contexts`) are cached in the database.
- The webmention worker caches endpoint discovery results in memory.
- **Response avatars** are saved once as files named by the SHA-256 of the
source URL and served from `/avatars/<name>` with
`Cache-Control: public, max-age=604800` (one week).
## Security posture
- **Outbound requests (SSRF)**: fetches of URLs that come from outside
(webmention sources and targets, endpoint discovery, reply contexts, WebSub
callbacks, remote Micropub photos, IndieAuth client pages, crosspost link
cards) are checked first: every address the host resolves to must be public
(private, loopback, link-local, CGNAT, multicast and reserved ranges are
refused). Every fetch of a user-supplied URL (webmentions, reply contexts,
WebSub, remote Micropub photos, IndieAuth client pages and, since v2.11.0,
crosspost link cards) uses the fetcher in `webmention_ssrf.py`: it follows
redirects by hand and re-checks each hop, connects to the address it
checked (no second DNS lookup) and limits response size (1 MB by default)
and total time. `DEV_MODE` relaxes the checks for local testing.
- **Outbound requests (SSRF)**: every fetch of a URL that comes from
outside (webmention sources and targets, endpoint discovery, reply
contexts, WebSub callbacks, remote Micropub photos, IndieAuth client pages,
crosspost link cards since v2.11.0, response avatars since v2.13.0) goes
through the fetcher in `webmention_ssrf.py`. Every address the host
resolves to must be public (private, loopback, link-local, CGNAT,
multicast and reserved ranges are refused); it follows redirects by hand
and re-checks each hop, connects to the address it checked (no second DNS
lookup) and limits response size (1 MB by default) and total time.
`DEV_MODE` relaxes the checks for local testing. Exceptions: avatars on
the site's own `GOTOSOCIAL_URL` host are fetched directly, as the
crossposting client does, since behind the same proxy it may resolve to an
internal address (v2.13.1); Bluesky CDN avatars are fetched from the
account's PDS with `com.atproto.sync.getBlob`, itself through the safe
fetcher. Apprise notifications go to the owner-configured `NOTIFY_URLS`,
outside the safe fetcher.
- **HTML sanitising**: rendered notes (Markdown or HTML sent by a Micropub
client) and webmention content are cleaned with nh3 allow-lists; search
highlighting escapes everything except `<mark>`.
@@ -327,4 +355,4 @@ their credentials are set. The full list with defaults is in
---
**Last Updated**: 2026-11-03 (v2.12.0)
**Last Updated**: 2026-11-10 (v2.14.0)
@@ -1,6 +1,6 @@
# Authentication and Authorization Architecture
Current as of v2.10.1. Decision record: [ADR-064](../decisions/ADR-064-oidc-admin-login-and-builtin-indieauth-server.md),
Current as of v2.14.0 (no auth changes since v2.11.0). Decision record: [ADR-064](../decisions/ADR-064-oidc-admin-login-and-builtin-indieauth-server.md),
which supersedes the "no self-hosted IndieAuth" decisions
([ADR-050](../decisions/ADR-050-remove-custom-indieauth-server.md),
[ADR-056](../decisions/ADR-056-no-selfhosted-indieauth.md)) and the external
+26 -10
View File
@@ -1,6 +1,6 @@
# Syndication (POSSE) Architecture
Current as of v2.10.1. Code: `starpunk/syndication.py`.
Current as of v2.14.0. Code: `starpunk/syndication.py`, `starpunk/backfeed.py`.
StarPunk publishes on its own site first and then copies each note to other
networks (POSSE: Publish on your Own Site, Syndicate Elsewhere). Later
@@ -16,7 +16,9 @@ Decisions: [ADR-065](../decisions/ADR-065-direct-syndication-posse.md)
(Bluesky), [ADR-068](../decisions/ADR-068-likes-and-reposts.md) (likes and
reposts), [ADR-069](../decisions/ADR-069-threads-syndication.md) (Threads),
[ADR-070](../decisions/ADR-070-crosspost-links-and-cards.md) (links and link
cards), and the [v2.9.0 Micropub review](../design/v2.9.0/2026-11-03-micropub-review.md)
cards), [ADR-073](../decisions/ADR-073-backfeed.md) (backfeed),
[ADR-074](../decisions/ADR-074-notifications.md) (notifications, including
crossposting problems), and the [v2.9.0 Micropub review](../design/v2.9.0/2026-11-03-micropub-review.md)
(bookmarks, `mp-syndicate-to` default).
## Targets
@@ -34,7 +36,10 @@ in the process.
Display names come from `GOTOSOCIAL_NAME`, `BLUESKY_NAME` and
`THREADS_NAME`. GoToSocial statuses use `GOTOSOCIAL_VISIBILITY` (default
`public`). The GoToSocial token needs `write:statuses` and `write:media`,
plus `read:search` and `write:favourites` for likes and boosts.
plus `read:search` and `write:favourites` for likes and boosts, and
`read:statuses` and `read:accounts` (or `read`) for backfeed. Backfeed on
Threads needs `threads_read_replies` and `threads_manage_insights`. The
Threads client uses the API host `graph.threads.com` (v2.13.0).
Bluesky and Threads can't edit posts through their APIs. Once a copy exists
there, edits to the note don't change it, but unpublish and delete still
@@ -59,6 +64,9 @@ is sent until the note is published.
## Data: the `syndications` table (migration 012)
Migration 020 adds the backfeed columns; see [Backfeed](#backfeed-v2130-adr-073)
and [database.md](database.md#crossposting).
One row per (note, target), unique on `(note_id, target)`:
| Column | Meaning |
@@ -83,6 +91,8 @@ delete and the worker can still remove the copy.
| Micropub photo changes | `note_changed(id)` | Same |
| `delete_note()` (soft or hard), `undelete_note()` | `note_changed(id)` | Same |
| Retry button on the edit page | `retry(id)` | That row set to `pending` now, attempts reset |
| Check now (`POST /admin/syndication/<id>/check`) | `backfeed.check_now(id)` | That copy's responses checked at the next worker pass |
| Backfill responses (`POST /admin/backfeed/backfill`) | `backfeed.start_backfill()` | Every eligible copy flagged for one check |
## Worker
@@ -130,7 +140,8 @@ again with the new content. `_fail()` does the same.
errors (codes 10, 190, 200).
- Other errors retry after `min(30 s × 2^attempts, 6 h)`. After 8 attempts
the row becomes `failed`. The error is shown on the edit page with a
Retry button.
Retry button. When a row finally fails, the owner also gets a `problems`
notification (ADR-074).
- `RemoteGone` (404, or Graph error 100/33) during an update means the copy
was deleted remotely, so a new one is created. During a delete it counts as
success.
@@ -227,7 +238,7 @@ to itself (v2.8.0).
`starpunk/backfeed.py` brings responses to the copies back to the note.
After each crosspost pass, the worker loop calls `backfeed.process_due()`,
which checks up to three synced copies of published notes (not likes or
which does nothing unless `BACKFEED_ENABLED`; otherwise it checks up to three synced copies of published notes (not likes or
reposts) that are due, each under a lease (`backfeed_claimed_until`):
- **Reading.** Each client has `responses(remote_id, remote_url)`, which
@@ -244,10 +255,14 @@ reposts) that are due, each under a lease (`backfeed_claimed_until`):
`WEBMENTION_AUTO_APPROVE` default; an existing row keeps its moderation.
A complete harvest marks that silo's rows for the note that weren't
found `invalid` ("No longer on <silo>"). Authors with `#nobridge` or
`#nobot` in their bio, or Bluesky's `!no-unauthenticated` label, are
skipped and their rows deleted. If the note's shown responses changed,
its webmentions are re-sent (spec 3.1.4). Threads counts go in
`syndications.likes_count`, `reposts_count`, `quotes_count`.
`#nobot` in their bio, or Bluesky's `!no-unauthenticated` label, are not
stored and their rows are deleted; since v2.13.3 their likes, reposts and
quotes are counted anonymously instead (`hidden_counts()`). If the note's
shown responses changed, its webmentions are re-sent (spec 3.1.4).
`syndications.likes_count`, `reposts_count` and `quotes_count` hold the
silo-only counts: all of Threads; elsewhere people who opted out. New
responses found by a backfill, or by a copy's first check on a note older
than a day, are stored as already notified (v2.14.0).
- **Schedule.** `backfeed_next_at` follows the note's age: 15 minutes (day
1), 1 hour (week 1), 1 day (to 30 days), 1 week (to
`BACKFEED_MAX_AGE_DAYS`), with up to 10% jitter; none after. Failures back
@@ -259,7 +274,8 @@ reposts) that are due, each under a lease (`backfeed_claimed_until`):
`site_state`.
- **Refused credentials.** A 401/403 (or Graph auth error) puts the target
in `backfeed.denied` until restart; the admin Webmentions page says which
scopes are needed. Crossposting is unaffected.
scopes are needed, and a `problems` notification is sent. Crossposting
is unaffected.
Avatars of all responses (received and backfed) are saved by
`starpunk/avatars.py` and served from `/avatars/<sha256>.webp`; the
+12 -10
View File
@@ -1,8 +1,8 @@
# StarPunk Technology Stack
**Version**: 2.10.1 (2026-11-03)
**Version**: 2.14.0 (2026-11-10)
**Status**: Current. The original v0.x stack write-up is kept as
[technology-stack-legacy.md](technology-stack-legacy.md) for history.
[technology-stack-legacy.md](../design/v0.x/technology-stack-legacy.md) for history.
StarPunk deliberately uses few dependencies: a WSGI web framework, SQLite
from the standard library, plain files, server-rendered templates and a
@@ -21,7 +21,7 @@ the pieces fit together.
| Content storage | Markdown files on disk |
| Background work | `threading` daemon threads; `fcntl.flock` file locks to pick one process |
| Templates | Jinja2, server-side rendered |
| Front end | One hand-written stylesheet; one small vanilla JS file for the editor's Markdown preview |
| Front end | One hand-written stylesheet; small inline scripts on admin pages; no JavaScript on public pages |
| Packaging | `uv` creates the virtual environment and installs requirements (locally and in the image) |
| Container | Multi-stage `Containerfile` (Podman/Docker), non-root user |
| Reverse proxy | Caddy in production (examples for Caddy and nginx in the repo) |
@@ -46,7 +46,7 @@ vulnerabilities (`pip-audit`); check again before each release.
| apprise | `2.2.*` | Notifications to the owner's services (`starpunk/notifications.py`, ADR-074); sends to the URLs the owner configures, outside the SSRF-safe fetcher |
| PyJWT[crypto] | `2.15.*` | Verifying OIDC ID tokens (JWKS, RS/ES signatures via `cryptography`) |
| python-dotenv | `1.2.*` | Loading `.env` |
| Pillow | `13.0.*` | Image validation, resizing and variants |
| Pillow | `13.0.*` | Image validation, resizing and variants; converting response avatars to 96 px WebP (`avatars.py`) |
| pillow-heif | `1.8.*` | HEIC/HEIF uploads (iPhone photos) |
`markupsafe` comes with Flask/Jinja2.
@@ -69,10 +69,10 @@ front-end framework or bundler, no separate search server.
| Area | Standards |
|------|-----------|
| IndieWeb | Micropub (create, update, delete, undelete, queries, media endpoint), IndieAuth (authorization server with PKCE, metadata endpoint, token revocation), Webmention (send and receive), WebSub (publisher and built-in hub), microformats2 (h-entry, h-feed, h-card markup and parsing), rel=me |
| IndieWeb | Micropub (create, update, delete, undelete, queries, media endpoint), IndieAuth (authorization server with PKCE, metadata endpoint, token revocation), Webmention (send and receive), WebSub (publisher and built-in hub), microformats2 (h-entry, h-feed, h-card markup and parsing), rel=me, web actions (`<indie-action>`), backfeed of responses from the silos |
| Login | OpenID Connect authorization code flow with PKCE (provider: Pocket ID) |
| Feeds | RSS 2.0, Atom 1.0, JSON Feed 1.1, OPML 2.0, HTTP content negotiation |
| Crossposting | Mastodon client API (GoToSocial), AT Protocol (Bluesky XRPC), Threads Graph API |
| Crossposting | Mastodon client API (GoToSocial), AT Protocol (Bluesky XRPC), Threads Graph API; the same APIs are read for backfeed |
Protocol details: [indieweb-protocols.md](indieweb-protocols.md),
[simplified-auth-architecture.md](simplified-auth-architecture.md),
@@ -80,7 +80,7 @@ Protocol details: [indieweb-protocols.md](indieweb-protocols.md),
## Testing
- **Framework**: pytest with pytest-mock; about 1,250 tests in `tests/`
- **Framework**: pytest with pytest-mock; about 1,260 tests in `tests/`
(`test_*.py` per module or feature, shared fixtures in `tests/conftest.py`,
helpers in `tests/helpers/`).
- **Isolation**: the `app` fixture calls `create_app()` with `TESTING=True`
@@ -93,10 +93,12 @@ Protocol details: [indieweb-protocols.md](indieweb-protocols.md),
- **Running locally**:
```bash
uv venv && uv pip install -r requirements-dev.txt
.venv/bin/python -m pytest
uv venv --python 3.14 && uv pip install -r requirements-dev.txt
SESSION_SECRET=test uv run pytest tests/test_<area>.py
```
Locally, run the tests for the area you changed; CI runs the full suite.
- **In CI**: the `test` stage of the `Containerfile` installs the production
requirements plus `requirements-test.txt` and runs the whole suite. The
image is only built and pushed if it passes. Checklist:
@@ -120,4 +122,4 @@ standards.
---
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
+1 -1
View File
@@ -2,7 +2,7 @@
## Status
Accepted (v2.13.0, 2026-11-10)
Accepted (v2.13.0, 2026-11-10; amended v2.13.2, v2.13.3)
Implementation notes (v2.13.0):
+4 -4
View File
@@ -85,8 +85,7 @@ See also [IndieWeb protocols](../architecture/indieweb-protocols.md).
| [066](ADR-066-bluesky-syndication.md) | Crossposting to Bluesky | Accepted | Bluesky as a second crosspost target (v2.2.0). |
| [069](ADR-069-threads-syndication.md) | Crossposting to Threads | Accepted | Threads as a third target, with automatic token refresh (v2.6.0). |
| [070](ADR-070-crosspost-links-and-cards.md) | Links and link cards in crossposts | Accepted | Keep note links in crossposts and build link cards for the linked page (v2.6.3). |
| [074](ADR-074-notifications.md) | Notifications through Apprise | Accepted | Notify the owner of new responses and crosspost/backfeed problems via the embedded Apprise library (v2.14.0). |
| [073](ADR-073-backfeed.md) | Backfeed of responses to crossposts | Accepted | Poll GoToSocial, Bluesky and Threads for responses to crossposts and store them as webmentions; admin backfill (v2.13.0). |
| [073](ADR-073-backfeed.md) | Backfeed of responses to crossposts | Accepted | Poll GoToSocial, Bluesky and Threads for responses to crossposts and store them as webmentions; admin backfill (v2.13.0, amended v2.13.2–v2.13.3). |
### Authentication (current)
@@ -106,6 +105,7 @@ See also [IndieWeb protocols](../architecture/indieweb-protocols.md).
| [054](ADR-054-structured-logging-architecture.md) | Structured Logging Architecture | Accepted | Rotating log files with correlation IDs (v1.1.1). |
| [055](ADR-055-error-handling-philosophy.md) | Error Handling Philosophy | Accepted | Layered handling: graceful degradation, clear user messages, detailed logs. |
| [072](ADR-072-remove-metrics-dashboard.md) | Remove the metrics dashboard | Accepted | Drop the in-memory metrics system and dashboard; keep `/health`, `/admin/health` and logs (v2.12.0). |
| [074](ADR-074-notifications.md) | Notifications through Apprise | Accepted | Notify the owner of new responses and crosspost/backfeed problems via the embedded Apprise library (v2.14.0). |
See also [deployment](../architecture/deployment.md).
@@ -202,5 +202,5 @@ was carried out and is not itself superseded.
---
**Last Updated**: 2026-11-03
**Total ADR files**: 67
**Last Updated**: 2026-11-10
**Total ADR files**: 70
+18 -12
View File
@@ -21,7 +21,13 @@ is in `../architecture/`; decisions are in `../decisions/` (ADRs).
## Contents
[v1.0.0](#v100) · [v1.1.1](#v111) · [v1.1.2](#v112) · [v1.2.0](#v120) · [v1.3.0](#v130) · [v1.3.1](#v131) · [v1.4.0](#v140) · [v1.4.1](#v141) · [v1.4.2](#v142) · [v1.5.0](#v150) · [v1.6.0](#v160) · [v2.0.0](#v200) · [v2.0.1](#v201) · [v2.0.2](#v202) · [v2.1.0](#v210) · [v2.2.0](#v220) · [v2.3.0](#v230) · [v2.3.1](#v231) · [v2.3.2](#v232) · [v2.3.3](#v233) · [v2.4.0](#v240) · [v2.5.0](#v250) · [v2.6.0](#v260) · [v2.6.1](#v261) · [v2.6.2](#v262) · [v2.6.3](#v263) · [v2.6.4](#v264) · [v2.6.5](#v265) · [v2.6.6](#v266) · [v2.6.7](#v267) · [v2.6.8](#v268) · [v2.6.9](#v269) · [v2.7.0](#v270) · [v2.7.1](#v271) · [v2.7.2](#v272) · [v2.8.0](#v280) · [v2.8.1](#v281) · [v2.9.0](#v290) · [v2.10.0](#v2100) · [v2.10.1](#v2101) · [v2.10.2](#v2102) · [v2.11.0](#v2110) · [v2.12.0](#v2120) · [v2.12.1](#v2121) · [v2.13.0](#v2130) · [v2.13.1](#v2131) · [v2.13.2](#v2132) · [v2.13.3](#v2133) · [v2.13.4](#v2134) · [v2.14.0](#v2140) · [hotfix](#hotfix)
[v0.x](#v0x) · [v1.0.0](#v100) · [v1.1.1](#v111) · [v1.1.2](#v112) · [v1.2.0](#v120) · [v1.3.0](#v130) · [v1.3.1](#v131) · [v1.4.0](#v140) · [v1.4.1](#v141) · [v1.4.2](#v142) · [v1.5.0](#v150) · [v1.6.0](#v160) · [v2.0.0](#v200) · [v2.0.1](#v201) · [v2.0.2](#v202) · [v2.1.0](#v210) · [v2.2.0](#v220) · [v2.3.0](#v230) · [v2.3.1](#v231) · [v2.3.2](#v232) · [v2.3.3](#v233) · [v2.4.0](#v240) · [v2.5.0](#v250) · [v2.6.0](#v260) · [v2.6.1](#v261) · [v2.6.2](#v262) · [v2.6.3](#v263) · [v2.6.4](#v264) · [v2.6.5](#v265) · [v2.6.6](#v266) · [v2.6.7](#v267) · [v2.6.8](#v268) · [v2.6.9](#v269) · [v2.7.0](#v270) · [v2.7.1](#v271) · [v2.7.2](#v272) · [v2.8.0](#v280) · [v2.8.1](#v281) · [v2.9.0](#v290) · [v2.10.0](#v2100) · [v2.10.1](#v2101) · [v2.10.2](#v2102) · [v2.11.0](#v2110) · [v2.12.0](#v2120) · [v2.12.1](#v2121) · [v2.13.0](#v2130) · [v2.13.1](#v2131) · [v2.13.2](#v2132) · [v2.13.3](#v2133) · [v2.13.4](#v2134) · [v2.14.0](#v2140) · [hotfix](#hotfix)
## v0.x
Not a release folder: documents from before v1.0.0 kept for history.
- [technology-stack-legacy.md](v0.x/technology-stack-legacy.md) — StarPunk Technology Stack - Quick Reference
## v1.0.0
@@ -408,43 +414,43 @@ OIDC admin login and built-in IndieAuth server.
## v2.10.2
- [2026-11-03-reply-context-fetch.md](v2.10.2/2026-11-03-reply-context-fetch.md) - Reply contexts fetched again (fetch_source returns three values since v2.7.0)
- [2026-11-03-reply-context-fetch.md](v2.10.2/2026-11-03-reply-context-fetch.md) — Reply context fetch
## v2.11.0
- [2026-11-03-maintenance-release.md](v2.11.0/2026-11-03-maintenance-release.md) - Dependency upgrades (Python 3.14), foreign keys, CSRF, fetchers, debug default, shared rate limits
- [2026-11-03-maintenance-release.md](v2.11.0/2026-11-03-maintenance-release.md) — Maintenance release
## v2.12.0
- [2026-11-03-remove-metrics.md](v2.12.0/2026-11-03-remove-metrics.md) - Metrics dashboard and `starpunk/monitoring` removed (ADR-072)
- [2026-11-03-remove-metrics.md](v2.12.0/2026-11-03-remove-metrics.md) — Remove the metrics dashboard
## v2.12.1
- [2026-11-10-category-unused-tags.md](v2.12.1/2026-11-10-category-unused-tags.md) - q=category lists only tags on posts that exist
- [2026-11-10-category-unused-tags.md](v2.12.1/2026-11-10-category-unused-tags.md) — q=category lists only tags in use
## v2.13.0
- [2026-11-10-backfeed.md](v2.13.0/2026-11-10-backfeed.md) - Backfeed of responses to crossposts (ADR-073), avatar cache, delete tombstones
- [2026-11-10-backfeed.md](v2.13.0/2026-11-10-backfeed.md) — Backfeed (implementation report)
## v2.13.1
- [2026-11-10-avatar-fetch.md](v2.13.1/2026-11-10-avatar-fetch.md) - Avatars from the own GoToSocial server and from Bluesky PDSes
- [2026-11-10-avatar-fetch.md](v2.13.1/2026-11-10-avatar-fetch.md) — Avatar fetching in production
## v2.13.2
- [2026-11-10-reaction-counts.md](v2.13.2/2026-11-10-reaction-counts.md) - Likes/reposts as a counts line with hover lists; web actions
- [2026-11-10-reaction-counts.md](v2.13.2/2026-11-10-reaction-counts.md) — Reaction counts and web actions
## v2.13.3
- [2026-11-10-count-opted-out.md](v2.13.3/2026-11-10-count-opted-out.md) - Opted-out people's likes and reposts counted without names
- [2026-11-10-count-opted-out.md](v2.13.3/2026-11-10-count-opted-out.md) — Count opted-out people without naming them
## v2.13.4
- [2026-11-10-list-counts.md](v2.13.4/2026-11-10-list-counts.md) - Counts on lists of notes; whole reply card links to the reply; class clash fixed
- [2026-11-10-list-counts.md](v2.13.4/2026-11-10-list-counts.md) — Counts on lists of notes, reply cards as links
## v2.14.0
- [2026-11-10-notifications.md](v2.14.0/2026-11-10-notifications.md) - Notifications through Apprise (ADR-074)
- [2026-11-10-notifications.md](v2.14.0/2026-11-10-notifications.md) — Notifications (implementation report)
## hotfix
@@ -465,4 +471,4 @@ IndieAuth PKCE endpoint discovery hotfix (2025-12-17, between v1.5.0 and v1.6.0;
---
**Last Updated**: 2026-11-03
**Last Updated**: 2026-11-10
@@ -3,7 +3,7 @@
> **Historical document.** This describes StarPunk's original v0.x technology
> choices (for example IndieLogin.com for admin login) and is kept for
> context only. It does not describe the current system; see
> [technology-stack.md](technology-stack.md) and [overview.md](overview.md).
> [technology-stack.md](../../architecture/technology-stack.md) and [overview.md](../../architecture/overview.md).
## Project Understanding
+1 -1
View File
@@ -1901,7 +1901,7 @@ class Webmention:
## References
- [ADR-004: File-Based Note Storage](../../decisions/ADR-004-file-based-note-storage.md)
- [Database Schema](../../../starpunk/monitoring/database.py)
- [Database Schema](../../../starpunk/database/schema.py)
- [Phase 1.1: Core Utilities](phase-1.1-core-utilities.md)
- [Python Coding Standards](../../standards/python-coding-standards.md)
- [Python Dataclasses Documentation](https://docs.python.org/3/library/dataclasses.html)
@@ -2061,7 +2061,7 @@ Phase 2.1 is complete when:
- [ADR-007: Slug Generation Algorithm](../../decisions/ADR-007-slug-generation-algorithm.md)
- [Phase 1.1: Core Utilities](phase-1.1-core-utilities.md)
- [Phase 1.2: Data Models](phase-1.2-data-models.md)
- [Database Schema](../../../starpunk/monitoring/database.py)
- [Database Schema](../../../starpunk/database/schema.py)
- [Python Coding Standards](../../standards/python-coding-standards.md)
- [Architecture Overview](../../architecture/overview.md)
- Security Architecture (`security.md`, not preserved)
+26 -11
View File
@@ -1,9 +1,9 @@
# StarPunk Backlog
**Last Updated**: 2026-11-03 (current release: v2.11.0)
**Last Updated**: 2026-11-10 (current release: v2.14.0)
These are the open features and bugs, sorted by priority. Each item was checked against the code
at v2.11.0. Work that has shipped is listed per release in `vX.Y.Z/RELEASE.md` and in
at v2.14.0. Work that has shipped is listed per release in `vX.Y.Z/RELEASE.md` and in
`CHANGELOG.md`.
## Priority Levels
@@ -23,11 +23,7 @@ at v2.11.0. Work that has shipped is listed per release in `vX.Y.Z/RELEASE.md` a
## High
None open.
---
## Medium
Bugs (DOCUMENTATION.md: bugs are High).
### Admin editor cannot clear all tags
- **Description**: When a note is saved with an empty tag field, the route passes `tags=None`. `update_note` treats that as "unchanged", so the last tags can't be removed from the editor.
@@ -36,9 +32,13 @@ None open.
### Media captions not escaped in RSS HTML
- **Description**: The RSS description embeds `<img alt="{caption}">` without escaping the caption. A caption containing `"` or `<` breaks the item's HTML.
- **Where**: `starpunk/feeds/rss.py` (two places, ~lines 136 and 277)
- **Where**: `starpunk/feeds/rss.py` (two places, lines 131 and 258)
- **Source**: Old backlog (Architect Review 2.2.10); still present
---
## Medium
### No rate limiting on upload endpoints
- **Description**: Media uploads (`/admin/new` and the Micropub media endpoint) have no rate limit. Both require authentication, so the risk comes from a leaked token or session.
- **Where**: `starpunk/routes/admin.py`, `starpunk/routes/micropub.py`
@@ -75,7 +75,7 @@ None open.
- **Source**: Documentation refresh 2026-11-03
### Tag-filtered feeds
- **Description**: Tag pages are h-feeds and WebSub topics, but there are no RSS, Atom or JSON feeds per tag (for example `/tag/python/feed.atom`). Tag pages also have no pagination, and the editor has no tag autocomplete.
- **Description**: Tag pages are h-feeds and WebSub topics, but there are no RSS, Atom or JSON feeds per tag (for example `/tag/python/feed.atom`). Tag pages also have no pagination, and the editor has no tag autocomplete (Micropub `q=category`, v2.12.1, already gives the list a `<datalist>` could use).
- **Where**: `starpunk/routes/public.py`, `starpunk/feeds/`, `templates/admin/`
- **Source**: Old backlog (Tag enhancements)
@@ -83,6 +83,16 @@ None open.
## Low
### Quote counts without names are not shown
- **Description**: Backfeed stores anonymous quote counts (`syndications.quotes_count`: Threads quotes, and quotes by people who opted out elsewhere), but the counts line only adds likes and reposts, so these quotes are counted nowhere on the page.
- **Where**: `templates/partials/responses.html` (`reactions`), `starpunk/webmention_queries.py` (`response_counts`)
- **Source**: Documentation review 2026-11-10
### Dead files and settings
- **Description**: `static/js/preview.js` is empty, yet the editor pages load it and `marked` from jsDelivr for nothing. `templates/feed.xml` is empty and `static/indielogin-test.html` is a v1 leftover. `syndication.get_targets()` reads a `THREADS_API` setting that `config.py` never loads, so it can't be set.
- **Where**: `templates/admin/new.html`, `templates/admin/edit.html`, `static/`, `templates/feed.xml`, `starpunk/syndication.py`
- **Source**: Documentation review 2026-11-10
### Micropub: `location` / `checkin` ignored
- **Description**: These properties are accepted but dropped, which spec 3.3.5 allows.
- **Where**: `starpunk/micropub.py`
@@ -154,7 +164,7 @@ None open.
- **Source**: Old backlog (v1.5.0 scoping)
### Unused settings and legacy tables
- **Description**: `NOTES_PATH` is read and its folder created, but notes are always written under `DATA_PATH/notes`. `SITE_AUTHOR` is required but shown nowhere. `INITIAL_SCHEMA_SQL` recreates the unused `tokens` and `authorization_codes` tables (dropped by migration 004) on every start, and `auth_state` is unused. Version fallbacks are stale (`author_discovery.py` "1.2.0", `base.html` "0.5.0").
- **Description**: `NOTES_PATH` is read and its folder created, but notes are always written under `DATA_PATH/notes`. `SITE_AUTHOR` is checked as required but defaults to "Unknown" and is shown nowhere. `INITIAL_SCHEMA_SQL` recreates the unused `tokens` and `authorization_codes` tables (dropped by migration 004) on every start, and `auth_state` is unused. Version fallbacks are stale (`author_discovery.py` "1.2.0", `base.html` "0.5.0").
- **Where**: `starpunk/config.py`, `starpunk/utils.py`, `starpunk/database/schema.py`, `starpunk/author_discovery.py`, `templates/base.html`
- **Source**: Documentation refresh 2026-11-03 (docs/architecture/database.md, deployment.md)
@@ -171,10 +181,15 @@ None open.
---
## Done since the last update (2025-12-17)
## Done (recent releases)
These items were removed from the backlog because they have shipped:
- v2.14.0: notifications of new responses and crosspost/backfeed problems through Apprise (ADR-074)
- v2.13.0–v2.13.4: backfeed of likes, reposts, quotes and replies from GoToSocial, Bluesky and Threads (ADR-073); counts line with web actions; counts on lists of notes; local avatar copies
- v2.12.1: Micropub `q=category` lists only tags in use
- v2.12.0: metrics dashboard and monitoring package removed (ADR-072)
- LICENSE: MIT, copyright Phil Skentelbery 2025-2026 (2026-11-03)
- v2.11.0: SQLite foreign keys enforced (orphans cleaned up by migration 018); CSRF tokens on admin, logout and consent forms; IndieAuth client and crosspost link-card fetches moved onto the SSRF-safe fetcher; `FLASK_DEBUG`/`FLASK_ENV` default to off/production; rate limits shared by all processes (and old windows pruned, so the webmention limiter no longer grows); dependencies upgraded (Python 3.14, no known vulnerabilities); stale `compose.yaml`, duplicate `dev_auth.py` and `test.ini` removed or fixed; `lxml`/`python-dateutil` pinned, `pytest` out of the runtime requirements
+14 -7
View File
@@ -4,19 +4,19 @@ Future work and per-release plans. See `../DOCUMENTATION.md` (PROJECTPLAN).
## Backlog
- **[BACKLOG.md](BACKLOG.md)** - Open features and bugs by priority (updated for v2.11.0)
- **[BACKLOG.md](BACKLOG.md)** - Open features and bugs by priority (updated for v2.14.0)
## Releases
- **[v1.0.0](v1.0.0/RELEASE.md)** (Released 2025-11-24)
- **[v1.1.0](v1.1.0/RELEASE.md)** (Released 2025-11-25)
- **[v1.1.1](v1.1.1/RELEASE.md)** (Released 2025-11-26)
- **[v1.1.2](v1.1.2/RELEASE.md)** (Released 2025-11-27)
- **[v1.1.1](v1.1.1/RELEASE.md)** (Released 2025-11-25)
- **[v1.1.2](v1.1.2/RELEASE.md)** (Released 2025-11-28)
- **[v1.2.0](v1.2.0/RELEASE.md)** (Released 2025-12-09)
- **[v1.3.0](v1.3.0/RELEASE.md)** (Complete)
- **[v1.3.1](v1.3.1/RELEASE.md)** - Feed Categories/Tags Support (Planning)
- **[v1.4.0](v1.4.0/RELEASE.md)** - Micropub Media Endpoint, Large Image Support, Enhanced Feed Media (Planning)
- **[v1.5.0](v1.5.0/RELEASE.md)** - Stability, Test Coverage, and Technical Debt Reduction (Approved)
- **[v1.3.0](v1.3.0/RELEASE.md)** (Released 2025-12-10)
- **[v1.3.1](v1.3.1/RELEASE.md)** - Feed Categories/Tags Support (Released 2025-12-10)
- **[v1.4.0](v1.4.0/RELEASE.md)** - Micropub Media Endpoint, Large Image Support, Enhanced Feed Media (Released 2025-12-16 as 1.4.0rc1, then 1.4.1 and 1.4.2)
- **[v1.5.0](v1.5.0/RELEASE.md)** - Stability, Test Coverage, and Technical Debt Reduction (Released 2025-12-17)
- **[v2.0.0](v2.0.0/RELEASE.md)** - OIDC admin login and built-in IndieAuth server (Released 2026-10-31)
- **[v2.0.1](v2.0.1/RELEASE.md)** - Absolute URLs behind HTTPS proxy (Released 2026-10-31)
- **[v2.0.2](v2.0.2/RELEASE.md)** - CI registry login (Released 2026-10-31)
@@ -49,3 +49,10 @@ Future work and per-release plans. See `../DOCUMENTATION.md` (PROJECTPLAN).
- **[v2.10.2](v2.10.2/RELEASE.md)** - Reply context fetch fix (Released 2026-11-03)
- **[v2.11.0](v2.11.0/RELEASE.md)** - Maintenance: dependency upgrades, High backlog items (Released 2026-11-03)
- **[v2.12.0](v2.12.0/RELEASE.md)** - Metrics dashboard removed (Released 2026-11-03)
- **[v2.12.1](v2.12.1/RELEASE.md)** - `q=category` lists only tags in use (Released 2026-11-10)
- **[v2.13.0](v2.13.0/RELEASE.md)** - Backfeed of responses to crossposts (Released 2026-11-10)
- **[v2.13.1](v2.13.1/RELEASE.md)** - Avatar fetching fixes (Released 2026-11-10)
- **[v2.13.2](v2.13.2/RELEASE.md)** - Counts line and web actions (Released 2026-11-10)
- **[v2.13.3](v2.13.3/RELEASE.md)** - Opted-out people counted without names (Released 2026-11-10)
- **[v2.13.4](v2.13.4/RELEASE.md)** - Counts on lists of notes, reply cards link out (Released 2026-11-10)
- **[v2.14.0](v2.14.0/RELEASE.md)** - Notifications through Apprise (Released 2026-11-10)
+1 -1
View File
@@ -1,6 +1,6 @@
# StarPunk v1.1.1 Release
**Status**: Released 2025-11-26
**Status**: Released 2025-11-25
## Features
+1 -1
View File
@@ -1,6 +1,6 @@
# StarPunk v1.1.2 Release
**Status**: Released 2025-11-27
**Status**: Released 2025-11-28
**Codename**: Syndicate
## Features
+1 -1
View File
@@ -1,6 +1,6 @@
# StarPunk v1.3.0 Release
**Status**: Complete
**Status**: Released 2025-12-10
**Codename**: "Categories"
**Branch**: `feature/v1.3.0-tags-microformats`
**Approved**: 2025-12-10
+1 -1
View File
@@ -1,6 +1,6 @@
# StarPunk v1.3.1 Release
**Status**: Planning
**Status**: Released 2025-12-10
**Codename**: "Syndicate Tags"
**Focus**: Feed Categories/Tags Support
+1 -1
View File
@@ -1,6 +1,6 @@
# StarPunk v1.4.0 Release
**Status**: Planning
**Status**: Released 2025-12-16 (as 1.4.0rc1; then 1.4.1 and 1.4.2)
**Codename**: "Media"
**Focus**: Micropub Media Endpoint, Large Image Support, Enhanced Feed Media
+1 -1
View File
@@ -1,6 +1,6 @@
# StarPunk v1.5.0 Release Plan
**Status**: Approved
**Status**: Released 2025-12-17
**Codename**: "Trigger"
**Focus**: Stability, Test Coverage, and Technical Debt Reduction
**Last Updated**: 2025-12-17
+1 -1
View File
@@ -1,7 +1,7 @@
# v2.10.2
- **Date**: 2026-11-03
- **Status**: Released
- **Status**: Released 2026-11-03
## Bugs fixed
+1 -1
View File
@@ -1,7 +1,7 @@
# v2.11.0
- **Date**: 2026-11-03
- **Status**: Released
- **Status**: Released 2026-11-03
- **Focus**: Maintenance: dependency upgrades and the High backlog items
## Security
+1 -1
View File
@@ -1,7 +1,7 @@
# v2.12.0
- **Date**: 2026-11-03
- **Status**: Released
- **Status**: Released 2026-11-03
- **Focus**: Remove the metrics dashboard
## Removed
+14
View File
@@ -0,0 +1,14 @@
# v2.12.1
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Micropub `q=category` lists only tags in use
## Fixed
- `q=category` returns only tags on posts that exist (not ones an edit removed, nor ones only on deleted posts)
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [Design note](../../design/v2.12.1/2026-11-10-category-unused-tags.md)
+25
View File
@@ -0,0 +1,25 @@
# v2.13.0
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Backfeed of responses to crossposts
## Added
- Likes, reposts, quotes and replies to GoToSocial and Bluesky crossposts, and replies on Threads, shown on the note
- Age-based checking schedule up to `BACKFEED_MAX_AGE_DAYS` (90); admin backfill and per-crosspost Check now
- Threads like/repost/quote counts; a Quotes group; origin filter and Deleted view in the admin
- Settings `BACKFEED_ENABLED`, `BACKFEED_MAX_AGE_DAYS`; migration 020
## Changed
- Response avatars saved locally (`/avatars/`)
- Admin delete keeps a tombstone
- `#nobridge` / `#nobot` and Bluesky's logged-out label honoured; already backfed responses not shown twice from Bridgy
- Threads client on `graph.threads.com`
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [ADR-073](../../decisions/ADR-073-backfeed.md)
- [Design note](../../design/v2.13.0/2026-11-10-backfeed.md)
+15
View File
@@ -0,0 +1,15 @@
# v2.13.1
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Avatar fetching in production
## Fixed
- Avatars from the site's own GoToSocial (resolves to an internal address) and from Bluesky (CDN refuses some server IPv4 addresses; fetched from the PDS instead)
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [ADR-073](../../decisions/ADR-073-backfeed.md)
- [Design note](../../design/v2.13.1/2026-11-10-avatar-fetch.md)
+20
View File
@@ -0,0 +1,20 @@
# v2.13.2
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Counts line for likes and reposts; web actions
## Changed
- Likes, reposts and bookmarks shown as one line of counts under the note, with who on hover; Threads counts folded in
- `<indie-action>` web actions with links to the note's crossposts
## Fixed
- Avatars GoToSocial hasn't cached (redirects to the original server)
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [ADR-073](../../decisions/ADR-073-backfeed.md)
- [Design note](../../design/v2.13.2/2026-11-10-reaction-counts.md)
+15
View File
@@ -0,0 +1,15 @@
# v2.13.3
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Opted-out people counted without names
## Changed
- Likes and reposts by people who opted out of backfeed count in the totals, without name or avatar
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [ADR-073](../../decisions/ADR-073-backfeed.md)
- [Design note](../../design/v2.13.3/2026-11-10-count-opted-out.md)
+22
View File
@@ -0,0 +1,22 @@
# v2.13.4
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Counts on lists of notes; reply cards
## Added
- Like, repost and reply counts on the home, tag and Likes pages
## Changed
- A whole reply card opens the reply where it was posted
## Fixed
- The counts line's CSS clashed with the Liked / Reposted / In reply to lines (`.reaction`)
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [Design note](../../design/v2.13.4/2026-11-10-list-counts.md)
+16
View File
@@ -0,0 +1,16 @@
# v2.14.0
- **Date**: 2026-11-10
- **Status**: Released
- **Focus**: Notifications through Apprise
## Added
- Notifications of new responses and crosspost/backfeed problems via the embedded Apprise library
- Settings `NOTIFY_URLS`, `NOTIFY_EVENTS`, `NOTIFY_PRIORITY`; admin status and Send test notification; migration 021
## Related
- [CHANGELOG](../../../CHANGELOG.md)
- [ADR-074](../../decisions/ADR-074-notifications.md)
- [Design note](../../design/v2.14.0/2026-11-10-notifications.md)
@@ -1,11 +1,11 @@
# Utility Function Patterns
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1; reviewed, content from 2025-11-18)
**Status**: Deprecated (2026-11-10). Superseded by [python-coding-standards.md](../python-coding-standards.md), which this document contradicts on type hints (`X | None`, built-in generics, hints on new and changed public functions).
**Last Updated**: 2026-11-03 (v2.10.1; content from 2025-11-18)
## Purpose
This document establishes coding patterns and conventions specifically for utility functions in StarPunk (`starpunk/utils.py`, `starpunk/slug_utils.py`, `starpunk/mf2_utils.py` and helpers in other modules). These patterns ensure utilities are consistent, testable, and maintainable. General rules, including project-wide patterns for configuration, database access and outbound HTTP, are in [python-coding-standards.md](python-coding-standards.md); where the two differ, that document wins.
This document establishes coding patterns and conventions specifically for utility functions in StarPunk (`starpunk/utils.py`, `starpunk/slug_utils.py`, `starpunk/mf2_utils.py` and helpers in other modules). These patterns ensure utilities are consistent, testable, and maintainable. General rules, including project-wide patterns for configuration, database access and outbound HTTP, are in [python-coding-standards.md](../python-coding-standards.md); where the two differ, that document wins.
The examples are illustrative. Several mirror real functions in `starpunk/utils.py` (`calculate_content_hash`, `write_note_file`, `validate_slug`, `generate_slug`, `validate_note_path`); others (`require_valid_slug`, `iter_note_files`) only show the pattern.
@@ -731,7 +731,7 @@ def generate_slug(content: str) -> str:
## References
- [Python Coding Standards](python-coding-standards.md)
- [Python Coding Standards](../python-coding-standards.md)
- [PEP 8 - Style Guide](https://peps.python.org/pep-0008/)
- [PEP 257 - Docstring Conventions](https://peps.python.org/pep-0257/)
- [PEP 484 - Type Hints](https://peps.python.org/pep-0484/)
+7 -7
View File
@@ -1,10 +1,10 @@
# Standards Index
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
Standards for developing and releasing StarPunk. Folder rules are in
[../DOCUMENTATION.md](../DOCUMENTATION.md). All standards below were checked
against the code at v2.10.1.
against the code at v2.14.0.
## Active standards
@@ -16,7 +16,6 @@ against the code at v2.10.1.
| [versioning-strategy.md](versioning-strategy.md) | Choosing MAJOR / MINOR / PATCH |
| [version-implementation-guide.md](version-implementation-guide.md) | Where the version lives, changelog entry and design note format |
| [python-coding-standards.md](python-coding-standards.md) | Style, naming, and project patterns (config, database, outbound HTTP, errors, routes, workers) |
| [utility-function-patterns.md](utility-function-patterns.md) | Patterns for small helper functions |
| [cookie-naming-convention.md](cookie-naming-convention.md) | `starpunk_` cookie prefix and the cookies in use |
| [documentation-organization.md](documentation-organization.md) | Templates and conventions for docs (folder rules: DOCUMENTATION.md) |
@@ -31,8 +30,8 @@ against the code at v2.10.1.
## Key rules in brief
- `uv` for environments, `uv run` for every command.
- Tests need `SESSION_SECRET`; the full suite takes about 6 minutes, 5 of
them in `tests/test_migration_race_condition.py`.
- Tests need `SESSION_SECRET`. Locally, run only the tests for the area you
changed; CI runs the full suite (about 6 minutes) on every `vX.Y.Z` tag.
- Every release: branch in a worktree, bump `__version__` and
`__version_info__`, changelog entry, design note (or ADR amendment),
`git merge --no-ff`, annotated `vX.Y.Z` tag; CI tests and publishes the
@@ -43,8 +42,9 @@ against the code at v2.10.1.
## Deprecated standards
Standards that no longer apply move to `DEPRECATED/` (none at
present). Earlier versions of the standards above are in git history.
Standards that no longer apply move to `DEPRECATED/`:
[utility-function-patterns.md](DEPRECATED/utility-function-patterns.md)
(superseded by python-coding-standards.md, 2026-11-10). Earlier versions of the standards above are in git history.
## Related
+1 -1
View File
@@ -2,7 +2,7 @@
**Status**: Active
**Date**: 2025-11-18
**Last Updated**: 2026-11-03 (v2.10.1; cookie list checked against the code)
**Last Updated**: 2026-11-10 (v2.14.0; cookie list checked against the code)
**Version**: 1.1
## Purpose
+9 -8
View File
@@ -1,7 +1,7 @@
# Development Setup
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
How to set up a local StarPunk environment, run the app and run the tests.
Each configuration variable is described in [`.env.example`](../../.env.example);
@@ -17,8 +17,9 @@ deployment is in [architecture/deployment.md](../architecture/deployment.md).
## Environment
The repository has no `pyproject.toml`; dependencies are in
`requirements.txt` (runtime) and `requirements-dev.txt` (adds pytest-cov,
pytest-mock, black, flake8, mypy).
`requirements.txt` (runtime) and `requirements-dev.txt` (adds
`requirements-test.txt` (pytest, pytest-mock), plus pytest-cov, black, flake8,
mypy and pip-audit).
```bash
git clone https://git.thesatelliteoflove.com/phil/StarPunk.git
@@ -100,9 +101,9 @@ docker run --rm -p 8000:8000 --env-file .env -v ./container-data:/data starpunk:
## Running the tests
```bash
SESSION_SECRET=test uv run pytest # full suite
SESSION_SECRET=test uv run pytest tests/test_websub.py # one file
SESSION_SECRET=test uv run pytest tests/test_websub.py # the area you changed
SESSION_SECRET=test uv run pytest tests/test_micropub.py -k delete -x
SESSION_SECRET=test uv run pytest # full suite (CI runs this; rarely needed locally)
```
- `SESSION_SECRET` must be set (in `.env` or the environment) because
@@ -113,9 +114,9 @@ SESSION_SECRET=test uv run pytest tests/test_micropub.py -k delete -x
`DATA_PATH` and database, so tests never touch `./data`. Under
`TESTING=True` the background workers don't start and
the production OIDC check is skipped.
- `tests/test_migration_race_condition.py` is slow (about 5 minutes). While
iterating, add `--ignore=tests/test_migration_race_condition.py`; run the
full suite before releasing.
- Locally, run the tests for the area you changed; the full suite, including
the slow `tests/test_migration_race_condition.py` (about 5 minutes), runs in
CI on the release tag.
- Coverage: `SESSION_SECRET=test uv run pytest --cov=starpunk --cov-report=term-missing`.
- The CI test stage can be reproduced exactly with
`docker build --target test -f Containerfile .` (see
+2 -2
View File
@@ -1,7 +1,7 @@
# Documentation Organization
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
**[docs/DOCUMENTATION.md](../DOCUMENTATION.md) is authoritative** for what
goes in which folder and supersedes this document. This standard only adds
@@ -94,5 +94,5 @@ top saying what replaced it, and removed from the active list in
- Architecture documents describing a design that no longer exists are
either rewritten or renamed with a `-legacy` suffix and a note at the top
(e.g. `architecture/technology-stack-legacy.md`).
(e.g. `design/v0.x/technology-stack-legacy.md`).
- Design notes and ADRs are historical records and stay where they are.
+5 -3
View File
@@ -1,7 +1,7 @@
# Git Branching and Release Process
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
How changes reach `main`, how releases are cut, and what happens after a
tag is pushed. This is the flow used for the v2 releases (see
@@ -27,6 +27,7 @@ differ, this document describes current practice.
| `feat/` | new behaviour (MINOR) | `feat/v2.10.0-websub` |
| `fix/` | bug and security fixes (PATCH) | `fix/v2.10.1-websub-hardening` |
| `ci/` | build and CI changes | `ci/v2.7.1-pytest` |
| `chore/` | maintenance, removals, licensing | `chore/remove-metrics` |
| `docs/` | documentation only, no release | `docs/refresh-v2.10.1` |
Release branches are named `<prefix>/vX.Y.Z-<short-description>`, so the
@@ -83,8 +84,9 @@ Code, tests and docs together:
- [ ] Add a design note `docs/design/vX.Y.Z/YYYY-MM-DD-<topic>.md` (what
changed and why, how it was verified). Small releases fully covered by
an ADR amendment and the changelog may skip it
- [ ] Full test suite passes:
`SESSION_SECRET=test uv run pytest`
- [ ] Tests for the changed area pass locally, e.g.
`SESSION_SECRET=test uv run pytest tests/test_notifications.py`;
CI runs the full suite on the tag (step 4)
Commit (usually one commit):
+2 -4
View File
@@ -1,12 +1,11 @@
# Python Coding Standards
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
How Python code in StarPunk is written. The project rule comes first:
"Every line of code must justify its existence. When in doubt, leave it
out." Patterns specific to small helper functions are in
[utility-function-patterns.md](utility-function-patterns.md).
out."
## Base style
@@ -147,5 +146,4 @@ functions or `Test...` classes with descriptive names
## References
- [PEP 8](https://peps.python.org/pep-0008/), [PEP 257](https://peps.python.org/pep-0257/), [PEP 484](https://peps.python.org/pep-0484/)
- [utility-function-patterns.md](utility-function-patterns.md)
- [ADR-055: Error handling philosophy](../decisions/ADR-055-error-handling-philosophy.md)
+12 -9
View File
@@ -1,7 +1,7 @@
# Testing Checklist
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
What to test, how to run the tests, and what CI does with them. Setup and
the environment variables the tests need are in
@@ -12,12 +12,14 @@ the environment variables the tests need are in
**Locally**
```bash
SESSION_SECRET=test uv run pytest # everything
SESSION_SECRET=test uv run pytest --ignore=tests/test_migration_race_condition.py # fast loop
SESSION_SECRET=test uv run pytest tests/test_websub.py tests/test_websub_hardening.py # the area you changed
SESSION_SECRET=test uv run pytest # everything (CI does this)
```
`tests/test_migration_race_condition.py` takes about 5 minutes; skip it
while iterating, never before a release.
Locally, run the tests for the area you changed. The full suite, including
the 5-minute `tests/test_migration_race_condition.py`, runs in CI. For wide
changes (migrations, `config.py`, `create_app`, `tests/conftest.py`) you can
build the CI test stage first: `docker build --target test -f Containerfile .`
**In CI** (`.gitea/workflows/build-container.yml`), on every pushed
`vX.Y.Z` tag (or a manual run):
@@ -30,16 +32,17 @@ while iterating, never before a release.
2. Only if that succeeds is the runtime image built and pushed as
`:vX.Y.Z` and `:latest`.
So a failing test blocks the release image; it does not block the merge or
the tag. Run the full suite before merging (see
[git-branching-strategy.md](git-branching-strategy.md#release-process)).
So a failing test blocks the release image, not the merge or the tag; CI is
where the full suite runs. If it fails, fix it in the next PATCH (see
[git-branching-strategy.md](git-branching-strategy.md#release-process),
step 4).
To reproduce CI locally: `docker build --target test -f Containerfile .`
(pytest-cov is not installed in that stage, so don't depend on it in
tests).
## Every change
- [ ] Full suite passes locally
- [ ] Tests for the changed area pass locally (CI runs the full suite)
- [ ] New behaviour has tests; a bug fix has a test that failed before the fix
- [ ] Tests use the `app` / `client` fixtures from `tests/conftest.py`
(temporary data directory, `TESTING=True`); nothing touches `./data`
@@ -1,7 +1,7 @@
# Version Implementation Guide
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
Where the version number lives and what to write for each release. Which
number to pick: [versioning-strategy.md](versioning-strategy.md). Git steps:
@@ -14,8 +14,8 @@ There is one source: `starpunk/__init__.py`, at the end of the file.
```python
# Package version (Semantic Versioning 2.0.0)
# See docs/standards/versioning-strategy.md for details
__version__ = "2.10.1"
__version_info__ = (2, 10, 1)
__version__ = "X.Y.Z"
__version_info__ = (X, Y, Z)
```
Update both lines. Nothing else holds the number: there is no
+2 -2
View File
@@ -1,10 +1,10 @@
# Versioning Strategy
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
StarPunk uses [Semantic Versioning 2.0.0](https://semver.org/):
`MAJOR.MINOR.PATCH`, currently **2.14.0**. Every release is a git tag
`MAJOR.MINOR.PATCH` (the current version is in `starpunk/__init__.py`). Every release is a git tag
`vX.Y.Z` and a `CHANGELOG.md` entry. Where the number is stored and how to
write the changelog entry is in
[version-implementation-guide.md](version-implementation-guide.md); the