Skip to content
Sudonix

NodeBB v4.0.0 — Federate good times, come on!

World
94 64 20.4k
Log in to reply

Related Topics
  • DownPWundefined

    Tutorial : NodeBB Scaling-clustering Redis + Proxied Cloudflare Free plan : integration guide

    Performance nodebb scaling redis cloudflare socket.io
    3
    4 Votes
    3 Posts
    967 Views
    crazycellsundefined
    thanks @DownPW ! this is definitely very helpful.
  • phenomlabundefined

    Export posts out of NodeBB into HTML and Markdown flat files -> Halo ITSM

    Guides nodebb python
    1
    3 Votes
    1 Posts
    854 Views
    No one has replied
  • crazycellsundefined

    "most votes" ranking option is not respecting the plugin

    Bugs nodebb
    5
    1
    3 Votes
    5 Posts
    1k Views
    phenomlabundefined
    @crazycells Agreed. It takes a more sensible approach. Nobody ever upvotes the first post - it’s usually much further down as the conversation progresses.
  • ahmedundefined

    nodebb error logs

    Bugs nodebb
    6
    2
    4 Votes
    6 Posts
    2k Views
    ahmedundefined
    I just wanted to ask because I don’t have much knowledge about the new installation. Thank you for the explanatory answer.
  • Pandaundefined

    Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    phenomlabundefined
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • cagatayundefined

    NodeBB v3 Chat Very Slow

    Moved Performance nodebb v3 nodebb chat
    47
    11 Votes
    47 Posts
    17k Views
    phenomlabundefined
    @DownPW Seems fine.
  • Pandaundefined

    NodeBB inline videoplayer

    Solved Customisation nodebb
    12
    3 Votes
    12 Posts
    4k Views
    Pandaundefined
    @phenomlab YAY! It works Thanks so much
  • crazycellsundefined

    fading in /tags page

    Solved Customisation nodebb
    32
    1
    30 Votes
    32 Posts
    11k Views
    DownPWundefined
    Fix working perfectly