@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.

agreed, use syncthing (which I think @nutomic@lemmy.ml also works on!) and call it a day. @mariusor@metalhead.club @reiver@mastodon.social

@CWSmith your user resolves with the URL https://community.darkscribes.com/user/cwsmith ... but the ActivityPub response identifies it as https://communuty.darkscribes.com/uid/1, which is not the correct URL. Please update config.json's url so the typo is fixed and test again

@mariusor@metalhead.club do you have a database abstraction layer? That's what we do in order to support multiple data stores

A reminder that the Forum and Threaded Discussions Task Force is meeting in roughly 20 minutes at this Jitsi link, see you all there! https://meet.jit.si/ap-forum-wg

@silverpill@mitra.social looks like the label was removed because GitHub introduced issue types.

@altcode@social.vivaldi.net thanks for reporting. It's a persistent bug that has been evading capture for some time. For whatever reason, occasionally some accounts will lose their handle-to-id association in the database. That is why you are not able to access the profile page, because NodeBB doesn't think it exists anymore. For now the workaround is for me to manually reassociate, but I still have not figured out the root cause of the issue.