@crazycells It's a massive security risk along with .mov

We've actually straight up blocked .zip and .mov TLDs where I work. And I know a lot of other companies have/are doing the same because of the risks it poses.

@josef If you have the realip caddy module installed you can add:

realip {
    header "X-Forwarded-For"
    from cloudflare
    maxhops 5
}

@julian Ah I was not aware of his (or your) comments on Federation in Mastodon. Pretty much everything I know about it is from the roadmap. I haven't even seen much on it on the Flarum discord or information behind the scenes (I should have disclosed that I'm a former Flarum core dev, and still sometimes maintain their VMs)

Me and a friend started up SysAdmins Zone would be cool to see it on the list. (We're also coming over from Flarum, and we're loving NodeBB so far)

@baris Thanks, updated and everything is working now.

@julian Unread is my preferred when signed in to a NodeBB (or Flarum) forum. While recent is my preferred view when I'm not signed in. Probably are carry over of working with Flarum forums for such a long time, at this point I very much dislike seeing the category listing as the main page and prefer to see content out the gate.

@phenomlab if he's a dino, I must be a grandfather at the ripe old age of 25....

@phenomlab Cloudflare Free plans have a 100ish max connections from what I remember to/from WebSocket's. I believe you can submit a support request with Cloudflare to up it to something more but I can't remember all the details. But basically what it comes down to is Cloudflare can't cache that data, and in some applications WebSocket's sends a ton of data which costs quite a bit of bandwidth on Cloudflare's side so they try to avoid it on the free plans by restricting the max number of connections.

Edit: https://developers.cloudflare.com/support/network/using-cloudflare-with-websockets/

Based on some general reports it looks like the Pro plan gives 5x the number of WebSocket connections over the Free plan, and a similar increase from Pro to Business.

@josef as @baris noted, this is something you have to fix at the proxy (Caddy), so adding the configuration options I noted (if you have the correct module in Caddy) should solve the issue. I've been running it on my site for a little over 2 months now and everything is resolved properly.

@eeeee said in Do you have limited or full access to your host?:

it does seem younger people are preferred as coders, but I don't get why?

Where I work all the devs are 50+ years old. And honestly, given the stuff we do I wouldn't trust a 20 something dev with it anyway. (Complex accounting software/ERP software that has to meet regulatory conditions).

These guys have been at it for 30+ years and actually helped write some of the original modules (before the CEO pulled them away from the company that writes the software we customize). And their knowledge is VAST, hell the lead engineer actually has a degree in forensics accounting.

@julian said in What's next after v3?:

NodeBB being a piece of software that is installable and configurable by individual admins means we've already achieved half of the formula for federation. It's theoretically possible to hook NodeBBs together and share content.

I've often said that Twitter is like shouting into the wind. Starting a forum is often like talking to an empty room. It's very possible we can take steps to change that

Flarum is also currently looking into Federation, personally I'm both for and against it, at the end of the day it should come down to whatever forum admins want to do with their forum. But if this is something that does get developed it would be nice if Flarum and NodeBB could in some way work together a bit to make sure that their implementations are compatible (at least the core of it) so that it's something other forum software could also participate in (instead of only NodeBB or only Flarum).

@julian said in What's next after v3?:

Drop jQuery
Ha ha, just kidding. Or am I?

Please do, native JS has come a long way and jquery isn't really needed much anymore and it pretty much just adds to JS bloat unless your doing very specific things with it. Even if you can't completely get rid of it, maybe use one of the much lighter alternative versions of it?

@julian said in What's next after v3?:

Yes, you're right. Having the passkey used as the first and only factor would be what passkey is hoping to implement. It would necessitate some changes to the 2factor plugin, including the fact that it's no longer a second factor

I would very much like to see PassKeys come to NodeBB, I was actually just looking into how feasible it would be myself a couple weeks ago. I don't think I have the knowledge required to do anything with it at the moment, but it'd be nice to have, even better if it's something that can be used in v3.

