I ended up adding a child span to hold the tooltip, and just removing the child altogether anytime the event fired. Inserting a new element and then setting the tooltip was the only way to get the tooltip updated correctly (for me). Thanks for the help!

A socket event is sent when a new topic or reply is made, they are called event:new_topic and event:new_post. We listen to that and update the ui when a new reply comes in.

Yeah your flow should work, we don't trigger it on all instances as that would cause issues if the function is doing db writes for example. You would have 2+ instances trying to create the same records etc.

My fault. I wasn't calling ajaxify.go correctly. All works now.

Thanks!, I was able to debug the issue.

Thanks, that works perfectly

Make sure you add jobsDisabled: true to all the machines except one so they don't run jobs. That error is usually fine since multiple machines will try to write out their analytics at the same time. The ones failing will retry and it will work on the second try.

That should be it, all the paths in template use {config.relative_path} as a prefix so things should work as normal

It finally happened again, Looks like app.user.uid doesn't match the logged in user uid as app.user.id is set to 0 while the uid is 2. It all starts working again as soon as I flush the Cloudflare cache. Where are the app values gettting set? [image: 1694730958697-screenshot-app.datadoghq.com-2023.09.14-17_35_09-resized.png]

Thanks, that works perfectly. I'm handling the hook in my custom theme, but this probably needs to be in the https://community.nodebb.org/post/95161 plugin as well (without the importedVotes) library.setTopicVotes = async function(hookData) { const topicData = await topics.getTopicFields(hookData.post.tid, ['cid', 'importedVotes']); const importedVotes = topicData.importedVotes || 0 const voteData = await db.getSortedSetRangeByScoreWithScores(`tid:${hookData.post.tid}:posts:votes`, 0, -1, 1, '+inf'); let allvotes = voteData.reduce((acc, cur) => acc + cur.score, 0); allvotes = allvotes + importedVotes await db.sortedSetAdd(`cid:${topicData.cid}:tids:votes`, allvotes, hookData.post.tid) }

@baris That should work, I'll give it a shot. I love the customizability of nodeBB. Particularly the ability to override templates and language files in the custom themes. It would be amazing if that capability could be extended to other file types as well just by placing the customized files in a folder structure that mimics the structure of the core files.

@baris Thanks for the confirmation

@razibal that would work for a single server but once you have multiple servers each running multiple nodebbs you would need the socket.io redis adapter. https://github.com/socketio/socket.io-cluster-adapter/issues/1

Thank you, that works perfectly. In most cases something like this is much better handled through the write API. However in this instance, due to the large number of updates, it was much more efficient to process them through a script (roughly 50x faster).

I'm trying to understand the legal implications of allowing EU residents to create accounts on a US based forum. Is it sufficient to place verbiage in the ToS that requires acceptance of data residency in the US? For example We care about data privacy and security. By using the Site, you agree to be bound by our Privacy Policy which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you agree to have your data transferred to and processed in the United States. Are there any other clauses that need to be clearly identified? We do state the identifiers collected when creating an account All data collected is solely for the purpose of providing unique indentifiers in order to allow for the creation of a user account that is then used to access our services. None of this data is shared with 3rd parties, and our own usage is restricted to informational messaging around the operation and functionality of the application. We may ask for and store the following data elements as part of our Sign Up process: Username (can be fully anonymous) A valid email address A valid phone number for dual factor authentication (optional) Any gotchas to be wary of? or any advice in general would be much appreciated.

@baris Thanks much, your help is always appreciated.

I was able to achieve the desired functionality by adding a custom "Share" button to the template for the private topics. This button triggers the move to predesignated categories based on the type of post. Cheers

@julian I think we've got it working albeit without the splitting out of objects to multiple collections. I think we'll probably tackle that as well, fortunately it should be relatively straight forward since the keys are already prefixed with a logical collection name e.g "post:1380" or "user:100". In the meantime we have some testing ahead of us to ensure that nothing breaks. We're happy to maintain it ourselves, but I think you guys should consider adding it as a core database. It gets NodeBB one step closer to being the first true "cloud native" forum platform. The only thing left would be splitting the UI from the API services and you would be all the way there.

AI moderating "conspiracy theories", that's a conspiracy theory confirmed!

I was able to use Categories.setCategoryField to tag the categories that are customized with topic cards and then use that attribute in the templates.