Earlier quoted context omitted.
Too bad, I was really excited about Gitflare :)
Cloudgit has more buzzword power.
Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
41–50 of 79 posts
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#42How about Github without a big corporation? Not controlled by Cloudflare, ddecentralized and uncensorable. Like bittorrent, but for git repos, issues, etc.
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 directly from each other (though we couldn't push).
Hell, even a "private" git repo wouldn't be too hard as long as you don't care about per-project permissions. Just make a user (e.g. 'git') that has read/write access to the folder and add some SSH keys to authorized_keys. Shazam, you have a private, self-hosted git repo at ssh://git@yoursite.com:path/to/repo.git.
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#43Are there any updates to the Cloudflare Registrar? Would be awesome to have marketplace or master/sub accounts. That is, launch a saas say a landing page builder and then allow my customers to also purchase domains from my saas (under my brand account) and have them automagikally configured. Instead of having the user to use namecheap/godaddy and mess around with their crappy control panel. Maybe have an opportunity…
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#44How about Github without a big corporation? Not controlled by Cloudflare, ddecentralized and uncensorable. Like bittorrent, but for git repos, issues, etc.
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…
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#45Cloudflare folks. Please don’t do this. I don’t know if Mr.Cumming is serious. As a user of CF, I hope you folks go a lot deeper than broader. Example: Better cache management – compete with Fastly, my tickets on load balancer bugs were open for almost 6 months, etc.
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#46More seriously. I’d be curious to hear about what you’d build on our network. We are all over the world and it would be fun to hear about companies other than GitHub that you think we should disrupt.
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#47Earlier quoted context omitted.
> quality of the repo (as measured by forks/stars/pagerank...) These two seem unrelated. Quality is not measured by popularity. There is plenty of popular stuff that's junk, and good stuff that nobody uses.
Precisely. For my organization, I'm looking for a way to quantitatively measure and compare quality/security postures of repos/packages when importing.
For the security angle it seems the first naive thing would be to count prior known vulnerabilities, but then, the projects that do absolute worst at that are not going to have discovered their security bugs let alone document them well.
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#48Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#49More seriously. I’d be curious to hear about what you’d build on our network. We are all over the world and it would be fun to hear about companies other than GitHub that you think we should disrupt.
While the ITP (Safari's -and maybe Chrome soon-- attempt to regulate tracking) initiative is on paper a good idea, I'm not convinced it's going to deliver.
Barging in with an OpenRTB v4 (current version is V3) that delivers on that - and maybe cut the middle men, that could be neat for every one : publishers, consummers and advertisers.
Re: Cloudflare CTO: “If we did [take on GitHub] what features would you like?”
#50Global Memcached or Redis. Support caches near the edges. SPA or apps running on a client's browser/machine can use the one nearby. Support pre-populating/warm-up the caches in batch.