PluginUpdate plugin update 0v21 (unicode)

I like the idea, but the main problem I see with the current implementation is the need for the ini and the dll to be available online for download, and personally I am too lazy to maintain that. Wouldn't there be a way it could read the Sourceforge file listing (I try to use consistent version numbers with releases), download the zip and unpack the right dll? I can have the DLL write its own version number to the local ini, the next restart it would be rewritten.
Another possibility is for the updater to have its own ini with a list of URLs and versions (maybe with regex), that the user can define, for example a plugin author gives an URL template and the updater uses that. Theoretically the plugin doesnt have to do a thing (easy version access could be usefull, for example with cross-plugin messages like NppExec supports, ini file and read the version info from the DLL itself that explorer also displays (hard)).
Third option would be sole use of cross-plugin messages, requesting current version and URL template.

The cross-plugin message could use a sort of linked-list datastructure so each plugin can append to it (using a common header).

URL template could be something like
http://..../$(NAME)_$(MAJOR)_$(MINOR)_$(SOMETHING)_$(BUILD)_dll.zip , you could retrieve RSS feeds and skim through them.

Anyway, what I'm talking about here is more of a whole new plugin that a little change, I'm just throwing ideas here from my point of view (ie being lazy).

BTW, is any of the other plugin developers using or planning to use the facility offered by this plugin?

If nobody find this useful I will abort it and incorporare the automatic update in some other way in my plugins.

Thanks,

Franco