this repo has no description
bnewbold.net
1
2conceptual questions:
3- ability to log-in to instance separate from a scene? eg, to manage scene
4- single client metadata or multiple?
5
6
7basic setup/infra:
8- lexicon schemas
9- gorm database models
10- echo web server
11- indexing: tap consumer, validate, filtering, tables
12- hydration: skeleton-style, labels, takedowns, viewer context
13- web app: pongo2, htmx, tailwind (?)
14- oauth client and sessions
15- label indexing: package/struct?
16- dev-env with fake accounts and data
17
18major components:
19- store.Store
20 => database, cache
21 => manages invariants
22 => high-level fetches and types
23- store/models: SQL schemas
24- indexer.Indexer
25 => consume from tap
26 => validate schemas
27
28
29views:
30- top bar: scrumble drop-menu; search; account/notifs drop-menu
31- feed of items: user, time, interactions, tags
32- scene summary bar: description, numbers, content guidelines, rules
33
34
35instance admin:
36- add PDS invite codes
37
38
39scene service account mgmt:
40- create new scenes as accounts on configured PDS (using invite codes?)
41- admin endpoint to create a scene; or add/import
42- instance invite codes allow anybody to create a scene
43- scene admins can take actions, and instance will update scene account (records)
44- lifecycle: create, migrate/import, deactivate
45
46
47
48scene config:
49- tags: any/limited/none; who
50- emoji reactions: any/limited/none; who
51- comments: threaded/flat/none; who
52- items: types; per-type filters and limits; filter code
53- membership: open/approve/invite/admin
54- basic colors
55
56
57tool shopping:
58- CDN solution
59
60docker-compose:
61- local PDS (?)
62- local PLC (?)
63- postgresql (?)