@jimmymansaray Your Twitter location lists you as in Pasadena! If you're free for coffee while you're here, I'm buying.
@macleodan You could also use Tumblr which could get you quite a way and it has reasonable export for moving in future if necessary.
@macleodan iirc, @jimmymansaray had same question last year. I know he looked at both @WordPress & @withknown.
Want to know what I've been reading lately? I post a steam of it on my own site here:
http:/
I suspect that markdown or semi-complicated html (like you, I occasionally like to do this too, even if it's just bold or italics) in replies are a second class citizen because most major CMSes (including Known) strip out or severely limit (for security reasons) the html that is accepted in comment fields. In fact, to conserve on space, I've even noticed that many even strip out blank lines between paragraphs! Many also will mark as spam comments that have one or more URLs in them. As a result doing fancy or even mildly complicated html or markdown in replies is something for which most platforms just don't build.
The other issue in status updates and replies is that they're often syndicated to other platforms and it's a more difficult issue to properly do this with each snowflake social media silo depending on how they individually handle html/markdown (or not). I do this sometimes in WordPress to properly format syndicated content, and it easily triples the amount of manual work, so be careful what you wish for. (This may also be the reason I love Known so much too!)
Every now and then I'll write an extended reply to someone's post that gets to the point that headings, additional structure, and the frills become much more valuable. In those cases, I'd probably then default to make them posts/articles and add the additional touches and then do a manual mark up of u-in-reply-to to have them show up as a reply instead of just a mention. This happens so generally rarely that it's not too much of a headache.
Either way, the end result on the other person's site isn't something I can ever control for, so I try not to sweat it too much. :)
Interestingly, I didn't get a webmention of your post (directly or via micro.blog), but came across it because I follow you either way.
I'm happy to throw in a spurious feed if you want to test it and see if it updates automatically, but I've also been adding a handful of new feeds a week until I can get things where I'd like them to be. Hopefully you find it valuable!
@taravancil Rel="me" cross linking also allows for distributed verification online as well:
http:/
The sound of your original post and the reply are making me think that you're manually opening up your site in a browser, clicking on the "Status Update" piece of the UI, then manually clicking on the "Reply to a site" button, and then manually cutting and pasting the URL in for replies every time. Does this mean you're not using the browser bookmarklet to generate all of your responses?!!
If this is the case, then hie thee to https:/
http:/
In some sense this will make your replies only replies, your status updates only updates, and your posts articles that can only mention other articles (unless you manually do what I'd done before). In the initial case I outlined above, you're manually creating statuses which technically get turned into replies by manually adding the reply URL. The difference can be seen in visiting/comparing the URLs http:/
I pray that you've known this all along, you'll forgive my "indiesplain", and that I'm not catching the subtlety of your original post. The Known bookmarklet is 90% of the beauty of the system and drastically cuts back on the manual 'til it hurts portion of the program. And of course if it doesn't make sense, let me know and I'll make a video of the process or we can do a screen share if necessary. I'm addicted to bookmarklets of all kinds, but realize that not everyone uses them the way (or to the extreme) that I do.
If not, I'm not sure I fully understand your original issue or why you'd want to create a new post (with a title) to do replies to others' content, and I'll have to revisit the issue you're having.
Why couldn't journalists use bigger publishers/aggregators as syndication partners this way? #POSSE
https:/