Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incident with Actions – Resolved

githubstatus.com

Post reply on HN
Print view View original

51–60 of 90 posts

Re: Incident with Actions – Resolved

#51

Post by tardedmeme »

johnfn wrote: post #24
foundatron wrote: post #4

I re-ask this: https://news.ycombinator.com/item?id=47979968 If everyone is vibecoding, and SaaS plays have no moats anymore, and everyone says they are mad at Github's reliability...why aren't there like 10 viable replacements already? Why are you still using Github?

- There are already viable GitHub replacements, like Codeberg, Bitbucket, Gitlab, etc. Everyone stays on Github for network effects, not because of the superior product. You can't vibe code network effects. - And yes, GitHub is a massive product with like 50 different huge features. No reasonable person would say you can trivially vibecode that. Vibecoding would still make it easier. I feel this argument is a bit sil…

What network effects does GitHub have? Every repository is independent. It's like saying GoDaddy has network effects.

Re: Incident with Actions – Resolved

#52

Post by tardedmeme »

CharlesW wrote: post #36
foundatron wrote: post #4

I re-ask this: https://news.ycombinator.com/item?id=47979968 If everyone is vibecoding, and SaaS plays have no moats anymore, and everyone says they are mad at Github's reliability...why aren't there like 10 viable replacements already? Why are you still using Github?

> Why are you still using Github? Stars. Grifters have discovered vibe-coding and the ability to buy GitHub stars, followers, etc. https://duckduckgo.com/?q=buy+GitHub+stars&ia=web

Why do stars and followers matter? Who is looking at them?

Re: Incident with Actions – Resolved

#53

Post by johnfn »

tardedmeme wrote: post #51
johnfn wrote: post #24

Earlier quoted context omitted.

- There are already viable GitHub replacements, like Codeberg, Bitbucket, Gitlab, etc. Everyone stays on Github for network effects, not because of the superior product. You can't vibe code network effects. - And yes, GitHub is a massive product with like 50 different huge features. No reasonable person would say you can trivially vibecode that. Vibecoding would still make it easier. I feel this argument is a bit sil…

What network effects does GitHub have? Every repository is independent. It's like saying GoDaddy has network effects.

Everyone already has an account, so there's no friction to opening up issues, adding thumbs up to issues, using the discussion forum, etc. And while I think it's pretty silly, a lot of people take "10k stars on GitHub" to be a positive signal, and you can only get there when you have 10k people willing to star on your platform.

Re: Incident with Actions – Resolved

#54

Post by SoftTalker »

johnfn wrote: post #24
foundatron wrote: post #4

I re-ask this: https://news.ycombinator.com/item?id=47979968 If everyone is vibecoding, and SaaS plays have no moats anymore, and everyone says they are mad at Github's reliability...why aren't there like 10 viable replacements already? Why are you still using Github?

- There are already viable GitHub replacements, like Codeberg, Bitbucket, Gitlab, etc. Everyone stays on Github for network effects, not because of the superior product. You can't vibe code network effects. - And yes, GitHub is a massive product with like 50 different huge features. No reasonable person would say you can trivially vibecode that. Vibecoding would still make it easier. I feel this argument is a bit sil…

Why do network effects matter for "in-house" (i.e. corporate/commercial) software work?

Open-source projects, yes I can sort of get it, you want to be where the contributors are (but there are downsides to that also).

Re: Incident with Actions – Resolved

#56

Post by levkk »

I'm using GitHub for my business and so do millions more. Might be time to prioritize paying customers, historically popular open source repos and PRs created by known human actors. Agents can wait, humans have much less patience.

Re: Incident with Actions – Resolved

#57

Post by bulte-rs »

deepdarkforest wrote: post #40
foundatron wrote: post #4

I re-ask this: https://news.ycombinator.com/item?id=47979968 If everyone is vibecoding, and SaaS plays have no moats anymore, and everyone says they are mad at Github's reliability...why aren't there like 10 viable replacements already? Why are you still using Github?

compute?? Github is struggling because of compute, which comes from everyone vibecoding and triggering actions 10x more. I can vibecode an alternative, but once i have users, who is going to secure this amount of compute? Compute+talent to manage it(devops isnt vibecoded *yet) is a moat

Why care about making a commercial alternative? I just want a “forge” for my team that looks like a combination of GitHub and tangled (stacked PRs and JJ).

So I’m working on waza.sh. I have NO intent on making it commercial, nor open-source (unless someone wants to collab on it).

Will it need compute? Yes! For my team only. So a dedicated box at OVH/Hetzner for 30eu is more than sufficient.

Re: Incident with Actions – Resolved

#58

Post by dspillett »

armanj wrote: post #16
LorenDB wrote: post #6

Down to 84.88% uptime: https://mrshu.github.io/github-statuses/ Can't even do three 8s properly.

How reliable is this uptime? and why it's sooo different from gh's official status numbers?

> How reliable is this uptime?

IT seems to be quoting incident reports for the duration of each outage, so there is accountability in terms of being able to verify all the details of what they are counting.

> and why it's sooo different from gh's official status numbers?

Maybe this is counting any period with any service showing any level of issue as a complete fail, and the official numbers are cherry-picking a bit (only counting core services? not counting significant performance issues that the other count does because things were working, just v…e…r…y … s…l…o…w…l…y) or averaging values (so 75% services running at a given time looks ¼ as bad in their figures), the two sets of calculations could be done with a different granularity, …

In other words: lies, damned lies, and statistics!

The only way to know is to know how both are calculated in detail, and that information might not be readily available.

Re: Incident with Actions – Resolved

#59

Post by xvilka »

datadrivenangel wrote: post #34
armanj wrote: post #16

Earlier quoted context omitted.

How reliable is this uptime? and why it's sooo different from gh's official status numbers?

1. This one counts downtime from any service, so if anything is down or degraded they count it as 100% down, which is harsh. 2. Github is doing some classic big org sneaky things where they don't count degraded service fully. So if github actions is partially down for most people in a away that makes you say "github is down", there's a good chance that microsoft doesn't count that or counts it partially instead.

> Github is doing some classic big org sneaky things where they don't count degraded service fully.

Even worse example is the Travis CI. For more than a year their CI jobs sometimes get stuck or do not start for days, and, surprise-surprise, it's never shown at their status page[1] - always green. We would switch to something else entirely if not the unique offering of PowerPC and SystemZ servers/runners. Apart from that - it's the worst CI service I used so far.

[1] https://www.traviscistatus.com/history

Re: Incident with Actions – Resolved

#60

Post by grayhatter »

Imustaskforhelp wrote: post #38

How is the company morale at github? I imagine it to be really very depressing working at github right now with all these downtime. I know github is being used by AI agents like there is no tomorrow but there have also been en-shittification attempts at github and I have seen some comments tell me that github can be more efficient. So what are people who are at github doing right now? Like what do the priorities look…

I'm not sure the uptime or UX of codeberg is meaningfully better?
Post reply on HN