In fact, creating large hex files could become complicated. Not because of a database issue, because one doesn't exist, but because of the size of the generated .txt file.

But even with a limit, unless it's very low, this type of issue could arise. The user could simply create multiple messages using parts of the code.

Now, that wouldn't be so practical, because it involves having to convert everything to text, and then recompiling it all. Especially for images and things like that.

But to minimize that temptation, you could set a character limit. What do you think of 1000 characters, is that reasonable?

Thanks for that tip.
I had never thought about it, nor noticed it.

I've already added my notes for future improvements.