this repo has no description
lewis.moe
1# Lewis' Big Boy TODO list
2
3## Active development
4
5### OAuth scope authorization UI
6Display and manage OAuth scopes during authorization flows.
7
8- [ ] Parse and display requested scopes from authorization request
9- [ ] Human-readable scope descriptions (e.g., "Read your posts" not "app.bsky.feed.read")
10- [ ] Group scopes by category (read, write, admin, etc.)
11- [ ] Allow users to uncheck optional scopes before authorizing
12- [ ] Distinguish required vs optional scopes in UI
13- [ ] Remember scope preferences per client (don't ask again for same scopes)
14- [ ] Token endpoint respects user's scope selections
15- [ ] Protected endpoints check token scopes before allowing operations
16
17### Frontend
18So like... make the thing unique, make it cool.
19
20- [ ] Frontpage that explains what this thing is
21- [ ] Unique "brand" style both unauthed and authed
22- [ ] Better documentation on how to sub out the entire frontend for whatever the users want
23
24### Delegated accounts
25Accounts controlled by other accounts rather than having their own password. When logging in as a delegated account, OAuth asks you to authenticate with a linked controller account. Uses OAuth scopes as the permission model.
26
27- [ ] Account type flag in actors table (personal | delegated)
28- [ ] account_delegations table (delegated_did, controller_did, granted_scopes[], granted_at, granted_by, revoked_at)
29- [ ] Detect delegated account during authorize flow
30- [ ] Redirect to "authenticate as controller" instead of password prompt
31- [ ] Validate controller has delegation grant for this account
32- [ ] Issue token with intersection of (requested scopes :intersection-emoji: granted scopes)
33- [ ] Token includes act_as claim indicating delegation
34- [ ] Define standard scope sets (owner, admin, editor, viewer)
35- [ ] Create delegated account flow (no password, must add initial controller)
36- [ ] Controller management page (add/remove controllers, modify scopes)
37- [ ] "Act as" account switcher for users with delegation grants
38- [ ] Log all actions with both actor DID and controller DID
39- [ ] Audit log view for delegated account owners
40
41### Passkeys and 2FA
42Modern passwordless authentication using WebAuthn/FIDO2, plus TOTP for defense in depth.
43
44- [ ] passkeys table (id, did, credential_id, public_key, sign_count, created_at, last_used, friendly_name)
45- [ ] user_totp table (did, secret_encrypted, verified, created_at, last_used)
46- [ ] WebAuthn registration challenge generation and attestation verification
47- [ ] TOTP secret generation with QR code setup flow
48- [ ] Backup codes (hashed, one-time use) with recovery flow
49- [ ] OAuth authorize flow: password → 2FA (if enabled) → passkey (as alternative)
50- [ ] Passkey-only account creation (no password)
51- [ ] Settings UI for managing passkeys, TOTP, backup codes
52- [ ] Trusted devices option (remember this browser)
53- [ ] Rate limit 2FA attempts
54- [ ] Re-auth for sensitive actions (email change, adding new auth methods)
55
56### Plugin system
57Extensible architecture allowing third-party plugins to add functionality, like minecraft mods or browser extensions.
58
59- [ ] Research: survey Fabric/Forge, VS Code, Grafana, Caddy plugin architectures
60- [ ] Evaluate rust approaches: WASM, dynamic linking, subprocess IPC, embedded scripting (Lua/Rhai)
61- [ ] Define security model (sandboxing, permissions, resource limits)
62- [ ] Plugin manifest format (name, version, deps, permissions, hooks)
63- [ ] Plugin discovery, loading, lifecycle (enable/disable/hot reload)
64- [ ] Error isolation (bad plugin shouldn't crash PDS)
65- [ ] Extension points: request middleware, record lifecycle hooks, custom XRPC endpoints
66- [ ] Extension points: custom lexicons, storage backends, auth providers, notification channels
67- [ ] Extension points: firehose consumers (react to repo events)
68- [ ] Plugin SDK crate with traits and helpers
69- [ ] Example plugins: custom feed algorithm, content filter, S3 backup
70- [ ] Plugin registry with signature verification and version compatibility
71
72### Plugin: Private/encrypted data
73Records that only authorized parties can see and decrypt. Requires key federation between PDSes. Implemented as a plugin using the plugin system above.
74
75- [ ] Survey current ATProto discourse on private data
76- [ ] Document Bluesky team's likely approach
77- [ ] Design key management strategy
78- [ ] Per-user encryption keys (separate from signing keys)
79- [ ] Key derivation for per-record or per-collection encryption
80- [ ] Encrypted record storage format
81- [ ] Transparent encryption/decryption in repo operations
82- [ ] Protocol for sharing decryption keys between PDSes
83- [ ] Handle key rotation and revocation
84
85---
86
87## Completed
88
89Core ATProto: Health, describeServer, all session endpoints, full repo CRUD, applyWrites, blob upload, importRepo, firehose with cursor replay, CAR export, blob sync, crawler notifications, handle resolution, PLC operations, did:web, full admin API, moderation reports.
90
91OAuth 2.1: Authorization server metadata, JWKS, PAR, authorize endpoint with login UI, token endpoint (auth code + refresh), revocation, introspection, DPoP, PKCE S256, client metadata validation, private_key_jwt verification.
92
93App endpoints: getPreferences, putPreferences, getProfile, getProfiles, getTimeline, getAuthorFeed, getActorLikes, getPostThread, getFeed, registerPush (all with local-first + proxy fallback).
94
95Infrastructure: Sequencer with cursor replay, postgres repo storage with atomic transactions, valkey DID cache, debounced crawler notifications with circuit breakers, multi-channel notifications (email/Discord/Telegram/Signal), image processing, distributed rate limiting, security hardening.
96
97Web UI: OAuth login, registration, email verification, password reset, multi-account selector, dashboard, sessions, app passwords, invites, notification preferences, repo browser, CAR export, admin panel.
98
99Auth: ES256K + HS256 dual support, JTI-only token storage, refresh token family tracking, encrypted signing keys (AES-256-GCM), DPoP replay protection, constant-time comparisons.