I can't speak for others, but this is one of the many reasons that I have mostly switched away from windows. I don't own this laptop, so it's running windows, but my main machine only has windows in a VM. In Ubuntu, I have all the wallets that I use, which is a fair number, and I compiled all of them.
I'm going to learn how to do it in windows. I don't know when, as I have a lot going on, but hopefully before the next major update. Once I have it figured out, I'll post up a step by step guide for it here. It's fairly easy in Linux, but I imagine Windows has a number of deliberately difficult steps, because that's the nature of the beast. I'd like to be pleasantly surprised and find it as easy as Linux.
I have Linux machines too. I understand the relative strengths and weaknesses of each OS environment.
However, in my opinion, the just-use-Linux argument is not a valid response to the issue at hand - that issue being that the latest compiled Windows version of the TEK qt wallet has started to cause AV programs to reject it.
If, on consideration, the TEK team decides to make the coin Linux-only, then that is disappointing but fair enough, assuming an update to the OP spells it out.
Otherwise, Windows users are left waiting for a Windows fix or a (difficult to achieve) convincing explanation of safety. Your earlier comment that you know and have confidence in the person who compiled the code is reassuring, and you definitely carry gravitas with me - but then so did BFL before they became the BFL we all know and loathe today, and so did the Dyslexic Zombei team before they vanished with a lot of
BTC. My point is not to lump you in with scoundrels, but rather to remind that there is just no way to know on the Webz who is doing what to whom. This stuff must be as trustless as possible.
Using compiled code is already a risky proposition. Using compiled code that sets off AV alarms when it did not before is more risk than I am willing to accept. Watching all the responses that bob and weave and deflect and deny and generally avoid fixing the issue is... baffling. I like this coin. I want to use it again - on a Windows machine - without disabling AV.
I can't disagree with a single thing you said here. My earlier responses were more frustration than intentional bobbing and weaving. I don't know how to fix it, and I hate being in that position. I have no official ties to the development team. Thundertoe is a friend, and I have helped where I'm able. (and got compensated for it, though that was not my goal). But I'm an amateur programmer. No, that's overstating my skill. I'm a dabbler who would like to be an amateur programmer.
I don't know why the current wallet is triggering your AV. It's NOT triggering mine, but I've only got Windows Defender set up. As I said, this is a secondary machine. My argument regarding Linux was more personal than advice. I'm a long term Windows user. I've used it almost since it's launch, bumps in the road and all, and I had thought after the debacle of Vista that maybe Microsoft had learned their lesson. Seven was great. I still like it a lot. 8 and 8.1 make Vista look good. I finally gave up in sheer frustration and started using Linux. Since I'm not a gamer, it does everything I need and doesn't give me a lot of grief. I'm still learning it, but overall I've been far more satisfied with it than I was with Windows, even without nearly 20 years of experience using it.
Thundertoe has a hard time getting people to compile the windows wallets, and both of the current ones were compiled by volunteers. Again, both known to me. Presstab, while an excitable guy, is beyond reproach. Argakiig is also a good guy. I'm as certain as I can be that they would not put anything deliberately malicious in the code. But as you noted, you don't personally know me, and that's simply not good enough. Which is why I want to learn how to compile windows wallets and post up a guide for it. If you compile it yourself, you KNOW what's in it. It's not as convenient, but it's safer. And I'm starting to ramble, so I'll hang it up here.
People! How can I make POS diff/timeline chart?? Also transactions volume data needed, then may help to get clue - about when to unlock my wallet for staking next time? Can any one tell me how to get POS difficulty data for the time after the hardfork??
