Here are some general issues I experienced when using the framework:
No separate English language file. Where is English? I expected hgjs.lang.en.js as an example.
No use of HTML5 History API. You don't even need to use the History API to have a representative URL at all times. You even use it, but for some reason it clears as soon as the relevant page loads. ?
help <cmd> and no <cmd> --help. I would expect the latter to work (e.g. aliased to the former) and be promoted since it's the de-facto standard nowadays.
Mission "Tidying up", task 5: jump to home. With simply 'cd' it works but it doesn't register it. If one MUST use the absolute path, the task should specify so.
Mission "Let's crack some passwords", task 3: crack the pass by guessing? I wasn't told how to do that, how to try a pass? Task 2. only says I'll get a binary-file error, doesn't mention edit file pass.
"password2" assignment is too hard. What everything am I supposed to try by hand? Assignment could be better extended if dict accepted additional argument wordlist.txt that I could construct (given the insight from the Learn more page).
The task also says: "Crack the first password." Now which one is that?
| (pipe) is an absolute must. That way we could teach grep-ing files with long output, and such.
If currently in a mission, I can't change my mind and go to another mission.
F5 key (page refresh) clears everything. Should really be storing my progress in a cookie or localStorage!
English is hardcoded because it is the fallback language and because English sentences serve as keys for other languages. I would really prefer if it stayed this way whereever possible (but I really need a better translation model for pages, I agree)
this is a large issue and I think it causes some bugs ... I will look into it, thank you
it doesn't always but somethimes it is the only way to look into the command. what would you recommend?
agree, thank you
is the how to guess help missing? I will look into it. I listed the 'guess' password in the most common passwords list and hoped the user would try them. The error message is wrong, I agree and will change it.
you could extend the dict command. You are right, the user should know how this can be done. Also, you can crack any password you wish as first and task will be complete. It only counts how many passwords are cracked until now.
pipe is a must =) I wanted to implement it sooner but I didn't find the time
agree, this should be solved
agree and some code is already prepared to do so. I only need to find a good way to store completed tasks. Will do.
Here are some general issues I experienced when using the framework:
help <cmd>
and no<cmd> --help
. I would expect the latter to work (e.g. aliased to the former) and be promoted since it's the de-facto standard nowadays.edit file pass
.dict
accepted additional argument wordlist.txt that I could construct (given the insight from the Learn more page).|
(pipe) is an absolute must. That way we could teach grep-ing files with long output, and such.