Encoding matters. This caught us during our recent demo at CloudSummit: while submitting an emoji in an API request emulated using @devproxy.bsky.social we got a broken response. Turns out, emojis are utf-8 and need a proper encoding. Change the content-type to include the encoding and avoid errors.
1 / 2
Post image
Post image

Comments