No, I think that is actually okay. In the emails we send out, we pass in day, week, or month depending on the digest. For the test email, the value alltime is sent in, purely so the digest is populated with something.
We just don't happen to have a language tag for alltime 
There's a rather distubing trend that I've noticed in recent years – sites take forever to load. It's a little distressing if only because our internet connections are getting faster, but on average (anecdotally) page speed metrics haven't changed much at all.
One would assume that faster internet would speed things up, but it hasn't panned out that way for a specific reason: site payloads are getting larger.
Click here to see the full blog post
In my experience there are few reasons to use a version manager, except for development reasons (i.e. testing on older versions of Node, etc.)
In production, I am increasingly in favour of compartmentalization via containers (or currently, simply separate servers). They can each maintain their own version of Node via the OS package manager, and that's that.
Ah, that's very unfortunate!
At this time, websockets are required for almost all of the write operations in NodeBB. That's due to change in v2, but that is a ways away yet.
Is there no way those IT administrators can allow for websockets to be whitelisted?
@gotwf It looks like AsciiDoc is something closer to a superset of Markdown, which can be more powerful in the right hands.
I will put plainly that the reason why Markdown was chosen was due to its simplicity and ease of use. I considered it an adequate balance between that and its potential to be an expressive markup language.
I will admit there are shortcomings, especially if you want to do some more esoteric formatting things like text alignment, colours, and so on, but that would be where AsciiDoc would shine, I think
Definitely worth supporting as the Markdown plugin itself is actually quite straightforward.
@olivedev Why don't you try to install it yourself? I published a little guide that helps you do just that
This forum is a good way to get help if you find yourself stuck somewhere.
Thanks @gotwf, nice to hear my thoughts echoed back.
I've been chasing this for some time now, with limited success. It all started when I went camping a couple hours north of Toronto, and didn't have any cell signal.
To my surprise, I had the most relaxing vacation I'd had in many years, simply because I was no longer connected to my work, emails, any responsibilities whatsoever. It was so liberating to plan only as far ahead as "what should I eat tonight", and "what should I do right now" 
Unfortunately, nowadays there is cell signal (or wifi) available everywhere, so it's much harder to achieve this organically
What is the Digital Sabbath? The premise is simple: To go without digital media for a whole day as a form of rest. The challenge then, is to go without digital technology one day a week for three months. How did I do, and what did I learn? Perhaps this is something you might want to take advantage of in your own life.
Just a heads up — today's blog post does not contain any technical write-ups or explanations, nor does it really related to NodeBB in any way, shape, or form. Journey onwards if you want to read my incoherent ramblings about technology &ndash or lack thereof.
Click here to see the full blog post
@glassdimly nice! Thanks for sharing 
NodeBB doesn't actually ship with any parsers in core. We bundle Markdown and it's enabled on all installs, but my original point was anyone can make an ASCIIdoc parser and replace Markdown, that's all
@gotwf for what it's worth, if you don't like Markdown you aren't tied to Markdown... You could always swap in an ASCIIdoc parser 
From the ACP, you can look at Advanced/Events, which contains an audit log of moderator/administrative actions.
What exactly are you trying to get loaded from Steam? If you log in via their OAuth2 endpoint, you should retrieve some data from steam which you can then save into the user hash. Is that the step you're stuck on?
To be honest, I've never really been able to get line breaks working with our markdown tables. So I am not sure if it is possible at this time 
@nibl hello there! We're actually running ghost 2.something, so I can't guarantee it'll work with Ghost 3.
We're probably going to upgrade Ghost at some point, and the blog comments plugin will be upgraded with it.
@greenmoon Appreciate the feedback! I should mention that the impetus for us cutting these features isn't to say that they're useless, or that we're giving up on them, but only that their usefulness in core was overestimated when initially added.
For users like yourself and your community, you may continue to find benefit in these features like the taskbar and sounds... there's no reason they cannot still exist as a plugin.
I'll consider moving sounds over to a plugin so they can continue to work
Re: taskbar – I still personally do see benefit in minimizing the composer (especially on mobile), in cases where I wish to read the thread some more. We'll likely come up with some sort of alternative UI for this. It might end up looking much like the taskbar, but it wouldn't be a separate subsystem, but somthing bespoke to the composer itself.
The taskbar as an experiment as an extensible module wasn't worth it in hindsight, that is all 
@oplik0 The taskbar doesn't much look like a taskbar in Persona, but in Vanilla, it is a little more "start bar"-like
We definitely didn't want to cut anything useful, unless we had a really good reason to do so... but yes, in short, that is a fairly succinct tl;dr for my blog post 
Without hesitation, I'd say that NodeBB has evolved heavily over the past 7 years.
The initial drive those first years was feature parity – bring features to NodeBB that other forums have, and that users expect. After all, how could we sell ourselves as a forum if we didn't have, say... user accounts... or password changing utilities?
The benefit are plain to see – it's easy to see what works, and years (if not decades) of user testing has surfaced certain UX patterns that have stood the test of time. For example, the category/subcategory hierarchy, or the use of tags to link disparate items together under a common label, etc.
Click here to see the full blog post
NodeBB has been production ready for a couple years now you can clone the stable version by appending -b 1.13.x to your git clone command
Hello @sharonyue, this guide is actually meant for installation with MongoDB as the data store, so redis is not necessary however you may use it if you wish.
The chris-lea PPA is no longer necessary on 18.04
Are you using an external emailer plugin, or just the one defined in the admin panel? I don't think the limiter settings apply if you're using a separate plugin for sending emails.