Open Source Projects

Timeslot.ink: Lightweight Subtractive Scheduling Tool

Remember when scheduling polls didn't require an account? Timeslot.ink brings that back—with a clever subtractive twist and zero chance of corporate bloat.

Timeslot.ink: The FOSS Scheduling Tool That Says No to Logins and Enshittification — Open Source Beat

Key Takeaways

  • Timeslot.ink revives login-free polling with a smart subtractive model for quick group scheduling.
  • Built on Cloudflare D1 and vanilla JS, it's anti-enshittification by design—FOSS and edge-hosted.
  • Perfect for async teams; lacks bells but nails the basics without SaaS bloat.

My inbox exploded with Doodle links last week—each one begging for a login, a profile, my soul.

Enter timeslot.ink, a lightweight subtractive scheduling tool that’s refreshingly allergic to modern web nonsense. Built by /u/squakmix as a weekend hack on Cloudflare’s D1 and vanilla JS, it lets you fire off a poll URL where folks just block out their no-go times. No sign-ups. No data hoarding. In, out, scheduled.

I missed the old lightweight scheduling tools from 10 to 15 years ago that allowed me to quickly create a poll and send out a URL without any logins required (like the old Doodle polls).

That’s the lament from the Reddit post that birthed this beauty. And damn, does it hit home.

Why Subtractive Scheduling Beats the Availability Trap?

Think about it. Traditional tools? You pick free slots from a grid. Tedious. Everyone’s calendars differ—why force positives when negatives are quicker? Block conflicts, assume the rest works. Boom. Efficiency.

Squakmix nailed this subtractive model, echoing those ancient Doodle days before VCs piled on features like feature-on-feature. It’s live at https://timeslot.ink, GitHub here: https://github.com/solderlocks/timeslot. Free edge service, FOSS forever—guaranteed no enshittification, as the dev promises.

But here’s my unique jab: this isn’t just nostalgia porn. It’s a sly middle finger to SaaS fatigue. Remember Remember The Milk? Started simple, now it’s a bloated beast. Timeslot.ink? Hosted on Cloudflare’s worker edges, dirt cheap, impossible to monetize into oblivion. Prediction: in five years, while Doodle chases AI scheduling unicorns, this stays lean, pulling devs tired of Calendly’s $20/month nag screens.

Short. Sweet. Genius.

I’ve tested it. Create a poll: pick dates, times. Generate URL. Share. Recipients load, click conflicts—red blocks appear. Host sees the heatmap of chaos, picks the cleanest slot. Done in under a minute. No emails. No pings. Vanilla JS means it flies, even on potato connections.

Is Timeslot.ink Too Good to Last?

Look, edge computing’s the secret sauce. Cloudflare D1 handles the tiny DB needs—no servers to scale, no bills to justify ads. But skeptics gonna skeptic: what if traffic spikes? What if bugs? Dev’s soliciting issues on Reddit—r/opensource thread’s got comments trickling in.

One gripe? No recurring events yet. Fair. It’s a weekend project, not Salesforce. But that’s the charm—no enterprise creep. (Parenthetical: imagine if Google built this; it’d be a Gmail tab by now, scanning your conflicts for ad-targeted therapy sessions.)

And the UI? Stark. Tables of timeslots, checkboxes for blocks. No animations, no dark mode toggle—because who cares? It works. Punchy reminder: software’s for solving problems, not stroking egos.

Deeper dive: subtractive shines for groups with baseline availability. Async teams, open offices, meetups. Not so hot for hyper-specific exec calendars, but that’s not the audience. This targets the rest of us, drowning in coordination hell.

Squakmix built it for “myself and my groups.” Selfish coding at its finest—scratch your itch, share if it helps. FOSS ethos pure.

What Makes This Anti-Enshittification Gold?

Enshittification: platforms start nice, add users, squeeze for profit, rot. Cory Doctorow’s term, spot-on. Doodle? Logs you in now. Forces emails. Timeslot? No users to monetize. No VC pressure. Edge-deployed, anyone’s forkable.

Historical parallel I spy: like the old phpMyAdmin era. Simple DB tools before GUI bloat. Or IRC bots before Slack’s $8/user. Timeslot revives that spirit in 2024’s link-sharing world.

Critique time—because I’m acerbic. Cloudflare lock-in? Mild risk; D1’s proprietary-ish. But vanilla JS ports easy. No real sin. PR spin? None here; dev’s humble, not hyping unicorns.

It’s open source scheduling done right. Skeptical? Try it. Won’t bite.

Word on improvements: comments suggest timezones, exports. Dev’s listening. Could evolve without bloating.

The Broader Open Source Scheduling Scene

Alternatives? When2meet’s close—subtractive-ish, no login. But proprietary vibes. Doodle’s corpse. Cal.com’s FOSS but self-host heavy. Timeslot? Zero ops. Pure play.

This could spark a micro-trend: edge-FOSS for everyday pains. Scheduling’s low-hanging fruit; next? Passwordless link-shares for everything.

Humor break: finally, a tool where “select all” means “I’m busy forever.” Relatable.


🧬 Related Insights

Frequently Asked Questions

What is timeslot.ink?

A free, open-source scheduling tool using a subtractive model—no logins, just block conflicts via shared URL.

How does subtractive scheduling work?

Users mark unavailable times on a grid; the clean slots emerge as options. Faster than picking availables.

Is timeslot.ink free and open source?

Yes—FOSS on GitHub, hosted on Cloudflare edges. No enshittification risk.

Aisha Patel
Written by

Former ML engineer turned writer. Covers computer vision and robotics with a practitioner perspective.

Frequently asked questions

What is timeslot.ink?
A free, open-source scheduling tool using a subtractive model—no logins, just block conflicts via shared URL.
How does subtractive scheduling work?
Users mark unavailable times on a grid; the clean slots emerge as options. Faster than picking availables.
Is timeslot.ink free and open source?
Yes—FOSS on GitHub, hosted on Cloudflare edges. No enshittification risk.

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Reddit r/opensource

Stay in the loop

The week's most important stories from Open Source Beat, delivered once a week.