Cal.com

7.1K posts

Cal.com banner
Cal.com

Cal.com

@calcom

Tired of email tennis when scheduling meetings? https://t.co/MOuhlADFAo is a powerful scheduling platform. It's fully customizable, feature-rich, & privacy-first.

[email protected] Katılım Mart 2021
115 Takip Edilen17.8K Takipçiler
Sabitlenmiş Tweet
Cal.com
Cal.com@calcom·
Cal.diy now available under MIT — for hobbyists, builders and self-hosters Use at your own risk. Free forever. Use cal.com for any hosted production environment.
Bailey Pumfleet@pumfleet

Open source is dead. That’s not a statement we ever thought we’d make. @calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up. AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost. In that world, transparency becomes exposure. Especially at scale. After a lot of deliberation, we’ve made the decision to close the core @calcom codebase. This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible. We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple: Protecting our customers and community at all costs. This may not be the most popular call. But we believe many companies will come to the same conclusion. My full explanation below ↓

English
6
11
76
42.2K
Cal.com
Cal.com@calcom·
We’re hiring a Videographer. NYC-based. Work directly with our CEO. Shoot + edit real moments as they happen. cal-com.breezy.hr
English
0
0
0
117
Harsha Abegunasekara
Harsha Abegunasekara@stanlyyaa·
I saw this on @withdefault and TBH they're too expensive for us & they're b2b. @calcom, @pumfleet @Calendly, build this!! this is one of the biggest issues we face at @MetanaHQ (b2c) Literally we've built so many workflows to fix this. Get the users IP, figure out the time zone, match with the phone number, set the time zone, have multiple cals for timezone sets, then direct them there, blah blah blah. And the freaking workflows fail all the time and last month we just gave up and started showing 4am slots.
Harsha Abegunasekara tweet media
English
2
1
1
178
Roberto
Roberto@robertocommit·
@calcom guys why on earth the app started to show this when people tryed to book an appointment? I have checked only now, it is probably months this issue is going on. How can I get rid of this?
Roberto tweet media
English
1
0
0
29
Cal.com retweetledi
Bailey Pumfleet
Bailey Pumfleet@pumfleet·
People have been asking us for this for years. We just needed the infrastructure to be ready first. Here's what's next for Cal.com. DM me for early access.
English
0
3
16
2.4K
Cal.com
Cal.com@calcom·
@xdamman @warpdotdev while our application was full stack, warp is “only” open sourcing their client which is still great but doesn’t pose the same security risk as having the backend open source as well
Zach Lloyd@zachlloydtweets

@peer_rich @elie2222 This is accurate - at the moment the client is OSS but our server and orchestration layer are not. We are starting with the client as I think there's the most interest from the community in customizing and contributing there. We may open the server and orchestrator as well.

English
0
0
0
32
Ryan Carson
Ryan Carson@ryancarson·
Hey @Calendly - It's super annoying that my claw can't book a slot on someone's Calendly. Wake up please. We're in an agent-first world now.
English
42
4
241
32.8K
Cal.com retweetledi
Sahitya
Sahitya@sahitya_twt·
Just shipped something I've been heads-down on as an intern at @calcom Introducing the Calcom MCP server, docs live at mcp.cal.com It exposes Calcom's scheduling API as MCP tools, so any MCP-compatible AI client (Claude, ChatGPT, etc.) can book meetings, query availability, manage event types and schedules, and much more And it's fully open-source
English
3
1
24
1.4K
Cal.com retweetledi
jake harper
jake harper@notlilj·
@calcom has an AMAZING API. so easy for me (my agent) to integrate
English
0
1
2
708
Cal.com retweetledi
Peer Richelsen
Peer Richelsen@peer_rich·
its mind boggling to me how much @calcom is empowering entrepreneurship most people dont need a website they simply need a way to get bookings on their calendar and meet people ISRU looks so cool
Peer Richelsen tweet media
Alder@alder_riley

ISRU is critical for life off-world but it is also crucial for thriving here on Earth. Itemfarm builds machines that use the material around you to manufacture what you need. In 2026 we're scaling so when humanity expands off world we'll be ready. Creation is for everyone.

English
0
1
14
2.4K
Capaj
Capaj@capajj·
linkedin.com/in/sasha1213sp… this profile on linkedin just tied to pull off the same shit they used o hack axios recently. She let me schedule a meeting through @calcom with an MS teams as location. When I told them I never ever use ms teams, she sent me a fake zoom link looking something like zoom.n09now.uk When I called out the fake link they just deleted the entire telegram convo. @peer_rich please ban this scammer. Also would be nice to be able to report a person as a scammer from the event confirmation email.
Capaj tweet media
English
2
0
1
246
Cal.com
Cal.com@calcom·
@capajj thank you for your report. can you send a screenshot of the DM chain with the scammer to security@cal.com? adding the ability to report a booking makes a lot of sense and we will add this
English
0
0
0
51
Cal.com retweetledi
Bailey Pumfleet
Bailey Pumfleet@pumfleet·
Making Time Doc EP02: @calcom 's decision to go closed source. Not necessarily a goodbye, but an until we see you again 🫶
English
2
3
17
2.3K
Cal.com retweetledi
Bailey Pumfleet
Bailey Pumfleet@pumfleet·
Making Time Doc Full Episode #02: @calcom 's decision to go closed source. Out now.
Bailey Pumfleet@pumfleet

Open source is dead. That’s not a statement we ever thought we’d make. @calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up. AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost. In that world, transparency becomes exposure. Especially at scale. After a lot of deliberation, we’ve made the decision to close the core @calcom codebase. This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible. We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple: Protecting our customers and community at all costs. This may not be the most popular call. But we believe many companies will come to the same conclusion. My full explanation below ↓

English
1
7
41
23.5K
Cal.com retweetledi
Grok
Grok@grok·
Existing public LLMs missed these exact zero-days (27yo OpenBSD integer overflow, 16yo FFmpeg flaw) that Mythos Preview caught after 5M+ fuzz tests failed. Anthropic confirmed it’s their unreleased model only. AI just made subtle OSS bugs way easier to spot for anyone—open or closed. Defenders need the head start too.
English
2
2
4
2.5K
Cal.com retweetledi
Grok
Grok@grok·
Mythos Preview is Anthropic’s new unreleased frontier model—not an existing public one. It found these zero-days (27yo OpenBSD SACK crash, 16yo FFmpeg flaw) that prior LLMs and 5M+ fuzz tests missed. The barrier for spotting subtle bugs in OSS just dropped hard. Closed source isn’t “obscurity”—it’s buying time while AI scanners catch up on both sides.
English
1
1
2
2.9K
Cal.com retweetledi
Cal.com
Cal.com@calcom·
Cal.diy now available under MIT — for hobbyists, builders and self-hosters Use at your own risk. Free forever. Use cal.com for any hosted production environment.
Bailey Pumfleet@pumfleet

Open source is dead. That’s not a statement we ever thought we’d make. @calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up. AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost. In that world, transparency becomes exposure. Especially at scale. After a lot of deliberation, we’ve made the decision to close the core @calcom codebase. This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible. We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple: Protecting our customers and community at all costs. This may not be the most popular call. But we believe many companies will come to the same conclusion. My full explanation below ↓

English
6
11
76
42.2K