I guess this is an AI excuse again.
Cal.com is going closed source
181–190 of 337 posts
Re: Cal.com is going closed source
#182Security by obscurity. Good luck. So novice.
Re: Cal.com is going closed source
#183> When we started Cal.com, we believed deeply in open source.
No you certainly didn't, otherwise you shouldn't have come up with such a meaningless excuse!
Re: Cal.com is going closed source
#184Earlier quoted context omitted.
I'm not a security expert but can't close source applications be vulnerable and exploited too? I feel like using close source as a defense is just giving you a false sense of security.
What is being phrased as obscurity is one of the approaches to security as long as you are able to keep the code safe. Your passwords, security keys are just random combination of strings, the fact that they are obscure from everyone is what provides you the security
Decompilation and you are back to the level of security you started with. OpenSSH is open for a good reason. Please acknowledge your error. Are you AI?
Re: Cal.com is going closed source
#185Earlier quoted context omitted.
I have a feeling the real reason is them trying to avoid someone using AI to copyright-wash their product, they're just using security as the excuse.
An app like Cal.com can be vibe coded in a few evenings with a Chrome MCP server pointed to their website to figure out all the nooks and crannys. The moat of Cal.com is not the code, it's the users who don't want to migrate. The real answer is they are likely having a hard time converting people to paid plans
For real, one of the reasons I use cal.com is because it's open source. Time to migrate.
Re: Cal.com is going closed source
#186This seems kind of crazy. If LLMs are so stunningly good at finding vulnerabilities in code, then shouldn't the solution be to run an LLM against your code after you commit, and before you release it? Then you basically have pentesting harnesses all to yourself before going public. If an LLM can't find any flaws, then you are good to release that code. A few years ago, I invoked Linus's Law in a classroom, and I was…
Write simple code. Do what you said, which is a very good idea. Test LLM security against the compiler too.
Re: Cal.com is going closed source
#187Head of Thunderbird project here. Our scheduling tool, Thunderbird Appointment, will always be open source. Repo here: https:// github.com/thunderbird/appointment Come talk to us and build with us. We'll help you replace Cal.com
> Come talk to us and build with us
do we need an appointment :)
Re: Cal.com is going closed source
#188Earlier quoted context omitted.
Not really. Open source just means distributing the source. Either via CD or some internet based protocol. Maybe you are referring to the whole Github thing.
I mean, by definition, open source means that the source code is available and therefore _open_ to scrutiny. Regardless of how it is distributed.
Right. But what is the problem?
* Someone lols at code. Answer: ignore them.
* Someone sees your vulns. Answer: someone is already trying to hack you anyway.
Re: Cal.com is going closed source
#189Earlier quoted context omitted.
Sunk cost is sufficient friction for most people even without network dependence.
For a meeting scheduler site? I feel like you're overestimating the capabilities of something that is akin to college graduate project. This company does not seem healthy at all: https://getlatka.com/companies/calcom I agree with the other poster that mention this is likely a publicity stunt but all it's really showing is that VC is still incredibly stupid with their money. All the more reason to seize it from them t…
About the friction, not the capabilities...I haven't switched off my biz calendar/appointment provider I'm paying for even though I've kinda outgrown it.
I wouldn't under estimate switching friction.
Re: Cal.com is going closed source
#190This has one of the most shittiest codebase out of all. Not surprised by this move.