Bytes sometimes erroneously returned as string in API

[852Kerfunkle]

First, apologies if this isn't the correct repo to report this issue in.

I'm running into a problem when the bytes I'm storing are returned as a string by the API, I suppose because it kind of looks like a string.

Maybe a global option that allow some control over this behaviour could be nice to have. For now I'm just working around it.

Some examples:

Correctly returned as a hex string: 0000000000003c003c0047833c00c2c6 0000000000003c003c00c8823c00c7ca 0000000000003c003c00c0343c0046a3

"Incorrectly" returned as a string: 0000000000003c003c00385c3c003a66 0000000000003c003c0043733c004674 0000000000003c003c00450a3c003d1f 0000000000003c003c00372e3c003e30

edit

I just realised sometimes certain characters are missing from the string entirely, I'll try to give an example later.

[m-kus]

Bcd tries to decode utf8 strings, maybe it is the case