Works for me. Or better said, I just received the push notifications for replies to this post

Me plotting to take over the world.

Inbox didn't do much for me as I already have tons of filters set to label everything accordingly.

No multiple option makes fuzzmz

I usually use Sublime Text + Notepad++ as my regular script editor/general text editor, then Eclipse for my Java needs, then PyCharm for Python, and currently trying CLion for my C/C++ pieces of code.

Just as a general rant, I don't really like the Universal SSL idea. The whole point of SSL is that each site in particular can be trusted (or not); with U-SSL, in theory, if you manage to spoof a certificate then you can spoof any site using universal SSL.

From what I know, the whole point of the Universal SSL from Cloudflare is that you don't need your own certificate. It just takes a while to activate that option on an account.

Not sure how it works with nginx, but with my own certificate I just had to configure nginx to use my cert, then redirect all links to https and preferably re-run the setup so you set the forum url starting with https.

Need anyone doing Romanian translation? I could lend a hand there.

@a_5mith, correct me if I'm wrong, but from what I understand from their Introducing GIFV blog post .gifv is a MP4 container and not a WebM one.

Basically they just use that wrapper to avoid having playback controls around the video.

I was actually thinking of something along those lines. Tempted to write a custom theme to use the forum as a blogging system (instead of Ghost, which I currently use) which would display threads as articles, where the first post in a thread is the post content, and all others that follow are comments to that post.

It's weird, I can't reproduce neither @hek's nor @Kacper-Domański's issues. I'm running 0.5.1 for what it's worth.

@a_5mith god damn it, need to pony up my commits or make some repos public :octocat:

Was just speaking to some friends about this and they were most excited about the free SSL cert, so I guess it wouldn't hurt to let people here know that you can get free SSL certificates from StartSSL.

Granted, they're not wildcard certificates (which means that they only work for the subdomain and master domain you register for), but you can get as many as you like, so there's no excuse not to

I haven't been getting any pushes either (and haven't changed my )

A free and really good alternative to the book mentioned by @mootzville is Git - Book. It teaches best practices, as well as providing both in depth information and quick reference.

@meetdilip it should be public instead of pulic. Sorry for the typo

@meetdilip said:

Restored using snapshotp and git status gave [...]

That just means that the public/google-adsense.config.json isn't being tracked by git (it isn't under source control). Most likely that file was added by some NodeBB plugin.

You can either add it to the git repo using git add pulic/google-adsense.config.json and then git commit -am "added adsense config file" and git push to update the remote repository, or ignore that message.

@meetdilip, open npm-shrinkwrap.json with a text editor and replace its content with the contents of this file.

After you've done that do a git add npm-shrinkwrap.json, git commit -am "updated files" and git push and things should be working.

@Scuzz, the main problem is that the issue hasn't been completely fixed. As far as I know the latest patch for bash 4.3 is 28 which makes things safer, but still not completely impenetrable.

Ok, I managed to get the comments plugin working by hacking around Ghost and the plugin itself.

Please note though that Ghost has changed the way the JSON output of a post query is formed, so the plugin can't work (even with auth) until it gets updated to account for that. I have opened #17 - Ghost post JSON changed breaking comment publish.

The hackish workaround implies modifying both Ghost so we can have public access to the posts API and we get back the format understood by the comments plugin, as well as modifying the plugin to use the new public API URL.

1. Hacking Ghost
   ==============

In order to expose the JSON post information we need to modify two files:

1. /core/server/api/posts.js
2. /core/server/routes/frontend.js

posts.js - find the read: function read(options) { block (it should start around line 72) and duplicate it making the following changes:

1. change the function declaration from read: function read(options) { to readN: function readN(options) {
2. change the return value from return {posts: [result.toJSON()]}; to return result.toJSON();

You can see how the change looks by going here. This will return the post info in JSON format which can then be consumed by the comments plugin.

frontend.js - the following changes must be made so the new API call we wrote in posts.js gets exposed without having to authenticate.

1. under the utils = require('../utils'), line at the begining of the file we must add api = require('../api'),
2. before return router; add router.get('/api/public/posts/:id', api.http(api.posts.readN));

How the file should look can be seen here. Now going to http://your_blog/api/public/posts/1 for example will show you the post information in JSON format even without being logged to the Ghost blog.

2. Modifying nodebb-plugin-blog-comments
   ===================================

We now must modify the comments plugin to use the new API we just created at step 1.

To do this we simply edit the /public/lib/embed.js file and change adminXHR.open('GET', '/ghost/api/v0.1/posts/' + articleID); to adminXHR.open('GET', '/api/public/posts/' + articleID);

The only change required is to update the embed code in the posts.hbs file to use embed.js instead of embed.min.js.

To do this we replace nbb.src = nodeBBURL + '/plugins/nodebb-plugin-blog-comments/lib/embed.min.js'; with nbb.src = nodeBBURL + '/plugins/nodebb-plugin-blog-comments/lib/embed.js';

And that's it, you should now have NodeBB comments running on your Ghost v0.5.x blog.