Pulse

Pulse turns time-of-day into a single global value. A day is 1000 millidays, so noon UTC is just @500 - the same number for everyone, everywhere, no conversion.

[Pulse @dotPulses]

Count the messages in your last scheduling thread.

Now count how many existed only to work out what time it actually was.

That number is the problem.

[Pulse @dotPulses]

Nobody is switching their whole life to decimal time and Pulse does not ask.

Local time shows everywhere alongside the anchor.

New standards fail when they demand everything.

[Pulse @dotPulses]

Web clock at https://t.co/8CeCtPQCM0. No install, no signup.

Full converter, live anchor. Good on a second monitor if your day crosses regions.

[Pulse @dotPulses]

Pulse started as an essay in 2021, not a product.

Sat as writing for four years.

Building it was a matter of finally being annoyed enough. Most useful software has that shape.

#buildinpublic

[Pulse @dotPulses]

Recurring meetings are where timezone systems fail quietly.

Correct when created. One region shifts. A third of attendees join an hour out.

Nobody files it as a bug because nobody knows whose fault it is.

[Pulse @dotPulses]

Chrome and Edge extension: current anchor on the toolbar, instant conversion, booking link one click away.

You are reading an email proposing a time. You should not need another tab.

[Pulse @dotPulses]

Free forever for individuals. Ordinary sense of forever.

Connect a calendar, make meetings, share them, export them.

Pro is $6/mo for a booking page and both calendars. That is the whole model.

[Pulse @dotPulses]

Every server logs in UTC.
Every protocol assumes it.
Every distributed system reconciles against it.

Then humans add 38 offsets and two annual shifts on top and wonder why scheduling is hard.

[Pulse @dotPulses]

Pulse in @SlackHQ: /pulse for the current anchor, or post an event that renders in each person's own local time.

Scheduling that requires leaving the conversation is how meetings get scheduled wrong.

[Pulse @dotPulses]

Why not just use UTC directly?

Because 14:00 UTC looks exactly like 14:00 local, so it gets read as local.

@583 cannot be mistaken for your wall clock. Being visibly different is the feature.

[Pulse @dotPulses]

Async work has a scheduling problem nobody names.

The point is not being present at the same time. But the few moments you DO share are exactly the ones timezone drift mangles.

[Pulse @dotPulses]

Meeting duration is a timezone argument too.

"An hour" is fine.
"An hour starting at 9" is not, once two regions and a DST boundary are involved.

60 millidays is 60 millidays everywhere.

[Pulse @dotPulses]

There is an open source Pulse clock for the Windows tray.

No account, no telemetry, no upsell.

Some software should just be useful.

https://t.co/lG4XTUsHWL

#opensource

[Pulse @dotPulses]

A booking link that says "pick a time" still makes your visitor do timezone math.

Pulse publishes availability in one global value. Same numbers for everyone booking.

[Pulse @dotPulses]

Swatch had this idea in 1996 and it was right.

Two things killed it: anchoring to a meridian through their own headquarters, and marketing it like a watch.

Pulse keeps the math. Anchors to UTC. Ships as infrastructure.

[Pulse @dotPulses]

Your calendar stays yours.

Pulse writes events to your own Google or Microsoft calendar, under your account.

A layer, not a host. Stop using it and nothing needs migrating.

[Pulse @dotPulses]

Pulse is on @Discord now.

Drop /event in any channel, every member sees the same anchor in their own local time.

For open source communities spread across a dozen countries this is the whole ballgame.

#opensource

[Pulse @dotPulses]

Adding time in base 60:
3:45:20 + 2h 25m 45s = carry the seconds, carry the minutes, hope

Adding time in millidays:
@345 + 456 = @801

Most time math is hard because the units came from Babylonian astronomy.

[Pulse @dotPulses]

Daylight saving was a 1918 wartime measure.

We are still doing it.

UTC does not observe DST. Neither does @500.

#remotework

[Pulse @dotPulses]

"What time is that for me?"

Six words that follow every cross-border invite and turn scheduling into a fifteen message thread.