I'm a holder, not a troll, and I also bothered to take a good deal of time to help solve some of these issues by donating a tutorial to this forum. I am not against anyone here. I am (and have been for a while) pointing out some really rudimentary things that need to be taken care of as soon as possible. I don't know how to program, so all I can do is write about what I guarantee will make for a better user experience.

Here is a dumb example you probably aren't aware of:
The wallet DOES NOT WORK when downloaded with Safari on a MAC. You absolutely must use another browser. If you don't use another browser, proper .config file or not, the wallet appears for a split second and then disappears. In fact, the system files needed to run the wallet won't even get created. There is nowhere to even put a .config file unless you use a browser other than Safari to do the wallet download. Are you going to tell me the problem is my ISP and network settings for that one?

That should be front page news, not buried in a tutorial somewhere for someone to discover after ripping their hair out. Better yet, fix the issue. Why is that even a problem? Do people have that same problem with other coins? I'd wager they don't. The last thing an even above-average person is thinking after downloading a faulty installation file is what browser he/she used to do the download, particularly when that browser is the default browser on a bazillion computers, like it or not. Following a poor Mac user figuring that one out on their own, the rest of the process of making a .config file is not as simple as just saving a text file, like it is on a Windows computer. People shouldn't need to go through that experience. It doesn't point to a rite of passage or a badge of honor they must "earn" to be involved in boutique crypto. It points to a faulty installation file that isn't as good as it could be (with just a little more work put into it). These are simple things that require a tiny bit of backtracking to fix. They should be fixed.