4 ms·
folks should probably avoid linking their own personal git forge (or others, if this is the case) to HN and just use GitHub to share their code. or deploy the c
by riffic 4y ago
folks should probably avoid linking their own personal git forge (or others, if this is the case) to HN and just use GitHub to share their code. or deploy the content to a static site host.
- aliqot 4y agoWhy even have any sites in other places? Why not just put everything on Github, then it's all in one place within reach at us-east-2
- riffic 4y agoI'm thinking in terms of etiquette and experience. It's not really polite to throw a bunch of unexpected traffic at a little lowly app server
- prepend 4y agoSince I host a little lowly app server with a public listener on 80, I’m cool with whatever traffic is thrown. And that’s good etiquette. The web was built for lots of distributed servers hosting and users hitting them. Only using “big servers” is bad for the world.
- riffic 4y agoPostel's law, I suppose, is the right way to look at it.
- autotune 4y agoAgreed, even as a SRE myself it is just easier to link to a GitHib repo. GH, with all of its warts, is still likely better at handling a traffic spike than you.
- jgwil2 4y agoLink elsewhere in this thread[0] shows that this user removed this repo from GitHub deliberately, so I doubt they're the account who shared it. [0]: https://news.ycombinator.com/item?id=33897373 https://news.ycombinator.com/item?id=33897373
- AceJohnny2 4y agoPeople are free to host however they like. They can't control who posts links on popular aggregators.