maarcadetweet

61 Commits 1 Branch 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
tomdeboneandClaude Opus 5	c4ca218d97	feat(appview): Notifications, Follower-/Following-Listen, Thread-Route Bisher erfuhr ein Nutzer nie, dass jemand anderes mit ihm interagiert hat: Like, Repost, Follow und Reply hinterließen keine Spur, an der der Client hätte pollen können. Der Tray-/Notification-Pfad im Desktop-Client (Phase 7) hing damit in der Luft. Migration 0008: * notifications(recipient, author, kind, subject_uri, created_at, indexed_at, read_at) mit Keyset-Index (recipient, indexed_at DESC, id DESC) und Partial-Index auf ungelesene Zeilen für den Badge-Poll. * Dedupe-Unique-Index über COALESCE(subject_uri, '') — plain NULLs kollidieren nicht, sonst gäbe es pro Follow beliebig viele Zeilen. Folge: Unlike-Relike erzeugt keine zweite Notification, Toggle-Spam ist damit ausgeschlossen. * Bewusst kein CHECK (recipient <> author): ein Ausrutscher dort würde die umgebende Like-Transaktion abbrechen, also das Like wegen eines Notification-Bugs verlieren. Gefiltert wird in Rust und im INSERT. Indexer: record_notification() hängt an upsert_like/-repost (in derselben Transaktion wie die Counter) sowie upsert_follow/-post. Selbst-Interaktionen sind still. Empfänger muss uns bekannt sein (profiles- oder posts-Zeile), sonst würden wir für den gesamten öffentlichen Firehose Zeilen anlegen — als ein INSERT ... SELECT ... WHERE EXISTS, also ohne TOCTOU-Fenster. Reply-Notifications tragen die URI der Antwort als subject_uri, weil die Liste den Text zeigt, den der Empfänger noch nicht kennt. Endpoints: GET /api/notifications, /api/notifications/count, POST /api/notifications/seen (seenAt als Wasserzeichen), GET /api/followers, /api/following, GET /api/thread (beide Schreibweisen). Cursor-Codec, Limit-Clamping und Fehlerform sind die der bestehenden Endpoints. /api/post/*uri bleibt wire-kompatibel und teilt sich jetzt load_thread_context() mit /api/thread — mit max_parents = 1, weil es nur den direkten Parent serialisiert; die volle Ahnenkette wären bis zu 20 sequenzielle Queries für Zeilen, die danach verworfen werden. Nebenbei ein Darstellungsfehler: der synthetische Platzhalter-Handle für Actors ohne bekannten Handle trug ein führendes '@', während jeder Consumer selbst '@{handle}' rendert — im Feed kam '@@did:plc:abcd…' heraus. Der Platzhalter ist jetzt durchgängig sigil-frei. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013HC9HLrUU1LNwkzp8nkDLX	2026-09-09 21:36:32 +02:00
tomdebone	59a3cb02dd	feat(appview): profile cache + Jetstream indexing + denormalised counts Adds the AppView-side half of the profile feature so non-local-PDS authors also get their profile metadata indexed (the Jetstream identity event stream only carries the handle, not display name / bio / avatar). The PDS-push path was already wired by the previous commit; this lands the Jetstream path. Migration 0005: * `profiles` table keyed by DID with display_name / description / avatar_cid / banner_cid plus denormalised post_count / follower_count / following_count. Backfilled from the posts table on apply. * `posts.avatar_cid` column — populated from the profiles cache at `upsert_post` time so the PostCard can render an avatar inline without a per-row PDS round trip. Migration 0007 (clean-up): the original 0005 also created a `LOWER(handle)` index that no query uses; this drops it idempotently so dev DBs that already applied 0005 converge. Indexer (`crates/appview/src/indexer.rs`): * New `app.bsky.actor.profile` arm in `apply_commit` calls `upsert_profile` on create, DELETEs the row on delete. Handle is looked up from `posts` (the Jetstream commit envelope doesn't carry it). * `upsert_post` signature is now `&mut PostRow` so it can fill `row.avatar_cid` from the profiles cache; the ON CONFLICT clause uses `COALESCE(EXCLUDED, posts)` so re-indexing doesn't overwrite an already-known avatar. * `upsert_profile` writes display_name / description / avatar_cid / banner_cid + the denormalised counts. * `blob_link_of` helper accepts both `{ $type, ref.$link }` and legacy flat `{ $link }` blob-ref shapes. Ingest (`crates/appview/src/ingest.rs`): * `app.bsky.actor.profile` create/delete arms in the PDS-push path. The handle-fallback previously did `SELECT handle FROM users WHERE did = $1` — but the AppView has no `users` table (it's PDS-owned state). Replaced with a simple use-what-the-PDS- sent approach; the handle_sync worker fills the column later. Routes (`crates/appview/src/routes.rs`): * `resolve_profile` reads the denormalised profile fields from the cache. When no profile row exists the `post_count` fallback uses a live `SELECT COUNT()` instead of `posts.len()`, so prolific authors without a profile row report the real count rather than the 50-post slice cap. Tests (DB-gated, run when DATABASE_URL_APPVIEW is set): `blob_link_of_modern_shape` / `_legacy_flat_link` / `_missing_field`. * `upsert_profile_round_trip` — insert + replace semantics. * `apply_commit_indexes_profile_create` — end-to-end Jetstream arm + delete.	2026-07-18 17:56:52 +02:00
tomdebone	c586fd39c9	maarcadetweet: initial commit AT Protocol PDS + AppView + Tauri Desktop Client, 160-char post limit. - PDS (Rust + axum + sqlx) - Auth: createAccount, createSession, refreshSession - Records: createRecord, deleteRecord (race-safe via SELECT FOR UPDATE) - Feed: feed.like.create, feed.repost.create - Sync: getRepo, getBlocks, getLatestCommit, getRecord (with MST proof), listRepos - Identity: resolveHandle - MST: spec-conformant (at-mst crate, 27 tests) - Repo: signed commits, TID counter (monotonic, 4096 wrap safe) - AppView (Rust + axum + sqlx) - Jetstream consumer (WebSocket, exponential backoff, 38k+ events indexed) - REST API: timeline/home (graph-aware), profile, search, post (with thread hydration) - Handle-sync worker (did:plc + did:web) - JSONB embed storage + thread columns (migration 0003) - Like/repost counter cache (migration 0004) - Tauri 2 + Svelte 5 Desktop Client - System tray (Show/Compose/Quit menu) - OS notifications (tauri-plugin-notification) - Auto-update (tauri-plugin-updater, placeholder endpoint) - Window-state (tauri-plugin-window-state) - 160-char compose with live counter - Image/Link embed rendering - LocalStorage-persisted like state - Timeline with poll (prepend new posts) - Custom TitleBar (transparent, no decorations) - Orange/IBM Plex Mono maarcade design Tests: 231 Rust + 9 vitest = 240 passed.	2026-07-05 20:01:31 +02:00

Author

SHA1

Message

Date

tomdeboneandClaude Opus 5

c4ca218d97

feat(appview): Notifications, Follower-/Following-Listen, Thread-Route

Bisher erfuhr ein Nutzer nie, dass jemand anderes mit ihm interagiert hat:
Like, Repost, Follow und Reply hinterließen keine Spur, an der der Client
hätte pollen können. Der Tray-/Notification-Pfad im Desktop-Client (Phase 7)
hing damit in der Luft.

Migration 0008:
* notifications(recipient, author, kind, subject_uri, created_at,
  indexed_at, read_at) mit Keyset-Index (recipient, indexed_at DESC, id DESC)
  und Partial-Index auf ungelesene Zeilen für den Badge-Poll.
* Dedupe-Unique-Index über COALESCE(subject_uri, '') — plain NULLs
  kollidieren nicht, sonst gäbe es pro Follow beliebig viele Zeilen.
  Folge: Unlike-Relike erzeugt keine zweite Notification, Toggle-Spam ist
  damit ausgeschlossen.
* Bewusst kein CHECK (recipient <> author): ein Ausrutscher dort würde die
  umgebende Like-Transaktion abbrechen, also das Like wegen eines
  Notification-Bugs verlieren. Gefiltert wird in Rust und im INSERT.

Indexer: record_notification() hängt an upsert_like/-repost (in derselben
Transaktion wie die Counter) sowie upsert_follow/-post. Selbst-Interaktionen
sind still. Empfänger muss uns bekannt sein (profiles- oder posts-Zeile),
sonst würden wir für den gesamten öffentlichen Firehose Zeilen anlegen —
als ein INSERT ... SELECT ... WHERE EXISTS, also ohne TOCTOU-Fenster.
Reply-Notifications tragen die URI der *Antwort* als subject_uri, weil die
Liste den Text zeigt, den der Empfänger noch nicht kennt.

Endpoints: GET /api/notifications, /api/notifications/count,
POST /api/notifications/seen (seenAt als Wasserzeichen),
GET /api/followers, /api/following, GET /api/thread (beide Schreibweisen).
Cursor-Codec, Limit-Clamping und Fehlerform sind die der bestehenden
Endpoints.

/api/post/*uri bleibt wire-kompatibel und teilt sich jetzt
load_thread_context() mit /api/thread — mit max_parents = 1, weil es nur
den direkten Parent serialisiert; die volle Ahnenkette wären bis zu 20
sequenzielle Queries für Zeilen, die danach verworfen werden.

Nebenbei ein Darstellungsfehler: der synthetische Platzhalter-Handle für
Actors ohne bekannten Handle trug ein führendes '@', während jeder Consumer
selbst '@{handle}' rendert — im Feed kam '@@did:plc:abcd…' heraus. Der
Platzhalter ist jetzt durchgängig sigil-frei.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013HC9HLrUU1LNwkzp8nkDLX

2026-09-09 21:36:32 +02:00

tomdebone

59a3cb02dd

feat(appview): profile cache + Jetstream indexing + denormalised counts

Adds the AppView-side half of the profile feature so non-local-PDS
authors also get their profile metadata indexed (the Jetstream
identity event stream only carries the handle, not display name /
bio / avatar). The PDS-push path was already wired by the previous
commit; this lands the Jetstream path.

Migration 0005:

* `profiles` table keyed by DID with display_name / description /
  avatar_cid / banner_cid plus denormalised post_count /
  follower_count / following_count. Backfilled from the posts
  table on apply.
* `posts.avatar_cid` column — populated from the profiles cache
  at `upsert_post` time so the PostCard can render an avatar
  inline without a per-row PDS round trip.

Migration 0007 (clean-up): the original 0005 also created a
`LOWER(handle)` index that no query uses; this drops it
idempotently so dev DBs that already applied 0005 converge.

Indexer (`crates/appview/src/indexer.rs`):

* New `app.bsky.actor.profile` arm in `apply_commit` calls
  `upsert_profile` on create, DELETEs the row on delete. Handle
  is looked up from `posts` (the Jetstream commit envelope
  doesn't carry it).
* `upsert_post` signature is now `&mut PostRow` so it can fill
  `row.avatar_cid` from the profiles cache; the ON CONFLICT
  clause uses `COALESCE(EXCLUDED, posts)` so re-indexing doesn't
  overwrite an already-known avatar.
* `upsert_profile` writes display_name / description /
  avatar_cid / banner_cid + the denormalised counts.
* `blob_link_of` helper accepts both `{ $type, ref.$link }`
  and legacy flat `{ $link }` blob-ref shapes.

Ingest (`crates/appview/src/ingest.rs`):

* `app.bsky.actor.profile` create/delete arms in the PDS-push
  path. The handle-fallback previously did `SELECT handle FROM
  users WHERE did = $1` — but the AppView has no `users` table
  (it's PDS-owned state). Replaced with a simple use-what-the-PDS-
  sent approach; the handle_sync worker fills the column later.

Routes (`crates/appview/src/routes.rs`):

* `resolve_profile` reads the denormalised profile fields from
  the cache. When no profile row exists the `post_count` fallback
  uses a live `SELECT COUNT(*)` instead of `posts.len()`, so
  prolific authors without a profile row report the real count
  rather than the 50-post slice cap.

Tests (DB-gated, run when DATABASE_URL_APPVIEW is set):

* `blob_link_of_modern_shape` / `_legacy_flat_link` /
  `_missing_field`.
* `upsert_profile_round_trip` — insert + replace semantics.
* `apply_commit_indexes_profile_create` — end-to-end Jetstream
  arm + delete.

2026-07-18 17:56:52 +02:00

tomdebone

c586fd39c9

maarcadetweet: initial commit

AT Protocol PDS + AppView + Tauri Desktop Client, 160-char post limit.

- PDS (Rust + axum + sqlx)
  - Auth: createAccount, createSession, refreshSession
  - Records: createRecord, deleteRecord (race-safe via SELECT FOR UPDATE)
  - Feed: feed.like.create, feed.repost.create
  - Sync: getRepo, getBlocks, getLatestCommit, getRecord (with MST proof), listRepos
  - Identity: resolveHandle
  - MST: spec-conformant (at-mst crate, 27 tests)
  - Repo: signed commits, TID counter (monotonic, 4096 wrap safe)

- AppView (Rust + axum + sqlx)
  - Jetstream consumer (WebSocket, exponential backoff, 38k+ events indexed)
  - REST API: timeline/home (graph-aware), profile, search, post (with thread hydration)
  - Handle-sync worker (did:plc + did:web)
  - JSONB embed storage + thread columns (migration 0003)
  - Like/repost counter cache (migration 0004)

- Tauri 2 + Svelte 5 Desktop Client
  - System tray (Show/Compose/Quit menu)
  - OS notifications (tauri-plugin-notification)
  - Auto-update (tauri-plugin-updater, placeholder endpoint)
  - Window-state (tauri-plugin-window-state)
  - 160-char compose with live counter
  - Image/Link embed rendering
  - LocalStorage-persisted like state
  - Timeline with poll (prepend new posts)
  - Custom TitleBar (transparent, no decorations)
  - Orange/IBM Plex Mono maarcade design

Tests: 231 Rust + 9 vitest = 240 passed.

2026-07-05 20:01:31 +02:00