VoodooShield ?

I came back here and found out people had lost a developer status/posting rights...

Can someone PM me with info on what happened? (e.g. what was said to cause the bans, etc.). I am just curious

 

This

The way a few individuals were hounding here was a disgrace and allowed to do so without any intervention.

 

@Triple Helix's suggestion would appear to be the best interim solution at least, as it is already there..

https://www.wilderssecurity.com/threads/voodooshield.313706/page-690#post-2700504

 

Dan has three choices:
-His own forum
-MalwareTips
-CalendarOFUpdates

He just has to choose!

 

There is a fourth: "Don't feed the trolls!" Dan rises to the bait like a trout to a fly, and it's sad.

But yes, an in-house forum has much to commend itself.

 

His own forum would give much more control, true. Very sad, this has been the VS source for a long time, but I'm over it. It would be welcome if an associate would drop a line on his behalf, it's been a week. But that's OK, I wish him the best.

 

So how is VoodooShield working for everyone?

 

On one machine VS seems sometimes to interfere with Acronis and Macrium scheduled differential or incremental backups, with no blocks or errors.
All I know is that the problem disappears if I put VS in disable / install mode.

Awaiting 4.0.

 

I've always had performance issues when using VS. Tis why I never use it. Curious to see if 4.0 stops the madness.

 

Fine for me, but see https://www.wilderssecurity.com/threads/zam-free.395690/#post-2700849 for what shouldn't happen... This is not how you should do updates.

 

Here, some word on the situation:

https://malwaretips.com/threads/voodooshield-discussion.63827/page-16#post-664422

 

Refreshing news!

 

Good news, good move by Dan..You can't keep a good man down!

 

I just want what is best for VoodooShield and continued discussion with Dan on the project.

 

Working very smoothly here. No issues for a long time.

 

For what it is worth I think that if Dan and anyone else involved with whatever went down to cause this mess apologized to each other then they can all focus on themselves and put what happened in the past without needing to be banned from posting.

Developers bring traffic and there are members using many product combinations here. Many people find it easier to keep up with updates and announcements on a forum like this also.

I have been in a position of a forum ban before and it doesn't feel good. It can even cause you to lose a lot of motivation and lack of motivation can cause someone to give up/go even more downhill, and everyone deserves a shot at achieving their dream.

I kindly suggest that the staff make a group PM with anyone involved in the disagreement that caused the mess so they can put things in the past, and allow them to have another chance without problems being caused.

There is no point with people with the same goal (to stop malware and help people stay protected) leaving things on bad terms. It isn't healthy for anyone!

There does not need to be conflicts between developers, so to avoid them developers could stick to their own products and not talk badly about others. That could do the trick and keep the place calm and friendly.

Trust me it will be nicer if conflicts were addressed by people involved and amends are made for everyone

Thank you.

 

sorry where do we go to keep up to date with updates?

 

+1

 

This thread needs to be taken over by the moderator and post only pertinent info about VS and update procedures. It's presently very confusing with so many posting different ideas and solutions. If Wilders is going to continue the thread, please at least make it work more clearly for us.

 

Or better yet, go to MT.

 

Unfortunately, this lack of direction is inevitable since the developer of VS is persona non grata at present. If Dan wants to communicate with his users he's been given some acceptable alternatives here and elsewhere. Hope he decides on a new home soon.

 

I'm on both...

 

Whatever happens it's essential this thread stays open.

We need this communication channel... now more than ever.