I think the privacy issue is a weak one, what kind of privacy data are you divulging because you downloaded a modification?
If someone is really paranoid about an author seeing they downloaded 'separate sticky threads from normal threads' then I think they should not bother downloading it.

However, thats just my opinion (and you know what they say about those!).

To me, these (and other) suggestions can easily be broken into multiple projects and then married together.

As far as I can see at this stage, we have:

1- A mini bug tracker (related to release by a projectid)
2- A mini rating/rep system (related to project and user)
3- A download/upload system with browseable history (related by projectid)
4- A project manager

If we can settle on core components of the system, then maybe we can start to organize teams to work on them?

Great suggestions TheGeek! yesterday during all those discussions about hackers leaving, not getting enough recognition and so on, I thought about a way of tracking installations. Anyway its not the greatest, but could be taked into consideration if hacks weren't just a single xml file.

For instance, you get a 2 step install screen here @ vb.org. The first one showing all the details about the hack, what it does, what vb versions support it, screenshots and how you can benefit from it.

The second window will allow the users to download the plugin, code modification, skin, whatever it is. And when THAT second screen/window is accesed and, I dont know, but maybe 10 seconds pass, the install button is automatically clicked/add 1+ to the install count.


What I dont like, is when you install a hack in a board, it automatically installs here in vb.org. Because most of us work with a lot of boards, maybe giving "installation" support, or helping other people around. And then when I come here, we have dozens of hacks we really dont care ;)

Appart from this, im not really sure if when we un-install some plugin/product, happens the other way around. Does it un-install also here at vb.org? :S If this is so, its really bad.


Just my 2cents. For coders to get their installation count more accurate.

Thanks!


ps. TheGeek u're never on a bad mood! Even your hack installers are full of joy and fun! =D keep it up

Thank you for voicing your opinion COBRAws.

But let's please use this thread to discuss future improvements to vBulletin.org, and not to have here another discussion about the Auto-install issue. Let's keep this thread clean and only do future suggestions.

Sorry MarcoH64

Is anyone truly bothered if the author has the ability to see who downloaded, what version and when?

I envision this being different than an install button.

To me, an install button is a form of:
1- Users being able to quickly see what modifications they have installed.
2- Users being able to keep notified of what modifications are updated.
3- Supporting the author.

I guess I just don't buy that there is any privacy issue here. If you downloaded it, why does it need to be kept a secret from the author?

I can't say that I fully agree but I respect the reasons. Thanks, MarcoH64, for addressing my questions. :)

Pretty good job Sam...
I myself like the idea of a team working together, where coders check one another's code since we're releasing our hacks for the sake of sharing, and for free!
Everyone is going to benifit from this, especially coders.
I don't mind getting an adivce (supports) from others, getting to know all the (how, where, why and when) needs taking my mods to the next level.

Like you, I personally, don't see a problem with it, but there could be if a member here was ever contacted by an author, for whatever reason, and that member felt like their privacy was invaded. Not saying it would ever happen, but an author could use something like that as a mailing list for any future hacks (commercial or otherwise) that he/she does.

I understand what you're saying and I know that isn't the only reason (if it's even a reason) as to why it's kept private for all those not posting in the thread, but why not impose a rule where the coder that employed such tactics would be punished, maybe even banned if the activity keeps up?
I mean, it wouldn't be too hard to figure out who did it, since the product they would be advertising would be traceable to said coder =P

I just hope that if it is made public, it won't scare users away from clicking the install button for whatever paranoid reason. It's hard enough to get people to click install as it is.

Point taken AND noted. ;)

When it comes to privacy, it gets to be a very controversial issue. It can be something totally innocent, and yet all it takes is one person to screw it up. Sure, you could take action against anyone who did it, but by then the damage would have already been done. And all the person has to do is let everyone else know what happened, and then you have a privacy scare on your hands. ;)