it sounds like extending the REST api is the way to go with this. Having a script that manipulates the .tid files is possible, but also something like reinventing the wheel. You can rename and filter tiddlers in the node server without building any of the utility functions yourself and then you have the benefit of all the testing and work everyone else has done to ensure stability.
Unless you have something specific to Bob that you need it may be better to use the core tiddlywiki server. Bob doesn't have sufficient security built in to it to be on a public-facing server yet, you would need to have apache or something similar in front of it for security. And if you use Bob the API routes are a bit different because it has to handle multiple wikis. They follow the same general structure as the core routes but remember the different module type. Let me know if you need any help. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9ffc4c9d-ad01-415d-b1cf-ea50505b8e39o%40googlegroups.com.
