Posts

• ---

  [NODEBB] Help for my custom CSS
  undefined phenomlab

  @DownPW Possibly, but the source files were also missing, and @cagatay has a custom theme developed by me.

  Customisation nodebb css bugfix

• ---

  [NODEBB] Help for my custom CSS
  undefined phenomlab

  @DownPW the FA library was missing with no paths defined. I’ve set these in the headers and uploaded the source, including necessary shim files which resolves the issue.

  Customisation nodebb css bugfix

• ---

  [NODEBB] Help for my custom CSS
  undefined phenomlab

  @cagatay Just looking at this now. Do you have a FA Pro 6 license, or are you trying to use the free version? It’s not immediately clear, and the directory structure on your server is a mess to be honest. Not sure what has happened here.

  EDIT - I have it working. DM me.

  Customisation nodebb css bugfix

• ---

  [NODEBB] Help for my custom CSS
  undefined phenomlab

  @cagatay if you look in the console (developers console in browser) do you see any error messages being returned?

  Linux is case sensitive, and it’s possible to have the same filename and folder name in upper and lower case.

  I suspect this might be the issue, but I could be wrong.

  Customisation nodebb css bugfix

• ---

  Nodebb to Xenforo
  undefined phenomlab

  @cagatay as @downpw stated, there isn’t a native tool that will do this for you. You’d need to either develop your own or ask the nodebb team to assist which will be a paid exercise.

  Configure xenforo nodebb

• ---

  What’s going on with NodeBB?
  undefined phenomlab

  @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it.

  Method 1: Using NVM (Recommended)

  If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed.

  1. Install Node 22:
     nvm install 22
  2. Switch to Node 22:
     nvm use 22
  3. Set it as your default:
     nvm alias default 22
  4. Verify the change:
     node -v

  ---

  Method 2: Using NodeSource (PPA)

  If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version.

  1. Remove the old NodeSource list (optional but cleaner):
     sudo rm /etc/apt/sources.list.d/nodesource.list
  2. Download and run the NodeSource setup script for Node 22:
     curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash -
  3. Install/Upgrade Node.js:
     sudo apt-get install -y nodejs
  4. Verify the installation:
     node -v

  ---

  Method 3: Using the ‘n’ Package

  If you have npm installed, you can use the n interactive manager.

  1. Clear the npm cache:
     sudo npm cache clean -f
  2. Install the ‘n’ helper:
     sudo npm install -g n
  3. Install Node 22:
     sudo n 22
  4. Update your shell:
     hash -r

  Troubleshooting

  • Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo.
  • Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc.
  • Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined phenomlab

  @DownPW I tend to stay at least one release behind intentionally to ensure maturity before upgrading - unless there is a good reason to do so immediately - such as identified vulnerabilities

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined phenomlab

  @cagatay what is in the nodebb log?

  Performance nodebb script die

• ---

  Claude Mythos in cyber security
  undefined phenomlab

  @crazycells I did see something similar to that article, yes. I never fully understood why anyone would want to give unfettered and complete access to AI without first understanding exactly what it had control of, and what it intended to do with that access.

  This isn’t the first “horror story” and it won’t be the last.

  Chitchat security artificial intelligence

• ---

  Claude Mythos in cyber security
  undefined phenomlab

  @crazycells I’ve not personally tried Claude Mythos to be honest, but I do know I’m fed up of the hype around Anthropic. Take this for an example

  https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-powered-ai-coding-agent-deletes-entire-company-database-in-9-seconds-backups-zapped-after-cursor-tool-powered-by-anthropics-claude-goes-rogue

  Who in their right mind grants AI this much power and expects it to end well?

  The real issue here is one of governance.

  Chitchat security artificial intelligence