Skip to content

what is the reason for choosing node BB over flarum?

Solved Performance
  • @phenomlab SEO extension does not do deal with canonical URLs for flarum core.

    flarum core sets 10 or 20 posts into a group and they add ?page=1 as the 20th post canonical URL

    31b6dae0-8eb7-4cf1-9893-1a8b9704f26c-image.png

    when I took this to askvortsov. he said if something can be done with an extension it has to be done with an extension and we donā€™t change the core, i was shocked by reading this.

    clark also responded in the same manner (Iā€™m sure he is not into SEO) google says you should not have multiple pages with same title otherwise bot will get confused to give ranking.

    imagine if someone searches for what is the difference between nodebb and flarum and google shows /24 th post as the first result? user will not understand anything until he scrolls up

    https://discuss.flarum.org/d/28600-understanding-canonical-urls-of-flarum-posts/

    i donā€™t want to talk about this further, it is not good to discuss the flarum flaws without their presence. hope they will realise the SEO part soon!

    we will continue using flarum for the next 5years

    on the other hand if get budget we will be switching to WordPress (gatsby + wpdiscuz with graphql)

  • @hari does your forum currently have many posts and users?

  • @jac Yes, i would not be able to share my domain since Iā€™ve singed a non disclosure agreement with my organization

    82b0bab8-cc10-4765-b578-6e2e4d91e4bf-image.png

    we do deal with my posts every day, I have a great bonding with flarum šŸ˜›

  • @hari said in what is the reason for choosing node BB over flarum?:

    i donā€™t want to talk about this further, it is not good to discuss the flarum flaws without their presence. hope they will realise the SEO part soon!

    And in the same sense, this site was not created to bash Flarum in any way. It was borne out of a lack of fundamental basics in Flarum that require a shed load of extensions to gain the required experience, where in contrast, NodeBB has all I need out of the box.

  • @hari Wow, very good stats šŸ˜. I was going to suggest moving to NodeBB would be a simplier option if having trouble with flarum although it seems moving isnā€™t an option with that may users / posts.

  • @phenomlab said in what is the reason for choosing node BB over flarum?:

    @hari said in what is the reason for choosing node BB over flarum?:

    i donā€™t want to talk about this further, it is not good to discuss the flarum flaws without their presence. hope they will realise the SEO part soon!

    And in the same sense, this site was not created to bash Flarum in any way. It was borne out of a lack of fundamental basics in Flarum that require a shed load of extensions to gain the required experience, where in contrast, NodeBB has all I need out of the box.

    Absolutely, although by the same token forums like this simply work because weā€™re all here to gather advice and find solutions to our tech issues we face, Iā€™d say opinions are welcome Iā€™m not speaking for the platform Iā€™m generally saying itā€™s good to have an opinion on something and for us it started with Flarum and quite frankly thatā€™s why weā€™re here because weā€™ve used Markā€™s services before.

    What Iā€™m trying to say is discussions and opinions are mostly healthy šŸ˜†.

  • @jac a year ago we devloped a WordPress flarum like theme to switch to (Wordpress + wpdiscuss)

    everything works perfect but the page size is ending up around 5mb and load time suks. (do not laugh at me šŸ˜› )

    recently we explored gatsby and graphql, wpgraph ql now supports wp comments ā€¦ if gatsby can generate a static page of WordPress comments in future we will switch to it.

    recently bbpress got graphql support too.

    using gatsby someone may build good static forum. it will be a great experience with Yet another related post plugin and a static page šŸ˜ lets see wp graph ql need to grow

    google loves related posts and too many links in a page.

    and each discussion page should have more content in a way related posts work as content too. quora does this a lot.

    even if qoura has 1000 posts they donā€™t change URL (like nodeBB or discourse)

    cdd0a2ff-1a87-4775-a670-2d9bfcc33fd6-image.png

  • @hari said in what is the reason for choosing node BB over flarum?:

    a year ago we devloped a WordPress flarum like theme to switch to (Wordpress + wpdiscuss)

    Sounds interesting! I used to mainly run wordpress sites but havenā€™t done for a few years properly anyway.

    Forgive me if Iā€™m wrong but are you looking for a solution away from Flarum?

  • @jac said in what is the reason for choosing node BB over flarum?:

    Forgive me if Iā€™m wrong but are you looking for a solution away from Flarum?

    we will continue to use flarum for existing forums.

    in future, we will plan something with wp graphql & gatsby

    static site with a commentator that would be good enough for our needs.

    we may close resignations on current flarums and redirect new users to the wp graphql powered forum. old installations will act as archives not sure.

    no thoughts for next 1-2 years

  • @hari said in what is the reason for choosing node BB over flarum?:

    @jac said in what is the reason for choosing node BB over flarum?:

    Forgive me if Iā€™m wrong but are you looking for a solution away from Flarum?

    we will continue to use flarum for existing forums.

    in future, we will plan something with wp graphql & gatsby

    static site with a commentator that would be good enough for our needs.

    we may close resignations on current flarums and redirect new users to the wp graphql powered forum. old installations will act as archives not sure.

    no thoughts for next 1-2 years

    It sounds like you have a clear goal, flarum isz a good option and if it irons out its issues it could be big.

    Personally if your project with WordPress and flarum donā€™t go fo plan to id definitely say go for Nodebb as a solid choice.

  • @jac @Hari my thoughts around this are that with any platform - be that WordPress, Flarum, or NodeBB, there is an inevitable ā€œlock inā€ - very much like Hotel California (ā€œyou can check out any time you like, but you can never leaveā€).

    What I mean by this is that you are buying into an ecosystem that offers no easy or readily available path out. If you plan to stay for the long term and there is a clear progression path from that project meaning itā€™s a viable route, then great.

    However, all of these platforms (except WordPress perhaps) have a way of ingesting data from other sources, but little to no way at all of taking that data somewhere else. This is nothing against any of those platforms, but the fundamental issue here is that whilst itā€™s probably easy to move into another product, itā€™s a different story altogether when you want to leave and take your data with you.

    Most FOSS based platforms can realise this and make money out of migrations. I know for certain that wpForo does this, and I also know that itā€™s something that one of the developers at Flarum has been touting for some time.

  • phenomlabundefined phenomlab referenced this topic on
  • phenomlabundefined phenomlab referenced this topic on
  • phenomlabundefined phenomlab referenced this topic on

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation šŸ’—

