If you feel that Therendil and I are putting malware into your files, then stop using the UI. Otherwise we would appreciate it if you would remove the link to the updater files, thank you. Exposing information of this type on a public message board is unwise and dangerous. At best, it is completely unnecessary for resolving your issue.

Darqwood, I do not think you are posting malware, and am rather insulted that was your first thought.

I was asking for help in clearing up the issue so I COULD continue to use the UI. Sometimes it is something in the coding that triggers the flag and can be resolved simply, especially if I was not the only one having the issue. I had not gotten such a message before in all my YEARS of using the UI and promoting it to others.

At least you did confirm that the path was the proper one and not high-jacked.

Darqwood, I do not think you are posting malware, and am rather insulted that was your first thought.

I was asking for help in clearing up the issue so I COULD continue to use the UI. Sometimes it is something in the coding that triggers the flag and can be resolved simply, especially if I was not the only one having the issue. I had not gotten such a message before in all my YEARS of using the UI and promoting it to others.

At least you did confirm that the path was the proper one and not high-jacked.

Forgive me if you were insulted. But I was surprised to say the least to see the equivalent of home address, phone number and social security number of my server broadcast on a public message board. Possibly -- and this is just me thinking out loud -- it may be more prudent if one is concerned about a web server being hijacked to send a private message to Therendil or me with the internet address in question. I promise we will take a personal interest in helping to sort out any concerns.

I hope Avast is able to correct their detection database to eliminate the issue.

-= Therendil =-

These are straight-up simple txt and xml ASCII files, distributed with industry standard compression over industry standard connections. Frankly, if "Avast" chokes on the utterly simplest of the simple, then I have zero confidence in the accuracy of their detections.

I guess we are seeing the benefit of anonymous domain registration here. As for Avast flipping out on an XML file being downloaded. that is pretty silly. Any launcher/updater I develop will also periodically check a 3rd party website for the availability of updates.

I did suggest to register a domain, then use cloudflare dns and free cdn/ddos protection. The public when pinging the domain will only see cloudflare's ip and it will keep your origin ip private as long as the cdn/ddos protection is enabled under their DNS settings. As long as the general public only needs content on port 80, 8080 or 443 your good. They even provide free SSL from user to their cdn servers.

I'm a little weirded out by some of the reactions in this thread, the urls the updater hits are pretty obvious. Maybe another option would be roping Feldon into this for the updates hosting? (sorry feldon~)

Thanks for the PSA in any case, @offkilterkitty. Hopefully it's been addressed and Avast won't scare any less savvy users away. Sorry you got beat up about it.

I'm a little weirded out by some of the reactions in this thread, the urls the updater hits are pretty obvious. Maybe another option would be roping Feldon into this for the updates hosting? (sorry feldon~)

Thanks for the PSA in any case, @offkilterkitty. Hopefully it's been addressed and Avast won't scare any less savvy users away. Sorry you got beat up about it.