Skip to content

Say what a place actually does in 0.14.0 - #28

Merged
sepehr-safari merged 1 commit into
mainfrom
places-in-0-14-0
Aug 31, 2026
Merged

Say what a place actually does in 0.14.0#28
sepehr-safari merged 1 commit into
mainfrom
places-in-0-14-0

Conversation

@sepehr-safari

Copy link
Copy Markdown
Contributor

Follows plaza#331, released as v0.14.0.

The Places section on both pages described one feed, no colour, and a welcome behind a button. Plaza now reads the rest of the fields the format carries, so a community can carry several feeds and switch between them, and one that states a colour is drawn in it: the accent, its tile on the rail, and the handles, mentions and links throughout its feed. Anything that means a state is left alone, so a warning, a zap and an unread mark read the same in every room.

The claim that was overreaching

Both pages said a place published once means the same thing in both clients. The field names are shared and the document is read the same way, but there is no shared publishing path. Hallway's deployer ships a site with the object embedded in its index.html; Plaza reads a kind:30078 carrying that same object. Somebody has to publish the second one by hand today.

So the pages now say exactly that, and the roadmap asks for the shared path rather than implying it already exists. The rest of that paragraph is unchanged, minus "the rest of the fields the format carries", which shipped.

npm run build passes.

The Places section described one feed, no colour, and a welcome behind a
button. Plaza 0.14.0 reads the rest of the fields the format carries, so a
community can carry several feeds and switch between them, and one that states
a colour is drawn in it.

Both pages also said a place published once means the same thing in both
clients. The field names are shared and the document is read the same way, but
there is no shared publishing path: Hallway's deployer ships a site with the
object embedded in it, and Plaza reads a kind:30078 carrying that object.
Somebody has to publish the second one by hand today, so the roadmap asks for
the shared path instead of implying it already exists.
@vercel

vercel Bot commented Aug 31, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
zignostr.com Ready Ready Preview Aug 31, 2026 3:46pm

@sepehr-safari
sepehr-safari merged commit 5eb0f3e into main Aug 31, 2026
3 checks passed
@sepehr-safari
sepehr-safari deleted the places-in-0-14-0 branch August 31, 2026 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant