I think mostly this is summed up to deal with the idea of enhancing TiddlyWiki or Tiddly Desktop to be able to serve in a capacity to configure hardware peripherals through cross platform web interfaces built with custom TiddlyWikis with individual TiddlyWiki plugins.
The largest version of this idea would be for the core developers to charge a small fee to develop these web interfaces for companies who create these peripherals, of which there are many to market to.
Because TiddlyWiki can be portable, then these configurations could be stored and transferred across platforms, consistently, longterm. Enticing.
A company could distribute a plugin, or a specific TiddlyWiki, with their plugin. This way, the plugins could be included and compiled into collections as users see fit, as long as they weren’t themed too uniquely.
The more participants, the merrier. If TiddlyWiki can build more and more clients to make it an attraction. Users being able to store these plugins in a collections could also be a marketing thing to these companies. These little obscure programs are awkward to keep track of individually, and they frequently only work on one particular Windows version.
(Now, I’m a Linux freak, so that’s a big aspect of this for me.)
There are many, many things you look at online that have these little configuration programs, and they’re mostly very utilitarian. They don’t need a lot of frills, and in fact it might actually be beneficial if they are similar in some ways. TiddlyWiki could market itself as a quicker way to create these configuration utilities if they made sure there was the right avenue to system access to do so cross-platform.
Smaller Idea Version
Some form of this idea can already be done by creating plugins that work for hardware peripherals that use configuration files. There are keyboards and mice and game controller devices and programs that implement portable config files.
TiddlyWiki interfaces could be used to create and modify these configs for other programs utilizing images and options to create the configs. (although these might not be worth charging for generally.)
Other configs
The idea could also be expanded to store and maintain configs for more complex configs for software like web browsers, browser-specific bookmark formats, and anything else that uses rule-based configs.
Exporting File Formats
Although it’s not too difficult to modify exported tid files, it would be great if TiddlyWiki could export to any particular chosen file extension. Now, maybe there’s a way to do this, and I don’t know, but it’s worth mentioning.
Suggestion
Anyway, it’s just a thought. I know a lot of these devices that you shop for have these little programs that only work on Windows, and it’s very frustrating. It might be a matter of marketing the idea as TiddlyWiki being offline and portable, and easier to develop than full JavaScript application from scratch, and cross platform through Tiddly Desktop’s NW.js foundation.
It’s really up to the core devs “in the know” about the hardware technicals on Linux/Mac/Window implementations. These products have different technical nuances etc.