The previous long-press behavior on native was functional but not great. You'd get a reaction picker. That was about it.

This week, we rebuilt the whole thing. Long-pressing a message now lifts it off the chat — the message physically rises from the feed and hovers in the center of the screen, with a reactions picker appearing above it and an actions menu appearing below. Reply, Copy, Edit, Delete. The layout is smart enough to measure the available space and shift the lifted message up or down so everything fits on screen without clipping. All of it animates together as a group using spring physics.

The reason this matters is that reactions and message actions had no natural home before this. Reactions were buried behind a long-press with no obvious affordance for anything else. Adding actions to the same surface would have made it cluttered and confusing. Lifting the message out of the feed gives you a dedicated context — it's visually clear that you're operating on this message, and there's enough room to show you everything you can do with it.

It's the kind of interaction where, once you try it, the old behavior feels broken.

We've renamed Streams to Channels. This one is a bit of a ship of Theseus situation — we're partway through the migration — but the visible UI text has all flipped. If you see "Channel" anywhere in Slashwork now, you're looking at what used to be called a Stream. We did this because we found that everyone understands the concept of a Channel, but no one has an immediate understanding of a "Stream". Channels have been around since the 1940s, going all the way back to CB radio communications.

Internally, we added CHANNEL as a valid group display type in the schema, but we're doing a staged migration: for now the server writes CHANNEL back to disk as STREAM, which means older client versions continue to work normally. Stage 2 (the actual data migration) can proceed once we know all clients have picked up the new enum value.

The reason we're doing it this way — staging the rename carefully rather than just flipping a switch — is that we've learned the hard way that bold database migrations and client deploys rarely land at the same time. Better to be boring and correct than exciting and broken.

Small one, but a good one: the browser favicon now switches to a notification variant when new messages arrive while you're in another tab. You get a visual dot on the tab without having to look at the tab title.

The implementation is a separate favicon asset that the app swaps in when unread notifications arrive and you're not focused on the window. It swaps back when you return. It's the kind of thing you don't notice until it's there, and then you can't imagine not having it.

The admin panel now has a dedicated section for managing Applications — the first-party name for bot users and integrations. You can view, create, and delete applications from the admin UI. Previously, managing these required API access.

We also made some quality-of-life improvements to the admin Users table: the username is now a clickable link to their profile, there's an explicit "Edit name" button rather than hunting for where to do that, and the table header stays fixed when you scroll through a long user list.