test post 22jun2017 0809posting from micropublish.net.using the article form, which creates html tags that i don't want. and it stores the content i

n a different json format.wren code is checking for the existence of the html name=value in the json. if exists, then it's an article, which i don't care about in wren, since all wren posts, currently, should have a title. i may change this later.if it's an article, then i remove the html sent, but the problem with this is that sometimes, i DO create html tags within the markup. this is lame by micropub clients.whey would ... forget it.anyway, within the micropub client article form, i can put anything in the text input field for "name", which i assume maps to the title of the post. i don't need this text input field data because in my web publishing apps, such as wren, i include the title within the markup of the post. i let wren pull the title from the post. i see no need for separate form junk for the title.

update

jeesh. no way will i support the micropub spec within my tanager javascript editor nor within my web server-side client code.

i'll only support micropub within my server-side api code.

i removed the html tags but because the micropub client changed newlines to html br tags, when i removed the html, the markup become one lone string.

i would love to engage with the indieweb people in person to find out why they devised the spec like this. why don't they want their server code doing the formatting?

that's the beauty of my tanager javascript editor. it does not formatting. it simply sends the markup to the server in json, of course, and then the server formats the markup into html. then the server returns the formatted html back to the client in json. tanager parses the returned json and displays the formatted html in the right window pane. simple ass stuff.

let the server app do the formatting. how does a micropub client know what formatting commands i permit? it doesn't.

in my other web publishing apps, i have created several custom formatting commands and other power commands that get processed by the server code. i don't want or can't have that functionality in the client app.

whatever. at least the note form sends raw markup to the server. but the problem is that i think that editing is only done with the article form.

that could possibly render all micropub clients useless for me. it's possible that i might be able to use micropub clients only to create new posts (notes and replies in micropub parlance.)

micropub/indieweb does not edit notes. i think. only articles an be edited. i cannot believe that an option does not exist to disable html formatting within the micropub clients.

thus far, i prefer my json api. but i like being able to create a reply (webmention) from within woodwind.xyz feed reader web app. that's pretty cool.