HN user

jawr

347 karma
Posts16
Comments175
View on HN

Storing and streaming is an expensive model, and the subscription price is a premium in the majority of the world. It’s actually impressive that so much content (both incredible and bad) is available, for “free” to so many.

I’m an ideal world there would be no ads, but we don’t live in one.

If you have such disdain for ads you should probably pay the premium or not use YouTube.

It’s my understanding that Reddit video was PoC’d by one person using aws lambda.

Severless often gets touted as being the best way of doing things rather than just a way. My comment was a dig at that.

But it seems like my comment somehow exposes multiple levels of ignorance, would love to know what they all are!

That’s great if you’re the only person working on the code.

Not everyone is as diligent and not everyone will have thought through/remembered all those edge cases when they happen to end up maintaining/adding to your code.

Personally I find that tests are a great way to ensure all that hard work you did thinking about those edge cases isn’t wasted. That and manually testing stuff is annoying after the first time.

It’s only dropped if the relay/server sending it is not behaving nicely, otherwise it’s there in quarantine (spam) awaiting user signals to train it.

I think it’s such a typical mindset that people with very limited domain knowledge think that people with a lot more domain knowledge are just being stupid.

I think everyone always looks at it from the perspective of the hobby mailer, when instead gmail looks at it from the recipients point of view.

It’s really really trivial to automate buying a domain, get some IPs and setup DKIM, SPF and DMARC. How can a provider determine intent?

Gmails approach is to mostly use user signals, which in my opinion is the best way.

At a company I’ve worked for, they sent some mail using sendgrid to a poorly made mailing list and we’re in gmail spam for ages.

My personal ran email mostly stays in inbox.

Aren't a lot of endpoints essentially bound to the database anyway? If you were to do any sort of major schema change, chances are you would have to create a new endpoint (i.e. /api/v2/) to handle the new schema changes. Also this handles versioning.