191–200 of 279 posts
Earlier quoted context omitted.
Your ISP could refuse service. This has happened. If you manage to start an ISP people could refuse to peer.
If you run your own AS you can buy bandwidth from literally any carrier, they famously don't give a triangular shit about what you do.
I contacted them and explained what I was doing and they reinstated it, but I always thought Github allowed and even encouraged "machine users" and thus multiple accounts.
I was definitely annoyed with their heavy-handed approach and lost trust; they could have emailed me first and given me a warning before just automatically shutting my account down and restricting access, assuming I'm a bad actor.
Earlier quoted context omitted.
If you truly wish to avoid this kind of problems you should think about hosting your own platform rather than jumping to the next one. Just because the smaller players haven't done anything bad doesn't mean they wouldn't. Gitea/Gitlab are crazy easy to set-up nowadays, especially with a fully working CI/CD setup (I use Gitea+Drone and I love it, Gitlab comes with its own)
Problem is that there are so many services that integrate with github directly that moving to other alternatives will also require moving/replacing those 3rd party services.
Earlier quoted context omitted.
You don't need a hosting provider. Your code fits on each developers' machine. (Remember when git was touted as a distributed version control system?) If it doesn't, you're at the scale where you're not worrying about your hosting provider dropping you — they're worried about you dropping them.
That's just as true of GitHub though, and isn't the problem. The problem is the related services, like issues, PRs and now CI/CD which all sit with the code but don't come down on a clone. That problem still hasn't been solved, which could mean your whole knowledge base goes missing if you lose access to the server. CI/CD can maybe be replicated from what's on your laptop, but if you don't have the PR history it coul…
Earlier quoted context omitted.
You'd be surprised how much an acquisition changes priorities. Suddenly the CEO of your company is a middle manager at the acquiring behemoth who is at the whims of their generous crop of Senior Vice Presidents, and wants to keep them happy because s/he has a ton of unvested stock on the line. I don't know what the precise cause of this bad support is, but I would wager that an acquisition by Microsoft will shift Git…
Just so you know how distant Microsoft is keeping this acquisition, Github employees don't show up on the default lookup tool (Who). I'm sure they're pedalling Azure, but other than that Github is still very much independent.
Earlier quoted context omitted.
These companies have millions of customers. Nothing is perfect and scale will always bring problems, both in quantity and depth. The massive success and reliability of cloud services doesn't point to a major risk for most. Regardless I don't see what the issue is in waiting for the full story.
That you'll be waiting forever?
Earlier quoted context omitted.
If you run your own AS you can buy bandwidth from literally any carrier, they famously don't give a triangular shit about what you do.
What is AS?
Earlier quoted context omitted.
If you run your own AS you can buy bandwidth from literally any carrier, they famously don't give a triangular shit about what you do.
What is AS?