Nagging.
Notifications, named after the imposition. One message per broadcast, an hour before, capped at three a week across the entire estate, and nothing at all in the weeks when nothing is happening.
The name is the promise.
Calling it Nagging does two things. It admits what a notification is, which is somebody deciding your attention belongs to them for a moment. And it makes the volume impossible to defend internally, because nobody wants to be the person arguing for more nagging.
That second effect is the useful one. A feature called Updates or Alerts can quietly go from two a week to nine. A feature called Nagging cannot, because every proposal to increase it has to be said out loud in a room.
The cap is three a week across the entire estate — shop, brewery, pub, Broadcasting and Nattering combined — and it is enforced by the system rather than by good intentions.
Nobody wants to be the person in the meeting arguing for more nagging.
The caps, in full.
Frequency
- Per broadcast
- 1An hour before. Never at the moment it starts.
- Across the whole estate
- 3 a week, maximumShop, brewery, pub, Broadcasting and Nattering combined.
- In a quiet week
- 0Silence is a valid state and is not a gap to be filled.
- During a series window
- TightenedOne every three days. The cap goes down when the temptation goes up.
- Marketing pushes
- 0Nagging carries events and orders. It does not carry offers.
Control
- Granularity
- Per strandHarvest Live but not The Drop, if that is what you want.
- Turning it off
- One tapNo confirmation dialogue asking whether you are sure.
- Quiet hours
- 9pm to 7amExcept Lambing Live, which is opt-in and is the whole point of it.
- Channel
- Email or pushNot both for the same thing, ever.
Nagging is also one of the fourteen named system states documented in Lawyering. This page is the broadcast-specific half of it.
What triggers a message, and what does not.
| Event | Nagging? | When |
|---|---|---|
| A broadcast you follow starts | Yes | One hour before |
| A broadcast you follow moves date | Yes | Immediately |
| A drop you asked about goes live | Yes | One hour before |
| Your parish has a meet | Yes | The evening before |
| An order ships or arrives | Yes | Not counted against the cap |
| A new podcast episode | No | That is what the feed is for |
| A new product, generally | No | Never |
| A sale or an offer | No | Never |
| We have not seen you for a while | No | Absolutely never |
What Nagging sends, and what it will not.
Sends
- One message per broadcast, an hour before
- An immediate message if a date moves
- Per-strand control
- Quiet hours, 9pm to 7am
- One tap to stop, no dialogue
Never sends
- Marketing pushes
- Offer notifications
- Re-engagement nudges
- A notification about a notification
- Anything at all in a quiet week
One per broadcast
An hour before.
Three a week, capped
Across the whole estate.
Nothing in quiet weeks
Silence is allowed.
No marketing
Events and orders only.
The diary instead.
Everything on the calendar, in one place, with no notification required.
What people actually ask.
The two questions this page gets most, answered without a support ticket.
No. This is an unsolicited third-party demonstration build, not affiliated with or endorsed by any of the businesses it describes.
Public filings, published rankings and press reporting, each labelled on the page as a verified record, a founder claim or a third-party estimate.
