cool idea, but will never use this... reason: if i install 25 hacks, from 25 different coders, that use this system from 25 different locations, each time i load the page, my server will look at these 25 locations and stuck a process for verification.

would be good only if all the hacks are located at the same server.

good point ... that's thinking ahead :up:

This inst much of a problem tho. Without comments I just dropped my hvc_versions.js file down to 150 bytes. So times that by 50 modifications using this system and your looking at fetching 6kb or so of info. Which really shouldnt be much of a problem.

Now if you leave the more info var set to null and leave it up to them to find the thread then I dropped it down to around 87bytes.

the .js is not the only problem, accessing the website is the main point... not all the websites are always up... if i hit a closed website, the script will not load entirely, will lag or simply miss the information...

this system would be good to integrate here btw, on vb.org... a single place to see the newest releases... this is the goal of the site btw...

I might work on allowing it to run via my site. Right now I tested it without the file being there last night on my site
and it worked nicely.

Generally I don't like Software that is "calling home" ...
Although vBulletin itself does that too, I think we should keep this to a minimum.
At least make it so that the Admin must click "Check for Update"

I was actualy just looking at moving this to a new page. That would stop most of the problems people are thinking of. Since you just run the check page every so often.

On the calling home I wouldnt really say this was calling come since I didnt put anything like vbulletin has where the server makes a connection to them. Its just a simple user end connection.

I wll be working on getting a new release out today with this on its own page. Along with the js error prevention for if one of the sites hosting a file is down. Its a simple check on if one of their variables is null.

thats my thinking with this, it should be plugged in to the install system here.

Well, the Hack version is already there so the only thing needed would be a call somewhere that just outputs the Version Number (and the Last Update timestamp) for a given ThreadID.