@pvagner @benwerd @mapkyca @rMdes_ @andrea @mruncieman @_dgoldsmith @techlifeweb @nxD4n I'm tempted to offer a bounty to see if we can't fix/reconcile difference in bookmarks/likes in @withknown core & that in @kylewmahan's Known Reactions. cross ref: https://github.com/kylewm/KnownReactions/issues/17

For those interested in more and who know a bit of code, David's also got a "master class" on adding microformats to modern themes in his commit trail for updating/upgrading the TwentySixteen theme to be more IndieWeb friendly: https://github.com/dshanske/twentysixteen-indieweb/commits/master

While it isn't comprehensive and may not cover every eventuality for every theme, following along with his commits here will get you a long way towards better understanding microformats v2 use with WordPress. I think I've learned more about WordPress themes and microformats by following his changes here than anything else I've tried.

@CodingItWrong @jeremywsherman @wookiee @davedelong I keep meaning to install Wallabag which is an indieweb-esque open source project that's a Pocket replacement. Perhaps that's your cup of tea? https://github.com/wallabag/wallabag/

@andrea It looks like you're missing the Semantic Linkbacks plugin for WordPress. That should make your facepiles have actual faces and display much better. https://github.com/pfefferle/wordpress-semantic-linkbacks

How are you posting to Known? Using Quill or another micropub application? Do you have the WithKnown Twitter plugin installed? https://github.com/idno/Twitter That can help some of the display issues you're probably seeing.

I'm sure many in the IndieWeb chat (Slack, IRC, Web, etc.) can give you help if you need it. There's a main room, and #WordPress and #Known specific channels. https://indieweb.org/discuss

I'm out at the moment but am happy to help more later if you need it.

@MarkGraham, @InternetArchive had previously collaborated with WP Broken Link Checker https://blog.archive.org/2013/10/25/fixing-broken-links/.
Is there someone there who could nudge this suggestion which could increase submissions? #DtMH2017
https://github.com/ManageWP/broken-link-checker/issues/23#issuecomment-279230774

@Chronotope @palewire Here's a thread & code for an @internetarchive tweak for @WithKnown CMS (php):
https://github.com/idno/Known/issues/1610

@Chronotope @palewire I wrote a sketch for a fix for it, but it's not been taken up yet:
https://github.com/ManageWP/broken-link-checker/issues/23

@Chronotope @palewire While I'm thinking about it there's lots of great stuff at https://github.com/pastpages

@khurtwilliams POSSE for WordPress can be tricky in part because, compared to most other IndieWeb pieces for WordPress, there are multiple different and varying ways to do it. Using one method could potentially conflict with another depending on how you set things up, though I think these are relatively few.

Your best bet is to hop into the #WordPress channel of the IndieWeb chat https://indieweb.org/discuss and ask for help, particularly to discuss the specifics of what you'd like to do and what you expect.

In general, the more control and flexibility you want over the display of your POSSE posts, the more set up and work you have to put into it (e.g. SNAP), while the less control you have the more simple the set up (e.g. JetPack Publicize).

Things like Brid.gy publish functionality (or via the Brid.gy Publish plugin) can be more finicky for POSSE copies to silos because Brid.gy is parsing your site for the proper data to publish. (It does have a preview button built in to do manual tests if you need to.) This means that if your WordPress theme doesn't have the correct microformats markup (and often they don't), then you can get spurious results, particularly when it comes to crossposting photos.

Most of the main POSSE plugins and tech are very stable in fact, but they do require that you do a bit of reading and understanding what they do and don't do and what you can and can't control with them. Most all of them have GitHub repositories that you can post issues to and almost all the devs, maintainers, and community are happy to help you out and/or make changes to make the UI and documentation better.

As for backfeed from Brid.gy, it generally requires that the URLs of your post and the syndicated post have matching permalinks to be able to match the two up to send you the webmentions properly. You may have changed your settings, but one piece you appear to be missing is the Syndication Links Plugin which allows you to add u-syndication links to your posts so that Brid.gy knows which ones to send your responses to. Much of this is documented at https://indieweb.org/WordPress_with_Bridgy It also looks like you don't have either an h-card or the appropriate rel-me links on your pages for Twitter, Facebook, et al. Brid.gy is pretty well documented, so you may want to take a look at some of the options there directly. https://brid.gy/about If it helps, you can do a lot of interactive stuff with Bridgy by manually creating posts with specific html in your posts directly. Understanding how to do this can be helpful later when you switch to using a plugin to help automate part of those processes.

I'm sure I've got a few odd posts from ages ago when I tested things out, but when you say "I can also see from some of the failed posts on your website that you may experience the same issues." I'm curious which particular posts you mean? To my knowledge things I intend to syndicate out are currently working as I expect them to (aside from one quirk that occasionally spams the Indieweb chat with micropubbed posts which continually redirect, but that's specific only to me because of some experimental code I've been running). It is the case that I don't always syndicate everything to each and every silo target I could. I do very much pick and choose which things to syndicate to particular networks.

We'll help you get there yet!

Aaron, I suspect that the visible code <span class='p-author h-card'>Aaron Davis</span> which appears on your byline on your site is the result of the uf2 plugin https://wordpress.org/plugins/wp-uf2/ conflicting with your theme, which already has microformats baked into it. You should be able to disable that plugin without any ill effects for any other functionality while simultaneously getting rid of that visible span. If that's not the case, you might want to file an issue at https://github.com/pfefferle/SemPress.