@nlafferty I know @jimgroom has used it and written about it: http://bavatuesdays.com/teaching-without-wordpress-exploring-the-known-world/

Tom, sorry for the trouble you're having. I can commiserate as I and many others are having the same problem you're encountering. Something went amiss with respect to the core "Like" (fka bookmark) plugin and the Known Reactions plugin somewhere after v0.9.2. It's this that is causing issues with Likes and Reposts. It's a Known issue (pardon the pun) which is documented here: https://github.com/idno/Known/issues/1753

Feel free to add your experience to the issue (which will also bring it back to everyone's attention again) and hopefully someone will figure out what is going on in the march to release v1.0 of Known. I suspect that the functionality in saving things to the database works, but that the output display is having issues as is the sending of webmentions so that they show up on other's sites.

Jeremy, I'm noticing that your likes still work properly and I know a bunch have had issues with them in Known v0.9.9. Which version are you running?

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. :)

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://stream.jeremycherfas.net/account/settings/tools/ and drag the bookmarklet button (which likely has your name on it) to your browser bar! Then when you're on a web page you'd like to respond to, click on the bookmarklet to pull up a slightly more sophisticated UI (pictured in link) that will allow you to share, reply, bookmark, RSVP, like, and repost as you prefer (depending on your plugin collection). When you choose the "reply" tab, the UI should have the "reply to a site" URL pre-filled for your convenience! Type your reply, choose syndication destinations, and click "publish".

http://stream.boffosocko.com/file/7c7d5dfebbb14f620d5595395e42ef1d/bookmarklet+UI.PNG

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://stream.jeremycherfas.net/content/statusupdates/ and http://stream.jeremycherfas.net/content/replies/.

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.

Here's another example of this superfeedr quirk in action:
https://indiechat.search.cweiske.de/?q=%22Why+we+built+Known%22

A few days ago, in part based on something that [Richard MacManus wrote](https://richardmacmanus.com/2017/06/22/openness-rivers-indieweb/) (and which may have prompted @scripting's response), I noticed that Inoreader differentiates between importing an OPML and subscribing to an OPML.

> # Importing an OPML
> If you import an OPML file in your RSS reader, you are creating a static copy of the reading list. If the owner of the original list updates the list, this change will not be shown in your feed collection.
>
> # Subscribing to an OPML
> An OPML subscription, however, creates a live connection between the original source and your feed folder. Whenever a feed is added or deleted from the original list, the change will be reflected in your subscriptions. The notification system in Inoreader will notify you that new feeds were imported or existing feeds were removed.

Ideally, if a site had a blogroll or other mechanism by which they maintained and publicly published their own OPML list, then the user could plug that into the reader to subscribe to the list which could update dynamically. One could also subscribe to others' OPML lists (or subsets of them?) as well without needing to pay attention to them. In total, this sounds like what Ben's reader (and Known's subscription list) were doing, but by using a pre-existing standard that's broadly supported. (As an example WordPress sites with the Links module enabled publish their OPML files at example.com/wp-links-opml.php).

I'm not 100% sure, but didn't I hear that he left out hosted Known in that data?? Which means it's even bigger?

Andreas, The best way I'm aware of to do read posts with #WithKnown currently is to post a status update to the effect. I've been considering doing a plugin similar to Jonathan LaCour's Watching https://github.com/cleverdevil/Known-Watching but for books. In fact, other than some cut and paste work and changing the microformats, it should be a simple thing. I'd almost feel guilty for "stealing" it.

I've started hacking away at a Read plugin similar to the bookmark or like functionalities that simply bookmarks articles which I've read online, but it's got some quirky upstream issues that need to be solved before I can finish it. Ultimately it's really for online content more so than books (or even magazines) though. I may circle back around to it sometime toward the end of the summer as I'm trying to finish up some last pieces on my Reading workflows for WordPress.

@BenjaminHarwood The best part is it supports cutting edge tech like webmentions & micropub out of the box as well as easy syndication to social media. It can also be quickly bundled with brid.gy to bring a lot of your social conversations back to live on your own website so you can use social media, but not rely on it being up forever. I also think it gives a better user experience on mobile as well.

While I love and use WordPress, I don't know what I'd do without Known.

Some of the issue is that WordPress has a huge number of plugins which adds a lot of additional complexity (especially for Micropub clients) which isn't always going to be handled by every client.

As for webmentions, they're being bolted onto WordPress which doesn't have (or allow) a custom comment type, so they're jury-rigged in the best manner possible. There is still ongoing work, especially with the Semantic Linkbacks Plugin which does a lot of the heavy lifting here, if you've got thoughts/ideas, you should certainly weigh in on those Github issues as they are evolving.

I know there were a handful of quirks that have been changed in Known in the past months to fix some issues with microformats that were being parsed incorrectly, and thus caused other platforms like WordPress not to let them display as nicely when received. I think most have been merged and a new release of Known was pushed yesterday and should hopefully clear up some of these issues. I think the developers of the WordPress plugins and even the Known community are very responsive, so feel free to jump in with feedback, suggestions, or even pull requests on any of the pieces which are all on GitHub.

I'm sure there will be some remaining rough edges, but in general a lot of them have been smoothed over in the past year and most improvements now seem to be geared towards making the suite of tools more user friendly or to better extend the functionality.