Skip to content

Ghost for blogging vs long posts on nodeBB?

Announcements
4 3 2.0k 1
  • Re: New blog section added

    Reading this post, I get the feeling @phenomlab tried ghost, but went back to long-form nodebb posts. Is that the case?
    I also started blogging on ghost, but never got very far. The platform is… peculiar. They don’t implement comments, and using disquss is not a great idea if you care about privacy of your users. Then, the last thing that put me off is that they don’t even have versioning (you cannot go back to old versions of your posts). NodeBB has this! The editor, which should be the shinning star for Ghost, is one of those ‘block based’ Guttenberg clones, so not to my liking either. It could very well be that long-form nodebb posts are a better solution than Ghost?

    If so, very interesting, and congrats to Nodebb!

  • Re: New blog section added

    Reading this post, I get the feeling @phenomlab tried ghost, but went back to long-form nodebb posts. Is that the case?
    I also started blogging on ghost, but never got very far. The platform is… peculiar. They don’t implement comments, and using disquss is not a great idea if you care about privacy of your users. Then, the last thing that put me off is that they don’t even have versioning (you cannot go back to old versions of your posts). NodeBB has this! The editor, which should be the shinning star for Ghost, is one of those ‘block based’ Guttenberg clones, so not to my liking either. It could very well be that long-form nodebb posts are a better solution than Ghost?

    If so, very interesting, and congrats to Nodebb!

    @qwinter

    @qwinter said in Ghost for blogging vs long posts on nodeBB?:

    Reading this post, I get the feeling @phenomlab tried ghost, but went back to long-form nodebb posts. Is that the case?

    Yes, exactly that…

    @qwinter said in Ghost for blogging vs long posts on nodeBB?:

    The platform is… peculiar.

    That’s one way of putting it 🙂

    @qwinter said in Ghost for blogging vs long posts on nodeBB?:

    It could very well be that long-form nodebb posts are a better solution than Ghost?

    Well, I evaluated my usage of Ghost, and just didn’t like the complexity of it when I could achieve pretty much the same results with NodeBB, as demonstrated here

    To me, it seemed pointless to have another site completely act as an area where I could write articles, then have to use a plugin from NodeBB to provide commenting - why not just have it all in NodeBB ?

  • connect ghost with gatsby and CF pages and enjoy the 100 to 200 ms page load speed 😉

  • connect ghost with gatsby and CF pages and enjoy the 100 to 200 ms page load speed 😉

    @Hari I get that load speed with NodeBB alone 🤭

  • phenomlabundefined phenomlab referenced this topic on
  • Madchatthewundefined Madchatthew referenced this topic on

Related Topics
  • Ch..ch..ch..ch..changes!

    Announcements themes layout
    16
    2
    15 Votes
    16 Posts
    2k Views
    @phenomlab of course, to be recognised is fantastic. @phenomlab said in Ch..ch..ch..ch..changes!: Sadly, no. Web crawlers and scrapers are often JS based and read text only, so styles don’t have any bearing. I’ve read mixed things about this, but no that does make sense, it was something I read a many years back when using Wordpress.
  • Theme retirement

    Announcements themes switcher
    21
    16 Votes
    21 Posts
    5k Views
    I relented somewhat here and added another swatch - one I missed, which was previous called “blackout”. This specific one has been adapted to work on the new theming engine, but the others have been reclassified, and renamed to suit. [image: 1693924764891-d7f3a7a1-9702-4238-99bd-5c0e0d53f244-image.png] As a result, the theme you might have had will probably be reflecting something else, so you (might) need to change your themes accordingly. The changes are as follows Light -> No Change Cloudy -> Is now the old “Dim” Dim -> Is now the old “Dark” Dark -> Now a new theme based on the revamped “Blackout”
  • 36 Votes
    43 Posts
    9k Views
    I was experiencing 500 (Internal Server Error) responses from the proxy, visible in the browser console: GET https://proxy.xxx-xxx.net/ogproxy?url=https%3A%2F%2Fzupimages.net%2Fup%2F26%2F16%2Fld8h.jpg 500 (Internal Server Error) After investigation, I found two root causes: 1. Direct image URLs being sent to the proxy The custom JavaScript responsible for detecting links and sending them to the proxy was using the following regex to exclude direct image links: var fileExtensionPattern = /\.(png|jpeg|gif|pdf|docx?|xlsx?|pptx?|zip|rar|svg)$/i; Note that .jpg and .webp were missing from the pattern. As a result, links ending in .jpg were not recognized as direct image URLs and were forwarded to the OGProxy, which then tried to scrape them as web pages using open-graph-scraper — causing a 500 error. The fix was to add the missing extensions: var fileExtensionPattern = /\.(jpg|png|jpeg|gif|pdf|docx?|xlsx?|pptx?|zip|rar|svg|webp)$/i; 2. The proxy not following HTTP redirects Some image hosting services (e.g. zupimages.net) return a 301 redirect from the bare domain to www. When curl follows the redirect manually the image loads fine: curl -IL https://zupimages.net/up/26/16/ld8h.jpg HTTP/2 301 → https://www.zupimages.net/up/26/16/ld8h.jpg HTTP/2 200 However, the proxy’s axios.get() call does not handle this gracefully when open-graph-scraper is involved, resulting in a 500 error being returned to the client. My questions are: Is there a known best practice for handling redirect chains in open-graph-scraper? Would passing maxRedirects or followRedirect options explicitly to axios or ogs fix this reliably? Is there a cleaner way to pre-filter direct image/file URLs before they reach the proxy, ideally at the NodeBB plugin level rather than in custom JS? Thanks in advance.
  • Clustering for NodeBB enabled

    Announcements cluster
    22
    1
    16 Votes
    22 Posts
    3k Views
    @Madchatthew True. I think this is the reason as to why most Open Source projects are abandoned because they are not sustainable in the long-term.
  • NodeBB v3

    Announcements nodebb v3 nodebb
    2
    3 Votes
    2 Posts
    797 Views
    @cagatay JS will work fine - no changes there, and there are no plans to drop support for jQuery. More of an issue is the CSS - for which there are quite a few breaking changes. Keep an eye on sudonix.dev (my development site) where you can see progress in relation to how I am tackling the compatibility issues.
  • RESOLVED: Blog offline for maintenance

    Announcements blog
    9
    3 Votes
    9 Posts
    3k Views
    Well, just remember - No matter where ya’ go, there you are.
  • New blog section added

    Announcements blog comments
    1
    4
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • Fancybox now used for image handling

    Announcements fancybox
    16
    6 Votes
    16 Posts
    3k Views
    And it seems to be less conflicting!