What hosts actually said after the sitting

“They asked our hosts to keep a paper log of muted alerts for three evenings. The readout named the 9:40 p.m. blast that emptied the room, which our own weekly summary had buried under a single line. We still argue with one of their comments on sticker density, but the blast is gone.”
— Mei L., community host, Petaling Jaya

“The audit sitting in Kuching was slower than I wanted. Farid would not skip the welcome sequence even though I had already rewritten it twice. He was right about the empty hall after the third card — newcomers landed in a thread with yesterday’s festival debris — but I wish we had been told on day two instead of day nine.”
— Daniel K., caretaker of a campus companion app, Kota Samarahan

“Our Bahasa and English creator rooms looked identical in the export. The side-by-side letter showed that English-room replies clustered after 10 p.m., while the Bahasa room went kindest just after Maghrib. We stopped copying the same announcement hour into both.”
— Nur A., host lead, Kuching

A longer visit: the river-market circle

A small social app for evening hawkers along the Kuching waterfront asked for a campaign readout during a three-night tasting week. Invites went out at lunch. Replies burst at 4 p.m., then the 8 p.m. “don’t miss tonight” ping trained mutes among the same stall owners who had been generous at lunch. The morning-after thread had photographers, not hawkers.

Lina sat with two stall hosts and read the ping copy aloud. They shortened the evening note to a single stall list and moved it to 5:30 p.m. The tasting week was already over; the letter was for the next one. The reservation they recorded: our five-day window could not wait for rain-delayed nights, so one evening of the log was thin.