3 ms·
Ah yes, because apparently no one besides GitHub is qualified to run reliable services. https://status.sr.ht/ https://status.sr.ht/ https://www.githubstatus.c
by ddevault 6y ago
Ah yes, because apparently no one besides GitHub is qualified to run reliable services.
https://status.sr.ht/ https://status.sr.ht/
https://www.githubstatus.com/ https://www.githubstatus.com/
https://sourcehut.org/blog/2020-07-03-how-we-monitor-our-services/ https://sourcehut.org/blog/2020-07-03-how-we-monitor-our-ser...
https://drewdevault.com/2019/01/13/Backups-and-redundancy-at-sr.ht.html https://drewdevault.com/2019/01/13/Backups-and-redundancy-at...
When your mail server goes down, nothing happens, the internet continues to function normally and then when it comes back up you will receive all of the emails that were sent to you when it was offline. If the mailing list goes down, you can still send emails and you're collagues probably won't even notice the outage because they were CC'd. When the mailing list comes back up, it'll receive all of those emails in the same way and get caught back up.
When GitHub goes down, everything stops. And GitHub goes down often!
- sreevisakh 6y agoI started trying out sourcehut out of curiosity and only recently started understanding the resilience and convenience of email workflow compared to Fork-PR workflow. It's also is clear to me that the pains with the email workflow is the user experience and not the workflow itself. None of this was apparent in the beginning (and hence the complaints). It would be great if there was a single page listing comparison of both workflows against specific technical points like these.