Meta tags with 'og' support ?

Unsolved General Discussion
  • Hello

    Was wondering about how to support open-graph og meta tags, while posting url's

    In facebook, whatsapp etc, when a url is pasted in composer, it automatically pulls/displays title, image etc.

    How can I do that in nodebb ?

    Thanks in advance !

Suggested Topics

  • 0 Votes
    2 Posts

    Thanks for asking this question. i am thinking the same. if you got any solution kindly please reply me here.

  • 0 Votes
    1 Posts

    Any idea how to achieve this by CSS or script in nodebb ACP?

    link :

    you can easily check the source code of it, here I copy it in below

    <!DOCTYPE html> <html> <head> <title>MathJax Dynamic Math Test Page</title> <!-- Copyright (c) 2010-2015 The MathJax Consortium --> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <script type="text/javascript" src="../MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script> <style> input {margin-top: .7em} .output { border: 1px solid black; padding: 1em; width: auto; position: absolute; top: 0; left: 2em; min-width: 20em; } .box {position: relative} </style> </head> <body> <script> // // Use a closure to hide the local variables from the // global namespace // (function () { var QUEUE = MathJax.Hub.queue; // shorthand for the queue var math = null, box = null; // the element jax for the math output, and the box it's in // // Hide and show the box (so it doesn't flicker as much) // var HIDEBOX = function () { = "hidden"} var SHOWBOX = function () { = "visible"} // // Get the element jax when MathJax has produced it. // QUEUE.Push(function () { math = MathJax.Hub.getAllJax("MathOutput")[0]; box = document.getElementById("box"); SHOWBOX(); // box is initially hidden so the braces don't show }); // // The onchange event handler that typesets the math entered // by the user. Hide the box, then typeset, then show it again // so we don't see a flash as the math is cleared and replaced. // window.UpdateMath = function (TeX) { QUEUE.Push(HIDEBOX,["Text",math,"\\displaystyle{"+TeX+"}"],SHOWBOX); } })(); </script> <p> Type some \(\rm\TeX\) code and press RETURN:<br /> <input id="MathInput" size="80" onchange="UpdateMath(this.value)" /> </p> <p>You typed:</p> <div class="box" id="box" style="visibility:hidden"> <div id="MathOutput" class="output">$${}$$</div> </div> <script> // // IE doesn't fire onchange events for RETURN, so // use onkeypress to do a blur (and refocus) to // force the onchange to occur // if (MathJax.Hub.Browser.isMSIE) { MathInput.onkeypress = function () { if (window.event && window.event.keyCode === 13) {this.blur(); this.focus()} } } </script> </body> </html>
  • 0 Votes
    8 Posts

    Feedback: Two days later, I'm totally in love with VSCode. It's really awesome and it made my life a lot easier! Thanks guys!

  • Support webm format

    General Discussion
    0 Votes
    2 Posts

    WebM Embed Plugin

    Forget about WebM. GIF's are where it's at:


    NodeBB Community (

    This perhaps?

  • 0 Votes
    1 Posts

    While browsing the 'net, I found a neat little IETF draft standard called JWT (JSON Web Tokens).

    Basically, the idea is that instead of having sessions on the server and a cookie to match a HTTP request to one of those sessions, one or more claims (i.e. user ID or admin status) are stored in a JSON object which is then signed by the server. (currently through either HMAC, RSA or ECDSA)
    The client then stores this in usually either localStorage or sessionStorage and sends it along in an HTTP header with any request requiring authorization.

    For example:

    client logs in with username "Example" and password "password" server if user and password match, issue a JWT containing the payload { 'userId': 47 } and send it to the client client stores the JWT in sessionStorage (later) client creates a new topic and sends the JWT along in the Authorization HTTP header server validates the signature in the JWT from the Authorization header with their own secret/key and if it's OK, uses the data from the JWT in the processing of the request
    (in this case, the userID of 47 is used as creator of the topic)

    Pros of JWT:

    The server doesn't need to store sessions!
    => less load on the server
    & no shared session store is needed when scaling horizontally as long as all instances share a secret or public/private keypair No cookies => no CSRF!


    XSS becomes more dangerous - any malicious script with access to the client's localStorage or sessionStorage for a site can fully impersonate the user until the token expires or is deletes

    There might be more cons & pros, I am neither good nor experienced enough to fully understand everything 😛

    ("everything" is a lot though, I do have trouble with way less than that 😒 anyway, don't take my words for granted, do your own research, etc. etc. you know the drill 😛 )

    Some links:

    General introduction: Slightly more detailed introduction with INFOGRAPHICS(ish): Web-based token decoder: Express middleware: