Choose the wiki path just like you can choose the backup path.
This would also let people choose “files”, if they want to be compatible with the standard node.js static server.
That will not allow User B to see the attachments of User A in his wiki
The path could be stored in the shared wiki?
- Synced wikis or unsynced wikis?
- Synced through LAN or Relay?
- Collab plugin installed yes / no?
- Lots of rooms connected at the same time?
- Any terminal logs that are constantly repeating?
It seems to relate to opening a TW file.
No synching. Not even LAN. Room is disconnected. (Only 1 room). Disabled collab plugin.
It appears that just opening a TW file is making the TDrs process run at 9%, and the xorg process run at up to 30%. Shutting the open TW down restores the situation. The dashboard by itself seems to be OK.
Is there a log option that I can invoke? I tried piping the output into a file, and that didn’t work.
Thanks!
It cannot be an absolute path for obvious reasons.
The path will have a different format on Android (completely different).
I believe thinking everything through the current solution is the most practible one.
I posted to the wrong thread. I am talking about the desktop version.
Not an absolute path, but choosing which relative path. The path in node.js is relative, for instance.
The problem turns out to be the CodeMirror 6 plugin itself. (not the collaboration plugin). If I disable this, the resources go back to normal.
Is there a way to add plugins to the plugin button list, possibly with an environmental variable?
Yes like I already mentioned before.
It reads from your TIDDLYWIKI_PLUGIN_PATH.
It additionally reads from your (probably empty) plugins folder within your appdata of the app.
Those two places are scanned for plugins.
You just need to add plugins to those places
Except it doesn’t seem to find it there. Or rather, the folder wiki finds it, but not the single-file wiki. The folder wiki automatically loads it as a plugin.
I don’t know what this refers to. It sounds like something that Windows would have. Does this refer to directory <TDrs directory>lib/tiddlydesktop-rs/tiddlywiki/plugins ? I can definitely put a plugin folder there, but then I have to move it every time the app updates.
Thanks!
I was looking at the Readme, and it promises that we can chain save to TiddlyHost. I doubt this is possible (might have been possible with the old tiddlyspot). I think you would need to load directly from a tiddlyhost url. And their is no field for the user ID in the saver config, which is how you now log in to TH. If it is possible, I would be very interested to know how you configure it to do this.
Thank you!
1 Like
Hi @Mark_S
The correct wording would be that the TiddlyHost saver, if configured so that it works with whatever service supported, saves effectively to that service and the TiddlyDesktopRS saver saves a local copy, too.
So if TiddlyHost itself is not supported anymore by this saver there must be a reason why the saver is still in the TiddlyWiki core. Note that I haven’t added it. Neither I haven’t added GitHub, GitLab, Gitea savers.
The TiddlyDesktopRS saver just checks if those savers are configured when a save is triggered and lets them do their work - whatever they will do.
Lot’s of stuff in TW is legacy.
I think the only way TH could work is if it the URL for TH could be loaded in TDrs, including the log-in screen (does webview even save cookies?). The advantage of this is that you could consolidate all your TW files in one place – including those that are hosted somewhere online.
If I change a tiddler while disconnected, should it or should it not send it’s changes once the two files are linked and in the same room?
Currently they do not, but I’m not sure if that is by design or accident.
Thanks!
Would it be possible to not put the “register relay” in the details? There are already at least 3 steps to setting up a TW to sync, and that 4th step apparently is more than my brain can hold.
I wanted to do a test from a remote location, and went through the steps to sync, but forgot to register the relay.