Skip to content
Sudonix

Threaded post support for NodeBB

Let's Build It

Related Topics
  • phenomlabundefined

    Target the posts counter in categories using CSS and jQuery

    Let's Build It
    2
    3 Votes
    2 Posts
    117 Views
    DownPWundefined

    Very great 😉

  • phenomlabundefined

    Extended functions for Q&A NodeBB plugin

    Let's Build It
    3
    5 Votes
    3 Posts
    1k Views
    DownPWundefined

    Very good like always 😉

  • DownPWundefined

    Material View Support for Stock NodeBB

    Unsolved Let's Build It
    51
    15 Votes
    51 Posts
    3k Views
    DownPWundefined

    Oh yes, that’s what’s super cool, I learn something every day. Afterwards I start from so low in JS

  • phenomlabundefined

    Threaded chat support for NodeBB

    Let's Build It
    35
    19 Votes
    35 Posts
    2k Views
    phenomlabundefined

    @DownPW said in Threaded chat support for NodeBB:

    Better like this : add shadow and border-left on self answer

    Of course - you style to your own requirements and taste 🙂 I’ll commit that CSS we discussed yesterday also

  • Pandaundefined

    Nodebb design

    Solved General
    2
    1 Votes
    2 Posts
    296 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.

  • phenomlabundefined

    Setup OGProxy for use in NodeBB

    Moved Let's Build It
    110
    21 Votes
    110 Posts
    11k Views
    phenomlabundefined

    @crazycells said in Setup OGProxy for use in NodeBB:

    are they cached for each user separately?

    No. It’s a shared cache

    @crazycells said in Setup OGProxy for use in NodeBB:

    additionally, this is also handling youtube videos etc, right?

    No. This is handled by nodebb-plugin-ns-embed

  • phenomlabundefined

    Setting up a beta NodeBB v3 environment

    Moved Let's Build It
    14
    11 Votes
    14 Posts
    878 Views
    phenomlabundefined

    @dave1904 excellent news. Thanks for the feedback

  • JACundefined

    Display tweets in widget [NodeBB]

    Solved Customisation
    29
    4 Votes
    29 Posts
    3k Views
    JACundefined

    @phenomlab brilliant, many thanks Mark 😁