4 ms·
TIL about https://github-debug.com/ https://github-debug.com/ and https://www.fastly-debug.com/ https://www.fastly-debug.com/ and https://dropbox-debug.com/ htt
by simonw 8y ago
TIL about https://github-debug.com/ https://github-debug.com/ and https://www.fastly-debug.com/ https://www.fastly-debug.com/ and https://dropbox-debug.com/ https://dropbox-debug.com/ - neat pattern.
- sbr464 8y agoGood find, I like this pattern. I could see a niche startup or open source solution providing this as a service, similar to statuspage (acquired by atlassian). It could also help keep the layout consistent, for user familiarity.
- fireattack 8y agoIf you have trouble to connect to github.com how you're going to "git clone https://github.com/[xxx]" https://github.com/[xxx]"?
- dpcx 8y agoBecause it's possible that you can't clone from the https endpoint but you can from the git endpoint, which helps them (and you) debug the cause.
- fireattack 8y agoYeah, but then the last step is to "copy & paste the results" to .. https://github.com/contact https://github.com/contact
- Operyl 8y agoI'm assuming it also logs some debugging information with regards to your git client's behavior, though. So you could still be able to get to that contact form.
- hamandcheese 8y agoYes, presumably being unable to clone is an important data point.
- fireattack 8y agoMy point is chances are you can't visit https://github.com/contact https://github.com/contact to paste your debugging result, if you're "Having trouble connecting to github.com".
- sitepodmatt 8y agoHa good catch
- phoenix24 8y agopretty cool. quick question, why not just make - https://github.debug https://github.debug or - https://debug.github.com https://debug.github.com
- mongol 8y agoWhy would that be better?
- tgtweak 8y agoTo isolate possible issues with gtld, dns + glue records, registrar, domain blocking (corporate firewalls, restricted/compromised user dns, malware) that affects .com (the github.debug that is, debug.github.com is not a good solution for the above reasons)
- SaveTheRbtz 8y agoThe main principle here is to reuse as less infra as possible: different dns provider, different hosting, different cert authority, etc. So, debug.github.com is probably worse, than github-debug.com (github.debug should be fine though, and even slightly better than github-debug.com)
- phoenix24 8y agothank you! i understand now.
- fireattack 8y agoHi, I assume you're the writer or at least work at Dropbox. Just want to let you know (as I mentioned somewhere): this blog link doesn't load at all if I click from here (i.e. with the refer of news.ycombinator.com).
- chaz6 8y agoYou could use two independent dns providers for the same domain (i call it inverse split horizon). I am a proponent of dns service discovery (using NAPTR and SRV records) so that by going to e.g. www.github.com, the dns provides a list of servers, and the final server would be your debug site (kind of like how there are MX records with different priorities, except naptr/srv is service agnostic).
- phoenix24 8y agoIs this open-source, how can I make one for my company?
- wulfmann 8y agoRead the headers from the request to your service. Pull browser information from navigator (in a browser try: console.log(navigator)). Should be most of the info.
- deleted 8y ago[deleted]