3 ms·

It'd be hitting Firebase, not HN.

• kbenson 11y ago
  Which is a distinction I don't think really matters. They have an agreement, and firebase provides the API, but that agreement could become strained or need to be renegotiated if there's a feeling that the HN API is taking more resources than it's worth, or if HN pays directly for usage, then we're back at it affecting HN again. Ultimately, the bits we consume aren't free. Someone pays for them, it just commonly not the consumer in the current model. At the point where you make the person that is paying for them feel it, then the person who pays might end up shifting to you. Or the resource goes away, and everyone loses. I'm not saying that's likely in this case, but even if it isn't likely, doesn't mean we shouldn't think about it.