good point about favs. maybe the download queue & hash files would be of
concern as well?
could we handle them through some upgrade step? could be done outside of the
XML parsing code, launched for these "precious" files when the XML parser
encounters a validation error?
some best effort to repl
@ maksis
Hello. I'm developer of Team Elite Hublist. You reported UTF-8
validation issue in our XML files, so I took a good look at it. You was
absolutely right, my pinger did not try to encode hub data to UTF-8 when
hub encoding was already set to UTF-8. It seemed obvious to me that if
hub says t
The validation function is cheap and there is effectively no difference
in filelist loading times.
Since it's possible to add favorite hubs directly from the hublist, it's
quite likely that there are users with malformed data in their
Favorites.xml as well. Disabling the validity check for certain
3 matches
Mail list logo
