@Марк-Дакаскос widget-essentials is packaged with NodeBB and is compatible. Its version is also pinned to the NodeBB version, so you do not need to update it unless you are upgrading NodeBB versions.

@trwnh@mastodon.social given that one way a context collection is discovered is via reference via a collection member itself, that's one way to define it. Admittedly, direct access to a context collection is also a legitimate use case (e.g. a NodeBB topic URL itself is the context collection), so something more explicit might be required.

@niccolove It's nice to have you back in term of content creation! I'm an happy Patreon supporter

@trwnh@mastodon.social correct. I suppose the easiest way to communicate permission would be that the thread deletion has to come from the context owner. In my case the context owner is a category, so it'd be federating out the deletion on behalf of the moderators.

@rikudou thanks, can you file an issue on the GitHub repo? https://GitHub.com/NodeBB/NodeBB/issues/new

@2TonWaffle ah, yes if you turn on the filters to "allow list" then it denies stuff from servers not on the list!

@xbermusic@mastodont.cat can you try renaming the handle to something else and back again?

@Kichae the github issue is here: https://github.com/NodeBB/NodeBB/issues/13172 I think I found the source of the problem and fixed it. Try updating to the latest master or develop commit and see if it still happens.

I have been following a Lemmy community from Firefish and I only get original posts, you can see this behaviour here: https://electricrequiem.com/@comradeship@lemmygrad.ml However Firefish has had problems with following Lemmy communities so this may not be the default behaviour from Mastodon. Still, I do think that boosting all replies is not ideal, especially for busy forums. If a topic gets say 50 replies, it can really flood your timeline. Also personally I have set up my Firefish account to only show me original posts (and boosts), to have a cleaner and more compact timeline. With a forum account that boosts everything, you can't filter replies, they all end up in your timeline. So my suggestion was to perhaps create two accounts for following a forum, one than boosts everything and one that boosts only original posts. This way users would get a choice, and if they find that following everything makes their timeline too busy, they can choose to get only original posts, instead of unfollowing the forum completely.

@Jakub-Urbanowicz http://forum_n66_pl this suggests there's an upstream block. Can you paste your entire nginx config?

@CWSmith silly question, but is the second NodeBB running? Are there errors when you run it, and does the last line report it listening on port 4568?

@openrisk@mastodon.social not a bad idea. NodeBB actually already does this. We have a configurable max on hashtag usage, and so if a post comes in with > 5 (the default) we just remove everything after the fifth hashtag. They're still in the post content, but only the first five count in indexing, etc.

@mario https://offline.place/ often has events in that direction

@NodeHam just the one here https://github.com/NodeBB/NodeBB/issues/new?template=feature-request.yml