Fixed my very first "buffer underflow" since the 90s , refactored and improved code readability, doc comments, etc. I'm quite happy with the current status.

Next step: adding the logging system and removing all the debugging prints. Maybe I'll continue later, who knows...

As promised, here we go: #Goophy in action. As you can see it's approaching an usable status.

Next steps: refactor more code, add a logging system and start my own gopherhole to test it in a real case scenario.

You also know you're making progress when valgrind output looks like this:

==32514== All heap blocks were freed -- no leaks are possible
==32514==
==32514== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Stay tuned, later in the day I'll show you current project status

You know you're not making any progress if you don't get a Segmentation Fault once in a while

More progress done. Some code refactor here and there, some security things like avoiding access to not authorized files and paths, gophermaps already supported... not bad at all

Funny story of the day: I was testing the program and I was excited because everything worked fine. Suddenly I realized a thing was working but it shouldn't. Why was it working? Because the data I was using didn't cover that specific use case yet