@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.
