Where should this conversation live?

← Mission hub · Presentation · Resources

Fleet is our community space. Mission Control is our shared room. A node can start a thread there—but some conversations may deserve a room of their own.

What gets linked to what?

Discuss groups → spaces, subspaces or rooms; nodes → rooms or threads; and comments → Matrix events. The application service transports events and authorized send-as requests. Entity mapping and policy decide their destinations, membership and lifecycle.

When does a thread deserve its own room? Who joins, who moderates, and what should happen when a page is archived or deleted?

Your assignment: a short fleet traffic burst

When the presenter starts the 90-second window, keep only this activity tab open. Open this page once, press Start recording if you choose, read two starter threads, expand/collapse a branch twice, add one proposal, and reply once to someone else. Use normal reading and posting—not reload loops, scripts, or a load generator. Stop if you see errors or the presenter calls a halt.

After the presenter ends the window, press Stop, then Copy report. Paste the report as a reply to ‘Results: fleet traffic observation’, with desktop/mobile, local/remote, and whether you used Drupal or Matrix. Describe any delay, failed post, or duplicated message. Matrix-only participants can post a short observation without a browser report.

Participation and recording are optional. The recorder stays in your browser until you choose to paste its numeric report. Server observations contain route/timing/status data; reports should not contain tokens, cookies, HAR files, private content or personal details. The shared PHP pool also serves other sites, so its worker counts are context—not ACT-only usage.

Ready. The report contains numeric browser timings, not PHP execution time.

Closing demo: create Feedback

The presenter will create a feedback node and explore choosing a Mission Control thread, a dedicated room within Fleet, or Drupal-only discussion. The room-selection UI is currently a labelled prototype: it does not create a Matrix room or relay messages. Help decide what the real workflow should do.

Then consider reactions, polls, direct messages, and Element widgets: which belong in the Drupal experience, and which should remain in the chat client? Private messages need a different access model from these public pages.

Comments labelled ‘Starter’ or ‘Workshop’ are prepared discussion prompts, not independent audience testimony. Participant replies are real contributions.