shaunpersad

Not at the moment, no. But that would be a great addition. Thanks for the suggestion!

Similar benefits to most hosted commenting solutions, most of which have to do with scale in one form or another. If you're a small blog who gets a handful of comments a month, you might not see as big a benefit (though, there are still some).

- Decreased server load.

- Reliable multi-region storage and delivery.

- More login options.

- One login account across several websites, which decreases friction whilst still providing the safety of having comments from verified users.

- Moderation filters that can act based on past user behavior, before they ever interact with your site.

Yeah, it's been the #1 requested feature so far. It's in progress!

I'm a fan! Same goal, different execution :)

Hi Everyone! I'm the maker of CommentBox.io. Many of us who have built blogs in the past have at least considered Disqus or Facebook Comments as their commenting system. Their ubiquity is unquestioned, and the free price can't be beat. But we're giving up trillions of data-points about us in return, strengthening their data-mining, ad-serving machines.

What if providing a great hosted commenting platform was the only goal, and didn't come with strings attached? I built CommentBox.io because I wanted to give users an alternative, and I hope you like it!

I love finding obscure APIs. Here's the Campbells Soup one: https://developer.campbellskitchen.com/

I found these articles from the Mozilla blog to be very helpful: https://hacks.mozilla.org/category/es6-in-depth/

The articles are in reverse order, so you'll have to go to page 2 to get to the intro.

I don't get why Lambda gets all the love while Google Cloud Functions doesn't.

I've tried both, and GCF is vastly superior in many ways.

1) Developer experience is pretty terrible in Lambda, whereas GCF is compatible with Express.js to the point where you can simply pass in an Express app instance to it (which makes vendor lock-in a moot point as well). Develop your app more or less like you normally would, and just export it to GCF. Job done.

2) Deploying is a simple cli command away, even with native binaries.

3) No API Gateway necessary for HTTP functions.

4) It's now compatible with Cloud SQL so you don't have to give up your traditional database.

5) No crazy IAM permissions hoops to jump through to get anything to work.

Disclaimer: I'm not affiliated with Google.

I can't say enough good things about Firebase and GCP in general, but I'm always cautious when using Firestore in particular. I usually avoid unbounded queries altogether, and treat it primarily as a key/value store to get by id.

When I do use queries, it's always in places where the results have a well-defined limit (usually limit = 1), e.g. finding the most recent X or the highest X.

With the above two, you get all the greatness of Firestore, but with a well-defined (low) cost that you can calculate ahead of time.

It might have something to do with the fact that their script tag that encompasses the console.log is outside of the body tag.

> Does Netflix want their shows accused of glorifying murder?

There are plenty of Netflix shows that glorify murder already. The Punisher comes to mind.

That "immature" community you speak of is one of the best parts of IH. As someone who joined IH and the maker community in general last year, there are few other places that I turned to beforehand to get basic and/or "dumb" questions answered about entrepreneurship. Hacker News is far too elite for that kind of environment.

For me, it's a place to feel "safe" to ask questions that might get ridiculed or passed on elsewhere. It's not just about the informative podcasts and interviews, but also about being around people who have the same goals as you, but are at different stages. It just so happens that many of us are at the beginning. And there's nothing wrong with that. We're all learning together!

How does this compare to CockroachDB (performance-wise and availability-wise)?

You would need to remember the state of the turnstile when someone attempts to go through it. If it's locked, you can't pass. If it's unlocked, you can.

Whether or not this situation needs a "state machine" is debatable, but you do need to remember the state. In this case, a simple boolean "isLocked" could suffice.