How to Ask
Some people don't know how to do it yet...
1) In general
- It's not my job to figure out what you are trying to tell me
- It's not my job to figure out what you are trying to do
2) No meta questions
- "Hello can I ask you a question"
- "Are you online?"
- etc.
No, dont do that... Yes you can ask me a question and if I am online and not too busy I will answer you.
3) Exploits
- "I'm using the exploit but it does not work"
- "How to make the exploit work?"
- etc.
I don't know... EDB has thousands of exploits, Github has exploits, ... tell me the EDB-ID, the GitHub link or something like that and I might know what is going on and what you are trying to do. Also, tell me exactly what you are trying to do (what modification you have made, which technique you used, etc.)
4) Error Codes
- "I am getting a warning"
- "There's an error"
- "An error code gets displayed"
- "It's not working"
There are tons of error codes, warnings, debug messages and so on; it's not my job to guess which one you are facing so just tell me directly.
5) Source Code & Configurations
- "My code doesn't work"
- "The config doesn't work"
- "I applied the given config"
- "The source code / config should be fine"
Well... firstly, are you sure? Also, I can't check it and help you if you don't tell me. Messages like "it should work" or "I did it how they told me but it doesn't work" isn't really enough for debugging and troubleshooting.
6) Pictures
- Please send proper screenhosts and don't use your Samsung Galaxy S2 to take a picture of your monitor.
- Software for taking screenshots:
- Flameshot (Linux)
- Greenshot (Windows)
- ShareX (Windows)
- Snipping Tool (Windows, pre-installed)
- Software for taking screenshots:
- Don't send me a random picture without a context, I don't have the time to figure out what you want to show me.
7) Downloads
- Don't send me direct download links