Skip to content
#0948
PipeNotificationsDisplay

The handoff pings your desk when the other side picks up

You're sending a 40GB dataset to a collaborator through a pipe URL. You pasted the link. Now you're watching a terminal.

You don't have to. The sender's response body is a status stream: [INFO] Waiting for 1 receiver(s) to connect..., then [INFO] A receiver connected., then [INFO] Transfer complete., or an [ERROR] line if the five-minute hold expires with nobody on the other end. A three-line loop POSTs each line to /api/v1/notifications/notify on display "1", the [ERROR] ones with urgency: critical.

Display 1 is the desktop you're working on, in the same container. The toasts land there. You go back to the notebook. The desk tells you when she picked up, and when the last byte left.

The transfer was already a stream. You just gave it a voice.