vb.org Cron Job Suggestion.
 

Just a suggestion that I think members would take advantage of is to create an option where users could sign up to recieve email as per a set time ( ie. every day, week, etc. ) that would list all of the current hack releases. That way members could know what was released and to know exactly where to look for it ( email contains links to the new hacks, the hack author, vb version etc. ) Not that I personally would take advantage of this feature, but I think that members that come to find out the latest hacks and to look for features would find this option a plus.

Cheers,
g-force2k2

i think thats a great idea its kind of hard to keep track of all the hacks and a weekly digest of new hacks would help a great deal

hmm, i'll think about it, but cannot promise anything.

i don't want to increase the ammount of mails sent out right now to far ;)

Try a test run, Stefan, and see how it goes before you decide. ;)

[high]* Boofo thinks that since he came up with the idea of a test run he ought to be first on the list?[/high]

Good idea but may be a strain like Stefan said :)..

I would defenitely go for this.

I remember in an old thread i made Xenon agreed to like a weekly vB.org newsletter, with new hacks on it etc etc, but he said not until after Gold :)

I think it's only server-efficient if you make it ONE set time, and not give the user any time-options to choose from. Basically, give them this option:

Receive weekly Newsletter: Yes/No

Giving people monthly/weekly/daily options will cause a lot more mails and forces the cron job to be run much more often.

But other than that technical detail, I think it's a good idea, would be nice to send out an email to all members beforehand (all who have "Receive Admin mails" set to Yes, anyway) to inform them of the new feature, and the changes etc. on vB.org. Might get a lot of people's interests in vb.org back up, that ;)

i'll definitely not add it before gold :p

@Kura: bah, emails, i already fear the undeliverable mail responses if i'd send out such a newsmail ^^

That's why you have bounces sent to /dev/null ;)