Live data from Hacker News

Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

twitter.com

51–60 of 79 posts

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#51
post #41

Earlier quoted context omitted.

Cloudgit has more buzzword power.

If we smash them together we'd get Gitgit, which is probably the best option.

I need a name for our internal Gitea instance, do you mind if I grab this idea? Haha.

* gitgit.at — as in, gitgit.at/username/ * gitgit.dev * gitgit.ist — sounds funny

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#53
post #44

Earlier quoted context omitted.

So... git? It's already designed to be decentralized. Hosting a public read-only repo would be as easy as standing up NGINX and pointing it at your repo folder, afaik. At my previous job, we all had individual dev machines that we each had accounts on. So, we each had a copy of our repos that we could push to/work from. I wrote a little git alias that would add remotes for each others' machines so we could pull direc…

Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but there is no standard format that allows easy migration and inter-linking.

Well for wiki, usually a branch containing markdown will transfer well across forges. Issues and PRs are the real issue. I’ve been hoping git appraise would get supported by the forges for distributed PRs, but it doesn’t look like that’ll happen.

Gitlab is implementing MRs via git send-email though, which is part of an epic to federate Merge Requests: https://gitlab.com/groups/gitlab-org/-/epics/260 .

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#55

I’m amused this is here. This was a random reply to someone who thought maybe we were doing this. To be clear: that’s all this is. But I’m happy to hear all the suggestions.

Do you have some kind of a script for these CF threads or do you just spend that much time on HN? :)

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#57

The most useful thing Cloudflare could do is allow us to disable the `__cfduid` cookie. That's one of the big reasons I stopped using Cloudflare on a public-facing API/CDN.

Just curious, what is your concern? Is it privacy related? Or does it inhibit consumption of APIs you tried to host with them? I don’t like the header either and I have a public API with Cloudflare but it hasn’t caused any technical issues as far as I know.

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#58

I’m amused this is here. This was a random reply to someone who thought maybe we were doing this. To be clear: that’s all this is. But I’m happy to hear all the suggestions.

After clicking through, this was pretty obvious. I think there are just a lot of fired up hackers out there wanting to see WW3 between Github, Gitlab and the rest of the world.

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#59

I’m amused this is here. This was a random reply to someone who thought maybe we were doing this. To be clear: that’s all this is. But I’m happy to hear all the suggestions.

well you could help out gitea and make a hosted version on gitlab. there is a ton of stuff which cloudflare could do, like creating a object storage git backend, etc..

Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”

#60
post #41

Earlier quoted context omitted.

If we smash them together we'd get Gitgit, which is probably the best option.

I need a name for our internal Gitea instance, do you mind if I grab this idea? Haha. * gitgit.at — as in, gitgit.at/username/ * gitgit.dev * gitgit.ist — sounds funny

Feel free!
Post reply on HN