I wasn't one of the downvoters, so I can only speculate.
However, it is site policy to include textual summaries of programming challenges. This policy was actually instated when Project Euler went offline for some time. So, the first thing you can do is include descriptions of the problem that you're trying to solve.
The next thing you could do is take some time to call out any concerns you have about your code. Were there any areas where you did the best you could, but weren't quite happy with your code? Mention them.
Lastly, on your Problem #68 question, you say
I know I name variables badly, but I'm a little lazy since I solve alone, you can however point this out too
That's a bit problematic from our point of view. It means that the code isn't your best effort. Good questions here have already put forth their best effort and yet, still fall short from your point of view. The answer "It's not as bad as you think. Looks good, ship it." should always be a possible answer to a question here. Obviously, if you know that your names need improvement, then that answer isn't possible and your code isn't ready for review.
It's also nice when titles say what the code does. Now, I realize this is sometimes difficult with programming challenges, but you can get creative.
For further reading on the topic, I recommend this meta.
How to get the best value out of Code Review - Asking Questions