For writing, I figured I'd just close-enough it and let 10C sort it out. Since we have editing abilities here, if it looks bogus for some reason, we can easily fix it.

If you don't allow arbitrary HTML in the 10C Markdown and can tell us what tags you use for what constructs, then we should be able to disassemble the HTML to more faithfully render as 10C Web would. Otherwise, could grab Markdown and render just as when writing.

//

@kdfrawg I think you can do any knife you want in checked luggage.

//

It was an announced change that they backpedaled on, unfortunately. I got all excited and picked up a compatible multitool for flying, and then, no dice. :(

// @kdfrawg

I'm also not a huge fan of CoreData - I hate how it tends to become a cross-cutting concern that infects the whole app - but in an app that might actually accumulate a pile of data if done one way, I'm not sure what I'd rather use. I mostly get to ignore it as an overkill caching layer in cases where all the real brains live on the server.

Oh wait, and Realm. Though I don't get what Realm gets you over CoreData; feels like just CoreData with a different class prefix.

The only one of those I'm familiar with is Alamofire. I considered it Sherlocked by NSURLSession and just use that now.

I was looking at third-party stuff for that. Mainly because the attributed text stuff is a pain. So far, I've just punted, as you've no doubt seen. :)

//

HTML might be more trouble than Markdown. Can you send us a parse-tree? >.>

//

I'm not using any third-party code yet. I suspect you'll get way past what I've done fast - I have too little time to put to it. :(

But hoping for a variety of clients here, and I have some ideas that should make this a different flavor of client than yours, most likely.

The more the merrier. :)

Oh no, switching from Italian to French? What is 10C coming to! ;)

//