Related Topics
  • 0 Votes
    1 Posts
    744 Views
    No one has replied
  • NodeBB socket with CloudFlare

    Unsolved Performance
    23
    1 Votes
    23 Posts
    2k Views

    @DownPW itā€™s your only realistic option at this stage.

  • error with v3 in browser console

    Solved Performance
    4
    0 Votes
    4 Posts
    237 Views

    @DownPW itā€™s in relation to the response I provided above

  • Coding question: fetch vs $.ajax call from Shopify

    Solved Performance
    4
    3 Votes
    4 Posts
    258 Views

    @Panda You should be able to use {% javscript %} as shown in this video - itā€™s quite the watch, but very educational, and provides insight as to how this works - see below screenshot for an example

    cdb160e9-d955-498c-b921-982db2986e2b-image.png

  • SEO and Nodebb

    Performance
    2
    2 Votes
    2 Posts
    323 Views

    @Panda Itā€™s the best itā€™s ever been to be honest. Iā€™ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example

    https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1

    However, this was not without significant effort on my part once Iā€™d migrated from COM to ORG - see below posts

    https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365

    And also

    https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164

    It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and itā€™s essentially going to boil down to one thing - ā€œcontentā€.

    Googleā€™s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.

  • NodeBB v3 Chat Very Slow

    Moved Performance
    47
    11 Votes
    47 Posts
    4k Views

    @DownPW Seems fine.

  • build nodebb Warning in entrypoint size limit

    Solved Performance
    2
    0 Votes
    2 Posts
    218 Views

    @eeeee they are nothing to worry about, and can be ignored.

  • NODEBB: Nginx error performance & High CPU

    Solved Performance
    69
    14 Votes
    69 Posts
    6k Views

    @phenomlab

    Seems to be better with some scaling fix for redis on redis.conf. I havenā€™t seen the message yet since the changes I made

    # I increase it to the value of /proc/sys/net/core/somaxconn tcp-backlog 4096 # I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! #save 900 1 #save 300 10 #save 60 10000

    If you have other Redis optimizations. I take all your advice

    https://severalnines.com/blog/performance-tuning-redis/