Replies: 2 comments 1 reply
-
Hi @linonetwo in #3461 we've been experimenting with allowing the browser to trigger commands to be executed on the server (amongst other things). I'll add a note there. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This reminds me of #3000 as well! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Notion and roam research and logseq calculate their backlinks in the server side. And relink also happened in the server side.
Running and caching things at the server-side have 2 benefits:
Reduce the memory usage, allow huge KB to mount
Currently, if we have 1GB of toddler files in the disk, we will load 1GB in the nodejs, and 1GB in the browser, this is a waste.
And some widget like backlink, that relies on loading all the tiddlers, can work on the server-side, and send the result to the client.
Run heavy things in server-side
Currently, if we want to refactor our KB, we can use relink plugin, but relink progress will run in the browser, relies on we fully load all tiddlers. So if we lazy load the tiddlers, it will not work.
Run these tasks on the server-side will solve this problem.
Beta Was this translation helpful? Give feedback.
All reactions