What a lost dog taught me about urgent posts

In mid-December, a member of Neighbourhood Organisers posted that her dog had slipped his lead in a park on the edge of town. The post did everything right: a clear photo, where and when he was last seen, a way to get in touch. And then it sank. Within two hours it had been pushed down the feed by a long thread about bin collections and a couple of event reminders.

The dog was found the next morning, mostly thanks to a neighbour who happened to scroll far enough. Happy ending, but it made me look hard at how this network treats posts that matter enormously for a few hours and then not at all.

Urgent posts are a different kind of content

• They need to reach people fast, ideally people nearby.
• They need an obvious resolved state, so others stop worrying and searching.
• They should step aside once they're no longer urgent.

A normal feed does none of that. It ranks by recency or activity, and a lost dog gets fewer comments than an argument about bins.

What we're trying

For now, group admins can pin an urgent post and unpin it after a day, and we've asked members to edit the first line to say FOUND or RESOLVED when it's over. It's manual and a little clumsy, but it works. I'm also sketching a proper urgent post type for groups, with an expiry time and an optional alert for members who opt in. Jane Okafor and the neighbourhood moderators have kindly agreed to be my test group.

Lost pets are the obvious example, but the same goes for a road closure on the morning of an event, a cancelled meetup or a heating failure at a community centre. If your community has posts like these, how do you make sure they're seen in time?