Live data from Hacker News

Cal.diy: open-source community edition of cal.com

github.com

41–50 of 75 posts

Re: Cal.diy: open-source community edition of cal.com

#41
post #33
post #18

I just installed calrs, a recent alternative to cal.diy. It absolutely rocks! The only downside is that it requires me to activate STARTTLS as force-TLS-SMTP isn't supported (I had to check the source code). It’s young, very promising, and honestly, I don't know what I could ask for more. I also replaced Radical with rustical, and I gained free push updates. https://cal.rs/ and https://github.com/lennart-k/rustical A…

Seems to be mostly vibe coded.

Who gives a shit. Cal.com is written by hand and the code is absolute garbage. Of all people that should be luddites I never imagined software engineers would be the most pointlessly staunch advocates of that philosophy.

Re: Cal.diy: open-source community edition of cal.com

#43

Tempted to buy cal.zone or cal.sucks just to add the paid features to cal.diy. They even made a list! Teams, Organizations, Insights, Workflows, SSO/SAML, and other EE-only features have been removed cal.ws is $630 on Namecheap... the tokens required to build this are cheaper than the domain.

I'm surprised cal.zone is not taken already

It still isn't taken but it's now $20k.

Re: Cal.diy: open-source community edition of cal.com

#44
post #14

Earlier quoted context omitted.

What do you want, it’s hard to resist VC money and “the enterprise offering”

Not impossible though, I run a directory of open-source alternatives and rarely do you see what Cal.com did. Projects gets abandoned yes, but a pure bait and switch like this really grinds my gears. This is from someone who is self hosting Cal.com right now and now they are going to strip even more features.

Are you really claiming you would rather the project get abandoned?

Re: Cal.diy: open-source community edition of cal.com

#45
post #8

From the docs, "It is strictly recommended for personal, non-production use." Wow what a 180 from just a year ago when their blog said, "For companies that handle sensitive information, deploying open-source scheduling software on-premises can offer an extra layer of security. Unlike cloud services controlled by external vendors, on-prem installations let teams maintain full ownership of their infrastructure. " ¹ I j…

I think this is less a bait and switch and more just a legal liability shield. They're not saying you 'cant' use it that way. They just don't recommend you do, and they won't support you at all for doing so. Which I think is completely fair. Also, these two things aren't in contradiction. Deploying on prem does offer more security, but then it's up to you to use it correctly.

But the OSS license already absolves them of responsibility. This might just be to set the tone that security fixes won't be prioritized to the standard that they used to be.

Re: Cal.diy: open-source community edition of cal.com

#47

Earlier quoted context omitted.

Not impossible though, I run a directory of open-source alternatives and rarely do you see what Cal.com did. Projects gets abandoned yes, but a pure bait and switch like this really grinds my gears. This is from someone who is self hosting Cal.com right now and now they are going to strip even more features.

Are you really claiming you would rather the project get abandoned?

Problem is using opensource as GTM strategy, to get developer contribution, traction and then say fuckoff.

Re: Cal.diy: open-source community edition of cal.com

#48
post #45
post #8

Earlier quoted context omitted.

I think this is less a bait and switch and more just a legal liability shield. They're not saying you 'cant' use it that way. They just don't recommend you do, and they won't support you at all for doing so. Which I think is completely fair. Also, these two things aren't in contradiction. Deploying on prem does offer more security, but then it's up to you to use it correctly.

But the OSS license already absolves them of responsibility. This might just be to set the tone that security fixes won't be prioritized to the standard that they used to be.

You seem really confident that an OSS license would protect them from liability… what is that confidence based on?

Re: Cal.diy: open-source community edition of cal.com

#49
post #11

Earlier quoted context omitted.

I'm unpersuaded by the assertion that closing the source is an effective security bulwark. From that page: > Today, AI can be pointed at an open source codebase and systematically scan it for vulnerabilities. Yeah, and AI can also be pointed at closed source as soon as that source leaks. The threat has increased for both open and closed source in roughly the same amount. In fact, open source benefits from white hat s…

How are LLMs at reading assembly? I assumed they’d be able to read assembly about as well as any other language… Is there such a thing as a closed source program anymore?

They are REALLY good at it.

Re: Cal.diy: open-source community edition of cal.com

#50
post #27

As a former cal.com advocate, I am now going to be switching my two companies to cal.diy or a similar alternative and canceling my cal.com subscriptions. I am now actively rooting for cal.com to go out of business now as a cautionary tale for any company thinking about taking open source projects proprietary. FOSS || GTFO

If you are looking for an alternative then please take a look at NeetoCal https://neeto.com/cal . It's closed source though.

Disclosure: I'm the CEO of NeetoCal.

Post reply on HN