we can have progressive web application in Nodebb
There is already a thread on the same
+1 for a Twitter like Notification Feed
This is definitley better I kinda like NodeBB extremley
Alright, feedback received
You know i really like to try nodebb unfortunately it doesn't have installation based on docker for easy upgrades.
Since i failed at installing nodebb via digitalocean and successfully installing discourse following the beginner docker guide -> +1 discourse
Any up-to-date tutorial for newbie non developer hobbyist to install nodebb on digitalocean?
The site that holds the digitalocean step by step tutorial seems to be down, but may be temporarily since is owned by @psychobunny . I think theres docker support too for nodeb now.
Weird upvote button should be at the bottom and bigger.. what if it is a long post.
Also will be cool when i'm composing a reply,i can view the thread as well - discourse style
@Nur On desktops, you can view the thread Just click the taskbar button to minimise the composer.
here's some small addition to what I want to see for nodebb that I liked from discourse.
although I am not sure if this has already been implemnted here on nodebb via plugin or core features
so far those are the things I think missing as far as I used the discourse for a couple of months and now migrating to nodebb
I spent more time messing with Discourse, this is my impression of the two so far:
What I liked most in NodeBB so far:
What I like in Discourse and didn't find in NodeBB:
For what it's worth, I ended up going with NodeBB.
Node + MongoDB (or Redis) just makes life so much easier than Rails. The plugin system here is great. I have no regrets I think what this team has done is awesome!
So for me it's solved. NodeBB is better.
@djensen47 Thanks for the kind words, always love hearing about converts from all sorts of forum software
I hope I don't get accused of super bumping multiple threads tonight (really not so old threads or well not so old last post!)
On first impression, nodeBB was the ticket - without any of the technicals. It's all that matters.
It truly is all that matters. Since the majority of fourm users are not going to be technical and forum have there work cut out to drag people away from the twitters and face books of the world.
A forum can be deployed to any user base so it's application and audience is potentially as wide as you like and varied as you like, that you have to think about simple but not dumb Ui/UX and rely on the beauty of tradition, i.e. established and solid universal conventions that are universal but not afraid to push the envelope to enhance convention to the point it's at least feels innovate if not actually is.
It's silky response. The fade out fade in transition was a genius choice, let me type that again GENIUS!
The composer is the window to all content creation, the crucible of an entire forums everyday lifeforce. It's got to be good, it's got to always be trying to be better, by trying to be great. This is the interface that makes or breaks the user experience and thus a forum.
My UI/UX 2c:
Please consider making the composers upper top line a drag focus draggable area so it is not restricted to the black circle aligned to the left, that should really be centered (it took me too long to figure out) - it breaks a basic UI/UX expectation burned into our retinas at this point!
Thanks for the kind words, we strive to keep NodeBB minimal and fast, and I feel we're keeping up with trends. Of course, what's in style always seems to pass too quickly
With regards to the composer resize, there's no particular reason it has to be limited to the resizer button, I'll look into it
One thing to add to the list is the lack of reliability of sending the digest email to a moderate or larger user base. I have 12,000 users and have successfully sent 7/20 digest emails.
To the teams credit, one issue related to this has been resolved. Thank you for that.
Today, however, NodeBB ran out of memory. It appears this while it was getting ready to send the digest. The server crashed and the digest was not sent. The smallest error happens related or unrelated to the digest and it just doesn't start nor finish. And there is no way to resume or resend to those who did not receive it. The solution? Wait a week or wait until the "underlying issue" is resolved.
Update, possibly irrelevant:
The team does not believe this to be an resolvable (nor important enough) issue so it will not be resolved. (That's an opinion and their decision and that's fine). If you're looking for reliable weekly digest, you need to seriously consider something else besides NodeBB. I don't want this to be true but it just isn't a priority for them. (Development teams have a lot of issues pulling them in different directions; so you have to set some sort of priorities and some things get left out, this just happens to be one of them.)
I don't know if Discourse is better on this point but I am on a few Discourse forums that definitely have 10s of thousands of members and I get the email every week.
For the first time reader of all of this, it is important to note that despite the digest email issue, the team is super responsive and receptive to every other issue. Especially when it is a well defined problem, the team turns around very quickly. I've logged a ton of bugs and nearly all of them get fixed and nearly all within a week of reporting. Priorities are priorities and this might be occurrence problem.
What sending mechanism are you using? Local SMTP? A service? We use MailGun and haven't seen an issue yet.
The out of memory may have been an independent issue. We use Sparkpost (as mentioned in the other thread).
Gotcha. Haven't used Sparkpost, don't know how they are. That would make sense if the memory was a different issue.