Jeremy Ruston

Hi @hoelzro @pmario I think I've somewhat hardened my position to thinking that we should opt into strict tables now, keeping our options open for opting out later if there...

Thank you @hoelzro @CrossEye. Conscious that the discussion thread at #6666 quickly got unmanageable, I propose to spawn separate GitHub discussions for each of the major areas of discussion. I'll...

> As I understand it, best practices seem to be trending away from passwords altogether. This option -- which I'm guessing a large number of users would want -- is...

> Indeed - maybe they could be leveraged for some of the deletion logic by way of `CASCADE`, but the logic to clean up is already there, and it's nice...

> @Jermolene BTW I noticed the "Instant syncing from server to browser" feature as well - do you have any thoughts on how you'd like to approach that? That feature...

I have been exploring switching to using SQLite3 compiled to Wasm instead of the current native code implementation. See #7996

> @Jermolene ... I think there is a typo and the wrong start command in the OP Thanks @pmario, much appreciated, I've edited the OP.

I've just completed some fairly major refactoring in preparation for beginning work on the improved synchronisation process: * No longer using the main root wiki for admin functions * Introduced...

Hi @pmario given that this change doesn't satisfy the requirements of the original requester (see https://github.com/Jermolene/TiddlyWiki5/issues/4224#issuecomment-1922729285), I propose that we shelve this for the moment. It makes the saving mechanism...

Hi @pmario it may be worth bringing this up at talk.tiddlywiki.org to see if there's any mileage in it. Without a clear use case I am not keen to merge...