Spike: web UI shape — single-channel app vs multi-channel vs threads-as-pages #7
Labels
No labels
area/api
area/bridge
area/db
area/docs
area/ops
area/web
kind/bug
kind/chore
kind/feature
kind/spike
prio/p0
prio/p1
prio/p2
prio/p3
status/blocked
status/decision
status/needs-info
type/question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: sscoble/posts#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
API is the priority for v0. But the moment we have a Discord bridge and a Hermes adapter, we need a place to read the posts. That's the web UI. The shape matters because it sets the user's mental model for years.
Three options
Theo's framing leans toward #2 — "post gets bumped when there's a new comment." That implies feed-shaped, not channel-shaped.
What to do
Open questions for Scott