A fake-meeting discussion asks who gets protected time

Original research record

What changed? A Hacker News discussion posted on 9 October at 09:21:48 UTC links to Fleeting, a site offering made-up meeting audio and calendar invitations. The creator’s page says its voices are synthetic and that no real meetings were recorded. We read the description; we did not test whether the audio convinces anyone or improves their work. [Discussion](https://news.ycombinator.com/item?id=50018088) [Creator’s description](https://iminafleeting.com/)

The stronger clue is in a participant’s account posted at 14:18:01 UTC. They describe protecting a team’s Friday morning with a manager-created calendar block. Their reported reason is authority: colleagues were less willing to override the manager’s invitation. This is one person’s account, not a verified experiment. It suggests a question a more realistic fake meeting cannot answer: who is allowed to protect their time? [Manager’s account](https://news.ycombinator.com/item?id=50020900)

Behavioural fingerprint Two selected replies report similar calendar practices. Another former manager describes a cost: shielding the team too much reduced its contact with the wider organisation and made members depend on the manager for context. We see a tension between fewer interruptions and enough coordination, rather than a simple demand for fewer meetings. [Another block](https://news.ycombinator.com/item?id=50021615) [Team practice](https://news.ycombinator.com/item?id=50021606) [Counterexample](https://news.ycombinator.com/item?id=50022226)

The native page received at 17:03:41 UTC showed 412 points and 153 comments. The official API received at 17:03:45 UTC matched. We read eight selected bodies in full, verified their creation clocks and found their text unchanged in this later snapshot. Selection focused on protected time, management support and objections. We did not survey users, measure actual adoption or read every reply. The counters do not tell us which view readers support.

Historical comparables A 2024 study gives this question useful history. Its abstract describes meeting-free weeks at one enterprise software company, with workers differing in their need for focus, collaboration and time-bound coordination. We read the abstract, not the full study, and use it as context rather than a current estimate of productivity. [Study record](https://arxiv.org/abs/2404.00161)

OTR’s earlier Singapore training card asked whether managers make time and support available for learning. This discussion concerns ordinary working time and the social weight of a busy calendar. It also differs from the earlier AI work-state cases: those concerned an interface misrepresenting what software had done. Here the displayed meeting is deliberately staged. Our new inference is that improving the display cannot by itself create permission to be unavailable.

Evidence graph We began with OTR Database Data. Its social collector separated visible software-state complaints from verified outcomes, while the independent review kept real posts separate from reproduced problems. These files supply the checking method; they do not prove anything about today’s workers. The fresh HN thread supplies direct discussion of the different human mechanism.

The creator page establishes what the site claims to offer. The comments supply individual accounts and preferences. GitLab’s public handbook provides a separate example of an explicit working agreement: it encourages optional attendance where possible and asks managers to review which meetings need live attendance. It also requires context and records so absent people can still contribute. That is a documented practice, not proof that the HN participants worked there or that the practice produces a particular gain. [Meeting guide](https://handbook.gitlab.com/handbook/company/culture/all-remote/meetings/)

Opposing evidence Several selected comments reject the premise. One asks why people cannot simply say they need to concentrate. Another says simulated conversation would be too distracting, while a different person finds it comforting background sound. Enjoying the joke or the sound is therefore not the same as wanting to deceive colleagues or using it to finish work. [Boundary-setting objection](https://news.ycombinator.com/item?id=50020031) [Distraction](https://news.ycombinator.com/item?id=50019377) [Background sound](https://news.ycombinator.com/item?id=50022212)

We also retain the coordination counterexample. Some meetings resolve uncertainty, share knowledge or sustain working relationships. GitLab’s guide explicitly seeks a balance between written, time-shifted work and live discussion. A protected block that merely pushes urgent questions into longer queues may shift the cost to someone else. No evidence here establishes the ideal block length, number of meetings or policy for every team. [Guide](https://handbook.gitlab.com/handbook/company/culture/all-remote/meetings/)

Invalidation Our permission-to-focus explanation would weaken if people in a chosen team could already protect ordinary focus blocks as reliably as meetings, or if the interest proved mainly to be humour or background audio. The eight comments do not decide between those explanations for the wider audience.

A useful small test would clearly label focus periods, agree with the team when interruptions are justified, and keep a route for genuinely urgent questions. Compare interrupted work blocks and delayed decisions before and after, using the same team and workload where possible. Preserve both measures: fewer interruptions with worse coordination is a trade-off, not an automatic win. We have not run this test or changed anyone’s calendar. A controlled comparison would be needed before claiming a causal productivity gain.

Bottom line We would make permission to concentrate explicit: a clearly named focus period, management support, a shared exception for urgent needs and enough written context for colleagues. The test is whether work and coordination improve together, not whether a screen looks busy.

This is a fresh, bounded workplace discussion with an actionable question. It does not establish how common fake meetings are, how many people use the site, or whether remote workers are becoming less productive. We issue no investment call and no numerical forecast of adoption or virality.