[deleted]
Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
21–30 of 440 posts
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#22Is my company's private information e.g. source code kept end-to-end encrypted?
All data is encrypted in-transit and at-rest, as per the industry standard. End-to-end encryption is an interesting feature with obvious extended privacy benefits on one hand, that could prevent a system from providing other features on the other hand. Depending on the requirement for end-to-end encryption, in some instances a custom NDA can be signed to mitigate a specific concern. It's a feature we haven't seen much demand for, but if that changes we may prioritize it higher on the road map. Would you mind sharing your use case or concern?
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#23[deleted]
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#24Nice. I make music and use git for my files, but often hit the usual space limitations and I hate dealing with git-lfs. I think there's a big use case for Diversion and music/video production.
Nice! We didn't even know about that. Thanks!
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#25Perforce seems to already fill this niche pretty well, at least in the gaming sector which this startup seems to target.
Totally right, perforce is used by almost all large game studios. But it's painful to use for smaller studios and indie devs - it requires managing your own server with configuration, backups, networking etc. It's also not great for cloud based workflows and remote work, and super expensive with rigid licensing.
Most of the time we need to host our own servers for licensing issues, you might need to consider a "on premises" option if you want to be an viable option for a lot of studios.
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#26Nice. I make music and use git for my files, but often hit the usual space limitations and I hate dealing with git-lfs. I think there's a big use case for Diversion and music/video production.
Nice! We didn't even know about that. Thanks!
Yeah, collaboration in music and video production is pretty unsolved. It often involves sharing huge files in GDrive/Dropbox, lots of project_latest_january_version_3_final_modified_updated.zip etc
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#27> In our previous startup, a data scientist accidentally destroyed a month’s work of his team by using the wrong Git command. While git is indeed a usability clusterbomb and there is massive space to improve, the problem above sounds like a devops failure. Git gives you all the tools to prevent such a disaster, all you have to do not give the root password of your CI server to any data scientist. On the topic of your…
True! They didn't actually have a root pwd to anything, the repo was hosted on BitBucket which didn't have a branch protection feature back then. Non-coder users are actually an important use case for Diversion (like in game development where many/most users are artists).
And nobody on the team had a reasonably fresh checkout of the repo on their local machine?
To put it bluntly, this story does not sound credible. It's also one of the first things you say in the pitch, which taints everything you write later. I would suggest focusing on what you do well, not in making up stories about data loss with what you perceive as the competition.
(It's especially odd when Git isn't the obvious competition; Perforce is.)
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#28I have not analyzed the full potentials and benefits of Diversion but I would not agree with the statements you made about the Git. I think you should not focus on Git in your pitch. >> it was built for a very different world in 2005 (slow networks, much smaller projects, no cloud) Slow network: why is this a negative thing? If something is designed for a slow network then it should perform well in a fast network. Mu…
Even a force push doesn't destroy the reflog or runs the GC server-side. I wonder how you can accidentally loose data with Git. I've seen lot's of people not being able to find it, but really destroying it is hard.
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#29I have not analyzed the full potentials and benefits of Diversion but I would not agree with the statements you made about the Git. I think you should not focus on Git in your pitch. >> it was built for a very different world in 2005 (slow networks, much smaller projects, no cloud) Slow network: why is this a negative thing? If something is designed for a slow network then it should perform well in a fast network. Mu…
> This is mostly a configuration issue. I guess this was done by a force push command. IFAIK, you can disable force push by configuration.
If a feature can lead to actual unintended data loss, it should come disabled by default. Are there any other "unsafe by default" features in Git? What would be a sane general default that prevents unwanted data loss, and why is it the case?
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#30Focusing on Git seems like completely the wrong pitch. Git is a distributed VCS - in all your examples you were clearly trying to use Git in a centralized manner with no backups. I suggest focusing more on your own product than on Git.
You're totally right, we were using BitBucket and pushing and pulling from there. It's really more of a centralized manner, but this is the usual workflow for most teams and companies and what they actually need (a single source of truth). Totally agree about backups, lesson learned :)
Until the day, the company is target by a ransomware group and everything is switched off in panic. Or the day the network connection of a building goes down. Requiring a REST api in the cloud for every VCS is command bytes hard then. We had this before with SVN and it wasn't nice.