June 8, 2026
This Week in Slashwork
A week of closing the loop on things we shipped last week. Pinned messages got expiry, scheduled posts came to native, and comments got a bunch of buffs.

⏰ Pin expiry
Pinned messages now support an optional expiry time, on both web and native. Pin something for the duration of an outage, or until the end of the week, and it'll quietly unpin itself when the time comes. We enforce expiry server-side so nothing slips through.
📅 Scheduled posts on native
Scheduled posts now work on the native apps too: you can schedule, edit the schedule, reschedule, or just send-now from your phone. We also brought editing and pinning posts to native at the same time — between this and last week's pinned messages, there's now feature parity across web and native for pretty much everything you'd want to do with a post.
💬 Comments improvements
Comments and comment replies now support editing, deleting, and replying. They've been read-only since launch, which has been a daily papercut. Image rendering inside comments is also much improved.
🧬 Chat UI buffs
When the same person sends several messages in a row, they now render as a single cohesive block instead of repeating the profile picture and timestamp each time. It's a small visual change that makes long chat conversations dramatically easier to read.
✨ Honorable mentions
- Cmd/Ctrl+Enter now saves an edited post or chat message everywhere, not just in the original places we shipped it.
- Replying on native auto-focuses the composer instead of making you tap it.
- The post timestamp on published-but-was-scheduled posts now shows the correct time (the time it was published, not the time you clicked schedule).