Seems strange that the dev seems to be keeping quiet on this, no? I’m not telling you to read every comment of every post, you can just skim the post titles. Then you’ll see multiple open issues and a few closed issues too going back 5 days to the latest BtS update.
Though I haven’t followed this project long enough to tell if this is just the way they normally behave.
Edit:
I’m back at my computer, so it’s easier to edit and add info now.
Some key points that have stuck out to me:
-
Previous version released in July only triggers 2 detections on Windows defender versus 29 for the most recent version: https://i.imgur.com/GIoH7eG.png
-
Users getting constantly pestered to update to the latest version: https://i.imgur.com/Oege3kU.png
-
Yeah, naturally, the dev is going to say it’s a false positive. Obviously. I’ve only mentioned that the dev has previously responded because some people barely skimmed through the issues and thought the dev simply hadn’t seen the latest open issue from only a few hours ago, when that is not the case.
You don’t say. And the developer they don’t trust pointing to some piece of code and telling those people who cannot understand it themselves that it’s not malicious achieves anything?
If it’s a false positive there isn’t even anything to show in the first place. Nobody but the antivirus vendors know for sure why something triggers a false positive.
It’s like a toddler telling you you’re changing their diapers wrong and expecting you to explain to them what you did wrong even though you did everything correctly and the toddler doesn’t know anything about changing diapers in the first place.
I guess it’s all a question of point of view and reference point. 💁 I can’t argue against your opinion on the other side.
I do agree though that from this point of view it also make sense.