@Panda because there is no match for the DNS entry specified. The receiving web server parses the headers looking for a destination hostname to match, and anything the web server is unable to resolve will be sent back to the root.
@Panda you’d be surprised. If you consider that you’d need to use the API to be able to populate a WordPress widget for example (which in turn would of course be PHP), taking this route is still immensely popular.
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.
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.
I got hit with this today. As I have a Pro subscription to Font Awesome, this allows me to use a much wider range of fonts. Unfortunately, NodeBB only seems to list the free fonts, so in order to use the Pro icons, you have to manually type the font name you want (leave the fa- part off, as it’s not needed).
No issues, so I went ahead and typed in the name. Below is the result
Now, despite the icon not showing here, it does once you save and reload the site. Great - problem solved then?
Yes - until you want to change the icon back…
Highlight over an unchanged icon, and you’ll see the mouse pointer change meaning there is a link behind it
However, hover over one you’ve changed by typing in the value manually, and you’ll see the link is gone
Panic stations… headless chicken… major cussing session… No - there is a way out
Fire up the dev tools (F12 for console), and press the select tool. Now select the element with the missing link
In the resultant element list, follow the HTML until you reach
Now delete the hidden part, so you are left with just change-icon-link and press enter
You’ll see that the alt text appears for the image, which is enough for you to be able to click the anchor, and change the icon
There you go. Now enjoy how smug you feel that you’ve sorted this problem yourself 🙂
@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
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.
@Panda Just circling back here with something of an update (which I think you’ll like). I’ve completely restructured the ranking system. There are now less ranks, with a higher point threshold to reach them.
More importantly, if you reload the site, you’ll notice that the ranks are now icons.
I also removed the “Author” badge, and made this a single icon, which (to me) looks much better.
Ah, got it working!
I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters.
So made the new fork title longer and button responded.