The current sentiment among developers is content ownership. By posting on dev.to, you are giving away your content for free. If tomorrow they shut down or paywall your content (like Medium), you have no other option. On the other hand, Hashnode offers something called Devblog (https://hashnode.com/devblog) using which you can host your blog on your domain and truly own your data. Plus you get the other benefits of Hashnode. So, the correct approach IMO is to publish your blog posts on your own domain first (using Hashnode's devblog) and then republish them on other platforms. This way you retain control of SEO and truly own your content while getting benefits and exposure of other platforms. You can read this related thread: https://hashnode.com/post/devto-or-hashnode-cjvrpqr24003435s1sakrb3gi#cjvuil135000y8cs11l5cm7et Never give away your content for free!!!

Can you login to your account and try setting Verify user emails to true? Exact Path = Account -> App Settings -> Hosting and Emails -> Email Settings

Thanks a bunch Justin! Quick question - Is it recommended to have an arbiter if we have a 3 member replica set with one primary and two secondaries?

Passport gives you two hooks where you get to tell it how to serialise/deserialize a user. Basically, you will do something like this : passport.serializeUser(function(user, callback) { callback(null, user.id); //You will store the id in session }); passport.deserializeUser(function(id, callback) { var query = 'SELECT * FROM user_profiles WHERE id=?'; client.execute(query, function(err, result) { callback(null,result.rows[0]); //Now we populate whole user using the id }); }); P.S. The above code is untested and may not work. But it gives the basic idea about Passport integration. You can use Cassandra Node.js Driver for your DB operations. Passport makes no assumption about how and where you store the data. You can use all sorts of DBs here - MongoDB, Cassandra or MySQL.. The key is using serializeUser and deserializeUser and loading the user object from underlying data store. Passport Docs Let me know if you have any questions!

Thanks Denny! This was helpful. :-)

Providers like AWS and others generally offer discounts and this pricing seems very high for a startup or even small teams. The only time it makes sense is when you consider big IT players who are already spending tons of money on their infrastructure and are willing to move to Meteor. So, the answer is No, I won't pay $495 per month.

Great to know it's geared towards functional programming. :) Thanks for answering!

I am not sure. Just discovered and found it interesting. Haven't got a chance to test.

Here are a few things I dislike about Bootstrap framework : In my opinion Bootstrap is not semantic and the presentation is not separate from content. This makes scalability and maintenance more challenging. I use a framework to get started quickly. But in case of Bootstrap most of the times I end up overriding a lot of CSS rules to suit my needs. It would have been great if Bootstrap offered just the bare minimum CSS. Of course this is great for prototypes, but not very good for serious website development. The SaSS support just came recently with Bootstrap 4. The previous versions should have been on SaSS, IMO. You can say Bootstrap is a bit bloated if you consider the lines of code and file size. Apart from the file size the DOM produced by Bootstrap is also heavy. To fit your elements in simple grids you need to add a lot of markup, rows, columns etc. No easy upgrade. I can't upgrade one of my Bootstrap 2 projects to newer versions because of lack of backward compatibility. P.S. I still use Bootstrap for prototypes. For serious production apps I prefer vanilla CSS.

Yes. I am willing to upgrade to Bootstrap 4. I am not sure why you are not motivated enough, but I am super excited. Here are the reasons : Bootstrap now uses Sass instead of LESS. This means we, the Sass lovers, have a reason to rejoice and not to forget Bootstrap now runs faster than ever thanks to Libsass (the C implementation of the traditional Ruby Sass). The second thing I liked the most is the support for Flexbox. Now you have the option to choose Flexbox based grid system and honestly this is the future. All the JavaScript plugins have been rewritten to support ES6. This means you have better plugin support in Bootstrap 4 and can take advantage of the new ES6 features. I also noted that responsive typography is way easier in Bootstrap 4. This is because the new Bootstrap has moved from pixels to rem and em units, which is a good thing. As I speculated earlier, no more IE8 support. Hurray!!