231–240 of 343 posts
Earlier quoted context omitted.
Sometimes I'll catch myself absentmindedly reopening the browser and checking two or three front pages, seconds after having just checked them and closed the browser.
That's a sign of addiction and I highly recommend changing your behaviour towards those pages!
Earlier quoted context omitted.
Do you carry a literal pager? We use the PagerDuty app.
It may interest you to know that pagers are still a thing, Motorola still makes them, and I know that one major use case is volunteer fire departments I used to work on Motorola Minitor 5 pagers. Looks like they recently released their newest model, the Minitor 7 I wonder if pagers are still used in hospitals? I imagine so
When it was down my thought was "damnit, I'll actually have a productive workday now."
Next time you can avoid that fate by opening HN in a private browsing (or whatever your browser calls its equivalent) window. This outage, like the vast majority of HN outages, only affected logged in requests. I suppose you could also just clear your HN cookies in regular browsing window, but then when they fix it you'd have to log in again.
Earlier quoted context omitted.
Do you carry a literal pager? We use the PagerDuty app.
It may interest you to know that pagers are still a thing, Motorola still makes them, and I know that one major use case is volunteer fire departments I used to work on Motorola Minitor 5 pagers. Looks like they recently released their newest model, the Minitor 7 I wonder if pagers are still used in hospitals? I imagine so
Yes, sorry! We're investigating, but my current theory is we got overloaded because I relaxed some of our anti-crawler protections a few days ago. (The reason I did that is that the anti-crawler protections also unfortunately hit some legit users, and we don't want to block legit users. However, it seems that I turned the knobs down too far.) In this case, we also had a secondary failure: PagerDuty woke me up at 5:24…
There is an official dump which doesn't even require parsing HTML at all: https://console.cloud.google.com/marketplace/details/y-combi...
I'm with Hund. Our hn.hund.io page did not catch this because it was requesting the cached, unauthenticated page. It now monitors authentication as well.
Yes, sorry! We're investigating, but my current theory is we got overloaded because I relaxed some of our anti-crawler protections a few days ago. (The reason I did that is that the anti-crawler protections also unfortunately hit some legit users, and we don't want to block legit users. However, it seems that I turned the knobs down too far.) In this case, we also had a secondary failure: PagerDuty woke me up at 5:24…
1. Blame: The first thing to do is to point the finger. That doesn't mean analysing the technical issue, which can delay this step and limit your options, but figuring out who is politically easiest to blame. Often, that's the new guy, but outside contractors and vendors without good connections are also a common solution. Even if you are technically responsible for hiring them, you can always push them under the bus with a little skill. This small sacrifice helps unify, focus, and motivate the rest of the team.
2. Emotion: Inject your emotion into the situation and make that the implicit, but indisputable priority. Particularly, outrage and anger - This is completely _____. These people are utterly _____ (I'd use all caps, but that's not allowed on HN). Make sure everyone's attention is over their shoulder, on your emotion, and infect the team with it. Threats are an effective tool here - this is a crisis, and anyone who is calm is not emotionally engaged. Otherwise, they won't care enough about this problem - without you driving them, they probably wouldn't care much at all. Anyway, you don't have time for niceties like empathy or even basic respect.
3. Speed: Respnsiveness to stakeholders is very important. People need answers now. Give them answers they want to hear, outcomes they will be comfortable with. Don't worry if different groups hear different things. Your team will find a way to make it all work - that's their job.
4. Communication: Good communication is essential. Make sure you clearly tell your team what they should be doing; repeat it several times to prevent misunderstanding. Especially people with experience can have minds of their own; keep them on track. The situation is a crisis so you can't take any risks; stay on top of them and everything they do, and give input if you're not certain they are doing exactly what you would be doing.
5. Victimhood: Find a way to turn the tables: Make it about you, and how you're the victim here, and feed the fire with more outrage. With this and outrage, nobody will undermine the team by challenging your ideas or authority, which is the most essential component of a successful outcome. Remember, without you this all falls apart.
Have I missed anything?
Earlier quoted context omitted.
It's entirely possible that this is the smartest place on the internet, but also often dumb. In fact, it seems likely. More of an indictment of the rest of the places on the internet.
> It's entirely possible that this is the smartest place on the internet, but also often dumb. In fact, it seems likely. More of an indictment of the rest of the places on the internet. Almost every (non-troll) online community that is relatively peaceful and has some semblance of moderation to remove flamewars thinks of itself as "the best community". Usually as compared to reddit, though if it's on reddit they will…
How does that go without saying? Name some others then, compare and contrast. As-is your argument is just posturing.
It would be a nice feature if hackernews had a simple news.ycombinator.com/status page that I could trust. I don't like loading those some-sketchy-domain/status-right-now sites.
> news.ycombinator.com/status page That's not so useful when news.ycombinator.com is having problems.
Maybe ycombinator does have an official status page somewhere, but it is not easy to find if that is the case.
Earlier quoted context omitted.
How does this happen? Not the person you are asking. Bot operators have an incentive to make crawlers look as much like a human as possible so they do not get blocked. Some of them fail miserably and some nearly succeed. That makes it trivial to accidentally block a real person. I am personally fine with that given I do not pay for this site and have no SLA or contract with it.
some humans also try their best to make themselves look like bots...