Parsing issue when trying to create post

[rcampoamor]

Looks like it is fine if the post doesn't have a category (like the first 2 below), but throws and 'invalid character' error after that. But wait, On the pond, doesn't have a BLAH: prefix...

2025/02/20 17:01:50 Creating The Scourge of Subdivisions
2025/02/20 17:01:50 Creating Newton, Palm and PSP
2025/02/20 17:01:50 Creating Book: Buying a Fishing Rod for My Grandfather
create post: invalid character '<' looking for beginning of value
2025/02/20 17:01:50 Creating On the pond
create post: invalid character '<' looking for beginning of value
2025/02/20 17:01:50 Creating Travel: Alaska

Also seems like it would benefit from some backoff/throttling because the back end seems to object to getting rapid-fire API submissions:
create post: Request: Post "https://write.as/api/collections/mobrec/posts": dial tcp [2001:4800:40a7]:443: connect: connection refused
2025/02/20 17:02:12 Creating Incredible Vanishing Nokia 6682
create post: Request: Post "https://write.as/api/collections/mobrec/posts": dial tcp [2001:4800:40a7]:443: connect: connection refused
2025/02/20 17:02:12 Creating More On Flock
create post: Request: Post "https://write.as/api/collections/mobrec/posts": dial tcp [2001:4800:40a7]:443: connect: connection refused
2025/02/20 17:02:13 Creating Video iPod Next Week?

[rcampoamor]

Looked into this further and the issue appears to be triggered if the first string it encounters in the content/body is a markdown image notation . Temporary workaround is to insert a string as the first part of the content/body (like "Update").