Yep, if the message is shorter than the pixels, the remaining pixels should be untouched.

Updated the full tests suite to use the same tests from the sample tests

• Python initial solution now has a type annotation
• For the full test, I switched to genereating some of the pixels, rather having them hardcoded
  • Full tests now also re-test the example test cases
• Python tests use the test framework outlined in the Docs

I removed it and put lorem ipsum text there instead for both Go & Python

Hi :)

• Initial solution for Python uses type annotations (msg: str, pixels list[list[int]])
• Added a note in the Bitmask Array section about thinking of it as bit replacing
• Kept a few 255 & 0's and added some more random color values in the Hello example and updated the tests to match

Thanks for all your feedback!

Cheers

ps: Hope you give Part 2 a try :)

edit: I'll make some time to apply some of the same feedback on Part 2 as well

Okay, I cleaned up the extra diagrams and added some more emphasis on insertion, and noted that the bitmask array is applied bit-by-bit to each color value one at a time.

If this still isn't good enough maybe we can text chat on Discord? I see you in the mods section so I can send you a DM if that's ok?

I can try to expand on this a bit more without completely giving away a solution

I've updated the python test cases to follow the framework outlined in the Docs.

The spoiler message was a work-in-progress description update I left for feedback. I ended up including it anyways in today's upddate, its the section - Least Significant Bit Explained

Hello!

Finally got around to addressing a couple things:

• Updated the example test case for "Hello" to match what's in the description
• Added another test case to the example tests
• Re-check the example tests in the full tests
• Updated the description to give a brief explanation of what a Least Significant Bit is

Link to part 2 added :)

Yes, it should be

Updated to be Go 1.18