@FrankM @brayd genau so betreibe ich opensuse

Are you using the ActivityPub functionality? It might be related to that if only because that's what's new (among other smaller items) in v4. If you toggle the global activitypub switch off, does that make memory usage stabilize? Keep in mind that since you upgraded, ActivityPub is automatically disabled, so perhaps this is unrelated.

@chartung you can also check out the scaling tips here: https://docs.nodebb.org/configuring/scaling/

@nlnetlabs@fosstodon.org oh! Oops unfortunate name collision.

@eeeee is right, it's pretty much an arms race between those who want to get the file, and those who don't want the file downloaded. Keep in mind that if a browser is viewing the file, then it has de facto already downloaded the file. The "save as" functionality is mostly a convenience feature for you to re-locate the downloaded file elsewhere.

@kriptokyng stop using :4567 in the url.

@Laz it was a typo, you can run the script with node script_name.js, which invokes the node.js interpreter.

@pfefferle@mastodon.social just wanted to poke you about this issue again. The latest updates to NodeBB now do a webfinger backcheck to ensure that the actor has a valid webfinger entry for their purported handle. If it does not, then the user is not properly created. Mastodon also does this. This check is probably for security as well as for preventing handle collisions. The multilingual plugin in conjunction with the ActivityPub plugin creates users that share the same handle, and that causes issues with federated content. For example, this article by @jonvt@vivaldi.com will load up just fine in Mastodon, but this japanese article by @akira@vivaldi.com will not, because that second article's attributedTo is https://vivaldi.com/ja/?author=176, which fails that check (the author's ID is actually https://vivaldi.com?author=176 as per the handle backcheck) cc @AltCode