@[email protected] While I generally agree with you, meetings like this tend to require tooling that I personally just haven't seen in open-source meeting software solutions yet. Not to mention, depending on the interest in the meeting it's entirely possible that something open source hosted on someone server might become overloaded and fall over, something that is unlikely for commercial software solutions.

@baris I think I may have found the issue, I ended up console logging the data.map function to console.log({email: entry.email, custom_fields: fields}) and what I discovered is that somehow, some way, a couple of users exist that have zero email associated with them. Which would in fact cause the 400 error I'm experiencing.

Deleting those user accounts (no content or posts) resolved the issue.

So I want to start off with saying that notification on @mentions hasn't been working at all on our forum in public chat rooms. But it appears that the situation is now worse as specifically mentioning a user in public chat causes the forum to completely crash and reboot with the following error message:

2023-08-25T01:29:33.228Z [4567/1686462] - error: uncaughtException: Cannot read properties of undefined (reading 'displayname')
TypeError: Cannot read properties of undefined (reading 'displayname')
    at Object.Mentions.notifyMessage [as method] (.../nodebb/node_modules/nodebb-plugin-mentions/library.js:195:73)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.fireActionHook [as action] (.../nodebb/src/plugins/hooks.js:211:4)
    at async Hooks.fire (.../nodebb/src/plugins/hooks.js:132:17) {"date":"Fri Aug 25 2023 01:29:33 GMT+0000 (Coordinated Universal Time)","error":{},"exception":true,"os":{"loadavg":[0.92,0.71,0.42],"uptime":784611.42},"process":{"argv":["/usr/bin/node",".../nodebb/app.js"],"cwd":".../nodebb","execPath":"/usr/bin/node","gid":0,"memoryUsage":{"arrayBuffers":22579632,"external":30825859,"heapTotal":125403136,"heapUsed":109508072,"rss":198705152},"pid":1686462,"uid":0,"version":"v16.20.2"},"stack":"TypeError: Cannot read properties of undefined (reading 'displayname')\n    at Object.Mentions.notifyMessage [as method] (.../nodebb/node_modules/nodebb-plugin-mentions/library.js:195:73)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async Object.fireActionHook [as action] (.../nodebb/src/plugins/hooks.js:211:4)\n    at async Hooks.fire (.../nodebb/src/plugins/hooks.js:132:17)","trace":[{"column":73,"file":".../nodebb/node_modules/nodebb-plugin-mentions/library.js","function":"Object.Mentions.notifyMessage [as method]","line":195,"method":"notifyMessage [as method]","native":false},{"column":5,"file":"node:internal/process/task_queues","function":"processTicksAndRejections","line":96,"method":null,"native":false},{"column":4,"file":".../nodebb/src/plugins/hooks.js","function":"async Object.fireActionHook [as action]","line":211,"method":"fireActionHook [as action]","native":false},{"column":17,"file":".../nodebb/src/plugins/hooks.js","function":"async Hooks.fire","line":132,"method":"fire","native":false}]}
2023-08-25T01:29:33.230Z [4567/1686462] - error: TypeError: Cannot read properties of undefined (reading 'displayname')
    at Object.Mentions.notifyMessage [as method] (.../nodebb/node_modules/nodebb-plugin-mentions/library.js:195:73)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.fireActionHook [as action] (.../nodebb/src/plugins/hooks.js:211:4)
    at async Hooks.fire (.../nodebb/src/plugins/hooks.js:132:17)
2023-08-25T01:29:33.231Z [4567/1686462] - info: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised.
2023-08-25T01:29:33.235Z [4567/1686462] - info: [app] Web server closed to connections.
2023-08-25T01:29:33.239Z [4567/1686462] - info: [app] Live analytics saved.
2023-08-25T01:29:33.256Z [4567/1686462] - info: [app] Database connection closed.
2023-08-25T01:29:33.257Z [4567/1686462] - info: [app] Shutdown complete.
[cluster] Child Process (1686462) has exited (code: 1, signal: null)
[cluster] Spinning up another process...

I'm happy to do as much debugging as needed to get this fixed and provide whatever information is needed. Below is the list of plugins we're using.

Active plugins:
        * @nodebb/[email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)
        * [email protected] (installed, enabled)