I think going with skinny tiddlers for a wiki like that is the right way to go. …
I thin I did spot something. …
The permalink you gave us is loaded immediately, because it points to a skinny tiddler. When TW sees it, it knows to show the text content. … So it loads the body and shows it. Flux Capacity — WVW Log Review
The Network dev-tools say it’s about 400 kByte . That’s reasonably fast (for me). …
When I click a filter on that tiddler content is loaded on demand, as expected eg: lots of icons.
I close this tiddler. It seems the background shows an overview of the last 8 days. … Which then seems to request all that info. … with the next 1 minute default poll … that seems to be OK
if I open a new tiddler from the sidebar it opens the skinny tiddler … and also waits until the next 1 minute tick comes up.
So worst case users have to wait 1 minute … Best case 1 second … It depends, when the timeout is over.
So the question is: Do you “block” the request for the tiddler content by accident or by intention.
My guess. It’s an accident … may be a timeout setting somewhere.
I don’t use lazy loading, so I don’t know all the options that are possible.
So “lazy loading users” are requested here.