A: Yes, if you use HzMod instead of NTR. Keep in mind however that FPS will be pretty bad, but you might say that some framerate is better than no framerate!
Q: Will you make a Mac/Linux/ port?
A: No, AutoIt can only compile stuff on Windows. Even if you somehow find a way to compile it on other OSes, it uses Windows-specific functions internally. Even if you replace these functions, both Direct2D and GDI+ are Windows-specific libraries. In order to make a Windows port, Snickerstream would have to be completely rewritten in another language.
Q: So then, can I run it using Wine?
A: You should be able to but no guarantees, so you're on your own if anything doesn't work.
Q: Will you add file uploading / CIA installing like kit-kat?
A: No. Snickerstream has been built with a "by streamers, for streamers" philosophy which means anything that isn't related to streaming or that cannot improve it in any way will be considered extra bloat and isn't going to be implemented. Besides, there are already many better ways to upload files (FTP or Nintendo's own SMB) or install CIAs (FBI, both locally, via URL or even via QR), so they are completely unneeded.
Q: What about input redirection?
A: I'm unsure as of now. You CAN already use any type of input redirection programs togheter with Snickerstream (I suggest you go with Luma's integrated feature, it doesn't require you to install anything else and has many different clients that support it) but, on the other hand, could be handy. Right now the main focus is to give you the best streaming performance ever with the most features, but I guess I might think about it in later versions.
Q: My antivirus sees Snickerstream as a virus!
A: Some antiviruses see EVERYTHING made with AutoIt as viruses, and usually crappy ones do that. You can see that it does nothing wrong to your system by looking at the source code posted here. Either add Snickerstream to the exclusions list or (recommended) change your antivirus because it's probably garbage, really.
Q: Can I stream screens outside my (W)LAN? / Should I open the ports used by Snickerstream on your router?
A: It's a technically supported feature but I strongly recommend you to NOT do either of these things. Unless you change the PcIpAddr value in the INI to an internal one used by one of your computer's network adapters (which kinda defeats the point of the first question) your stream will be accessible to everyone that knows your external IP address, which you might think isn't bad until you realize that NTR sends its frames as RAW JPEG data: a malicious user could send invalid or modified packets and interfere with it! As long as you stream inside your (W)LAN (aka, if you use internal IP addresses) you DO NOT have to port forward.
Q: Why can't I close Snickerstream using the window's close button?
A: Read the troubleshooting section in the wiki. If that doesn't help, set the loglevel to 3 and try to understand what's wrong. If that STILL doesn't help, check if it persists with other clients (mainly NTRViewer). If everything else fails, contact me and send me the log.
Q: I've got a neat idea for a feature! Can I tell you about it?
A: Sure, there have been already user-submitted features coded in so you're encouraged to do so! As long as it isn't outright impossible, it might make it in one of the next versions!