It would be hard to view it any other way without the devs talking about it, which i am sure they will. The fact that it is all open source just makes me doubt that there is anything nefarious about it.
...presuming folks were required to view the source code before using it, or that they do. Most folks, even pool ops, just hurry up and compile to keep their systems from accumulating downtime. There have been numerous opensource exploits not caught until after damage has been done. While this wasn't implemented, it's very odd to not have some description there.
Look at it this way,
nobody to date has caught it. Imagine how many hundreds of thousands of potcoin could've been skimmed/stolen? Only 1 individual out of the userbase noticed this? Your point is wholly negated.
happy. There is no reason to not contribute to a good cause, or 1% donation to charity 1% goes to maintaining the coin(which is more like a premine if you really want to split hairs, but i still don't see anything intrinsically wrong with this).
"Contribute" usually carries with it the idea that it was voluntary and of your own decision making process. This code amounts to a tax/fee, if not outright theft since there's absolutely NO commentary about it in the code or online.
As long as the devs are honest with the coins. It will make or break the coin if they go this route. They will either be transparent and gain mucho respect or be shady and lose a lot of the community. Like i said, i doubt anything sinister is meant by this.
Honesty means you put the code in recently (which they did), and then announce it by explaining what it is. Or better yet, explain that you'd like to put such code in down the road and maybe make it an option set with a flag.
Instead they merely put it in without warning. That's DIShonest and pretty dumb. Another poor business move on their part.
At this point I would highly suggest that all folks using the Windows wallet cease use of it and put your wallet into cold storage until the windows code can be verified. Easy way to do this is take the code and compile it under windows. If the CRC matches then you're safe, if the CRC doesn't match then your windows binary was modified from the source.