@johnsonjohnson said in Which is better NodeBB or Discourse?:
@gotwf's claim that Ruby on Rails is somehow history is absolute nonsense. So is the claim that it's somehow hard to customize and scale.
Most people who make such claims have no idea what Rails actually is. They've never used it, or at least never developed anything substantial with it. In addition they've often spent most of their lives learning something else and is therefore reluctant to vouch for anything new regardless of what it is.
@gotwf said in Which is better NodeBB or Discourse?:
.... bunches o' snippage....
Rails vs. NodeJS: Are you kidding? Was an early adopter of Rails back, circa 2003/4 or so? It rocked at that time as an alternative to then php stuff sporting the serious security hole of the day/week. Or so it seemed - php was pretty sketchy for a while there. Fast forward a decade and a half and it's freakin' no contest! Rails is all but history/legacy, at least in my mind.
Pretty sure I was using RAILS before most people hereabouts. Used to own the first edition of "the pick axe book" before some asshat "borrowed" it from my cube and never returned. That was copyrighted 2004 and I'd been using ROR for at least several months prior. It was a dandy alternative to the php security hole of the week. Fast forward to more modern times and I'd prefer to use else. But then I have also not used ROR in a decade so.... my impression may well be outdated.
But whatever. The above was an opinion. Your mileage may vary.
But it is cool that you feel passionate enough about ROR to create an account to post a rebuttal to something I posted nearly a year prior. So, @johnsonjohnson, welcome to NodeBB. You've tried the rest and found the best (TM)
P.S.; Even recounting that history has me pissed off again because they also stole my first edition copy of "The Pragmatic Programmer". Never replaced either. Fsck'ing hate thieves.
It's been several months since our Toronto team has convened in our downtown office, and we've blogged previously about how we are spending our free time during social distancing. But of course that DOES NOT mean the team hasn't been working hard. Version 1.14.0 includes expanded documentation and improved features, as well as streamlining and security fixes. Here are some highlights...
Click here to see the full blog post
As outlined in the second part to this post here - I have created this dedicated topic for the purposes of pitching this new feature and functionality for composer.
A composer that can align in one click to the right of the screen - creating a split view.
I guess if people want left they can have it but the concept is being able to easily reference posts on the right and compose on the left, keeping an unobstructed view of the entire flow of the topic posts without having to minimize the compose editor.
Meet the new contextual button that would toggle between positions.
Click to toggle horizontal position:
Click to toggle right-aligned position (split view):
As an evolution of composer core feature & function, I believe the case for, is incredibly self evident.
I'm waiting for someone to tell me this feature is already available...
I will edit an addition this OP with summary points and extra info if required.
Please Upvote - If you want to see this as a core feature in standard nodeBB deployment.
I would imagine you would add what @baris mentioned in here:
if user is member of the poster set, return content as is
@PitaJ said in Integration with Canny.io:
action:ajaxify.end is the hook you're looking for.
I had tried ajaxify.end many times. But missed the fact that I can't run console.log like that, I had to put it in a callback function and it worked great. Thanks for pushing me to this direction again!
Whoever it is, it's not us... as @pitaj suggests it could be bots issuing HEAD requests to determine site availability before crawling? Who knows... I am looking at some of them coming in our logging system now, but they have no user agent either, so
Related Github issues:
PostMidnight created this issue in NodeBB/NodeBB
djensen47 created this issue in NodeBB/NodeBB
Allow weekly email digest to be resumed
Thanks @julian, that solved that issue.
Additional details. The problem may be the way that I have my S3 content bucket locked down such that my dev forum cannot access the files (different subdomain).
Pika is a persistent huge storage service , compatible with the vast majority of redis interfaces (details), including string, hash, list, zset, set and management interfaces. With the huge amount of data stored, redis may suffer for a capacity bottleneck, and pika was born for solving it. Except huge storage capacity, pika also support master-slave mode by slaveof command, including full and partial synchronization.
@Mukkamala-Akhil said in Please let us know whether NodeBB will be actively maintained as Enterprise Grade Community Software. ?:
@scottalanmiller said in Please let us know whether NodeBB will be actively maintained as Enterprise Grade Community Software. ?:
Not rude, just wondering why you were tagging me for input for plugin requests. I'm a pretty random person to have asked to respond about them.
Cos, You replied to my previous thread. So I thought you'll be throwing some light about NodeBB.
Sure, but your questions were about feature requests. Your original question was about when NodeBB would be enterprise maintained, and that was easy to answer... five years ago and continuously since then. It's absolutely enterprise ready now.
Your next set of questions weren't really questions, but just mentions of features specific for you that you'd like someone to develop. There wasn't really a question to answer there, it's just a note that you'd like to see those features. Not much that I, as a long time user, can say about those.
I can shed light on the usual paths... you can make a thread requesting them (one thread each or no one will notice), but unless they get loads of traction, there is no reason to assume that NodeBB will even consider that - that's not how the core system works. You can hope that others want them too and that someone third party makes a plugin for you to use, but if that is going to happen it is most likely to have already happened. You can offer a bounty on the plugins. Or you can hire either NodeBB themselves or a third party to make plugins. That's easy to do, but expensive.
Other than that, I'm just an end user like you, but not one that wants those features so am glad that NodeBB is not focusing on them.
The reason that no one responded to that particular post is because, if you read it, there isn't a question - nothing that would warrant a response. So I had read it, but it just seemed like you were mentioning a wish list. Which would make no sense for me to respond to since you weren't wishing it from me.