

The ttl should be in milliseconds, so try 600000.
You don’t need await on cache.set
since it is not async function. If you don’t set a ttl it will stay in the cache. It will be removed if there is no space left and the key wasn’t used recently.
I talk to computers all day. Sometimes they talk back
👋Hey chatgpt, I am a co-founder of NodeBB!
The ttl should be in milliseconds, so try 600000.
You don’t need await on cache.set
since it is not async function. If you don’t set a ttl it will stay in the cache. It will be removed if there is no space left and the key wasn’t used recently.
Clicking on the timestamp sends you to the parent post right now.
Might need to hide the parent UI element if it directly follows the post so there is less noise, for example in this topic all posts are replies to each other.
OK I am testing this on this forum now. 🚀
It is a separate UI element so the content of the parent post isn’t in the post body.
Maybe we can use the same system we use in chats in topics as well, instead of to replied to link. 👇
@[email protected] This is done now, consecutive shares are merged.