Compiling Ruby to machine language
patshaughnessy.net
Show HN: I built a synth for my daughter
bitsnpieces.dev
Azure hit by 15 Tbps DDoS attack using 500k IP addresses
bleepingcomputer.com
Run ancient Unix on modern hardware
github.com
Show HN: Reversing a Cinema Camera's Peripherals Port
3nt3.de
Ion: Modern System Shell in Rust
github.com
“One Student One Chip” Course Homepage
ysyx.oscc.cc
FreeMDU: Open-source Miele appliance diagnostic tools
github.com
Show HN: Continuous Claude – run Claude Code in a loop
github.com
I caught Google Gemini using my data–and then covering it up
unbuffered.stream
Astrophotographer snaps skydiver falling in front of the sun
iflscience.com
Temporal Dithering of NeoPixels on an ATtiny412
sarah.alroe.dk
WeatherNext 2: Our most advanced weather forecasting model
blog.google
Show HN: ESPectre – Motion detection based on Wi-Fi spectre analysis
github.com
Show HN: Parqeye – A CLI tool to visualize and inspect Parquet files
github.com
How when AWS was down, we were not
authress.io
How to escape the Linux networking stack
blog.cloudflare.com
My stages of learning to be a socially normal person
sashachapin.substack.com
Giving C a superpower: custom header file (safe_c.h)
hwisnu.bearblog.dev
An official atlas of North Korea
cartographerstale.com
The time has finally come for geothermal energy
newyorker.com
Where do the children play?
unpublishablepapers.substack.com
Kalendis is an API-first scheduling backend. You keep your UI; we handle the gnarly parts (recurrence, time zones, DST, conflict-safe bookings).
What it does: • MCP tool: generates typed clients and API route handlers (Next.js/Express/Fastify/Nest) so you can scaffold calls straight from your IDE/agent tooling. • Availability engine: recurring rules + one-off exceptions/blackouts, returned in a clean, queryable shape. • Bookings: conflict-safe endpoints for creating/updating/canceling slots.
Why we built it: We kept rebuilding the same "hard parts" of scheduling: time zones/DST edge cases, recurring availability, conflict-aware booking, etc. We wanted a boring, reliable backend so we could ship product features without adopting a hosted scheduling UI.
How it's helped: We stopped re-implementing DST/recurrence math and shipped booking flows faster. One small team (just 2 developers) built a robust booking platform for their business using Kalendis—they kept full control of their UX without spending lots of cycles on scheduling infrastructure. The MCP generator cut the glue code: drop in a typed client or route, call the API, move on.
Some tech details: • REST API with ISO-8601 timestamps and IANA time zones • Recurring availability + one-off exceptions (designed to compose cleanly) • Focused scope: users, availability, exceptions, bookings (not a monolithic suite)
The MCP server exposes tools like generate-frontend-client, generate-backend-client, generate-api-routes, and list-endpoints. Add to your MCP settings:
How to try it: Create a free account → get an API key. (https://kalendis.dev). Then hit an endpoint: Happy to answer questions and post example snippets in the thread. Thanks for taking a look!