# Test Post 15Jul2017

I place the article's title within the body of the post. I don't want extra HTML form junk, such as a text input field to accept title text.�

I'm typing this from Quill, but I'm using Quill's fancy editor, which I think is based upon medium.js.�

The problem with fancy browser editors like this is when I want to do something simple like bold text, I have to remove my hands from the keyboard and use the mouse to highlight the text which caused a pop-over menu of actions that I can choose, such as bolding the highlighted text.

For me, it's easier to type raw markup and use text commands for Markdown or Textile to bold text.

I don't think this post will work anyway. For some stupid reason, Micropub clients add HTML to the post when it's an "article" type of post. I don't like that. That's why I always choose the "note" type of post in Micropub clients because the clients send raw text.�

I can format MY article type of posts, using MY preferred markup methods in the Micropub client note type of posting form.

This post will probably fail. Either I'm not supporting the "article" type of post as defined by the Micropub spec because the JSON is different, compared to the "note" type of post. I don't understand why the JSON spec changes the location of certain keys or names, when the post type changes. I don't do that with my JSON API. Mine is simpler.

Or my Wren code will break on the Micropub "article" post because of the screwy addition of HTML that I DID NOT ADD.

Someday, I'll ask the IndieWeb community why Micropub clients do stupid things, such as convert newlines to the HTML br tag. I let my server code do that. I guess the CMS apps of IndieWeb users function differently.

end post.

Error

The post did get created at boghop, but the other files did not get updated, like mft.html, and this error occurred, I think, when my code tried to copy the post to the S3 bucket.

I think that my code did not account for special, funky, extended ASCII characters that got include in the post by the fancy JavaScript editor.

The post got created at the wren.soupmode.com development site too, and the other files got updated because I'm not copying to an S3 bucket.

The funky characters appear in the above post here. They need to be escaped in order for the post to make it to the S3 bucket, I assume.

HTTP/1.1 100 Continue

HTTP/1.1 500 Accepted
Server: nginx/1.4.6 (Ubuntu)
Date: Sun, 16 Jul 2017 00:56:37 GMT
Content-Type: application/json; charset=ISO-8859-1
Transfer-Encoding: chunked
Connection: keep-alive

{"description":"Internal Server Error", "nothing":"nothing", "status":"500", "system_message":"HTTP::Message content must be bytes at /usr/local/share/perl/5.18.2/Amazon/S3.pm line 272.\n", "user_message":"Runtime Error:"}