Arlen Beiler

So I think my concern is that this seems to be implemented somewhat inconsistently. My main question is why do changes still need to be propagated to the server? Or...

To be clear, I don't have a problem with the feature, I'm just trying to understand what it is accomplishing because I'm looking into several things related to this.

> So I think my concern is that this seems to be implemented somewhat inconsistently. My main question is why do changes still need to be propagated to the server?...

I think I had a draft yesterday and then closed the tab. In brief, I propose several changes. https://github.com/Jermolene/TiddlyWiki5/blob/7ec6d3703150469e73dabcf25655192767092a77/core/modules/server/routes/get-tiddlers-json.js#L23-L24 - Here we should change `$:/config/Server/ExternalFilters/` to refer to the title...

> * Here we should change `$:/config/Server/ExternalFilters/` to refer to the title of a tiddler rather than the text of the tiddler. This will make it easier for the user...

While that takes care of the server tiddler list, it would be used for lazy-loading as well, so do we need a separate filter to change the list of tiddlers...

So `SyncServerFilter` would be served in tiddlers.json, and also be used to filter the list of changes in any event emitters using server sent events or websockets. `SyncClientFilter` would be...

Obviously once we implement bags and recipes in the Wiki class we're going to get a little more complicated, but not much. I think this lays the groundwork pretty well.

Basically, `SyncServerFilter` and `SyncClientFilter` work in tandom. `SyncServerFilter` would affect which tiddlers get synced to the client through all of the several sync mechanisms, and `SyncClientFilter` would affect which tiddlers...

> * Here we should change `$:/config/Server/ExternalFilters/` to refer to the title of a tiddler rather than the text of the tiddler. This will make it easier for the user...