Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation
Thanks Richard, this reminds me that I've been meaning to delve back into some of the blogroll functionality hiding within my WordPress install. It's not as updated as it should be, but you can find mine at http:/
You're also sure to find a handful of interesting tidbits at http:/
If you're looking for a relatively full-featured RSS reader for WordPress, I highly recommend the PressForward [http:/
I don't think he'd linked to it, but Colin Walker has a "beta" webmention plugin he built for his functionality which is on Github: https:/
AltPlatform blogger Richard MacManus details how he's modifying his website to join the independent web. I'm tickled pink that he holds my site up as a quintessential example. (I'm hoping he's using it in the sense of the Latin word for five as I can name at least that many and even more that are better...) Of course, like Bernard of Chartres, I've only been able to see further because of giants like Matthias Pfefferle, David Shanske, dozens of other indieweb proponents, and the thousands upon thousands of folks in the WordPress community.
I'll check to see if it's the case with altplatforms' bug, but I've discovered that it's having Jetpack's commenting feature "Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment" activated that prevents the Webmention Form from appearing on the page. If I deactivate it, it not only appears properly, but shows up twice with the standalone plugin installed.
Incidentally it also causes issues on my 2016 theme where if one types too much in the enclosed field, the UI moves down and it becomes impossible to actually post the comment!
While I'm thinking about it, as an Indieweb-forward thought, would it be possible to put the Webmention Form at the top of the comment section instead of underneath it? While I'm (and I'm sure most of us are) receptive to comments in general, it would be nice to encourage others to own theirs at the top and then provide the default comment form underneath it. Just a thought...
I'll do some additional testing and report the bug to JetPack shortly.
"Medium hasn’t made it easy for publishers to leave with their full content..."
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:/
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.
This has been driving me crazy, so I stripped everything down and rebuilt from scratch. I'm not sure why it didn't show up before when I previously cycled through other plugins as the potential cause/conflict, but it appears that Automattic's [WP Super Cache ](https:/
Turning caching off on this particular plugin (or un-activating it altogether) allows the retrieve button to work properly. My JS skills are woeful and I'm not seeing anything on direct inspection that would cause this problem when it's enabled. If anyone has useful thoughts about the conflict, I'd love to hear them.
It appears that WP Super Cache hasn't updated since October, so it likely wasn't a change on their end, but rather a change when Post Kinds upgraded.
Another interesting piece that's related to webmention and feed readers is the <a href="https://www.w3.org/TR/micropub/">W3C Micropub spec</a> that I believe was released on the same day as ActivityPub. There are already feed readers like www.woodwind.xyz that allow you to not only subscribe and read your friends who publish to their own sites, but you can use it to micropub "likes" and "replies" to those posts directly from the reader and to publish them directly to your own website if it supports the micropub spec (and yes, there's already a WordPress plugin for that). These micropubbed posts can then, in turn, send webmentions from your own site to your friends' posts to be displayed as comments there.
More details on all of these and how they can interact can be found on the wiki at https:/
@AramZS I've double-checked and had cleared caches previously (which if not done wouldn't have forwarded as I'd had the forward value set to 0 before.)
I've cleared everything out and reinstalled the new .org version from the repository and am finding the same issue seems to persist. (Even testing in a new browser install.)
One thing I am noticing is that a lot of my older posts were actually imported into my self-hosted install from either other non-WordPress sources or an older WordPress.com account. When editing these which don't have any values set for `pf_forward_to_origin`, I notice that the UI default for PF is for them to `Forward` rather than the typical default of `Don't Forward` which I get for new posts.
I'm also noticing that these older posts have the original site's GUID set in wp_posts which means that they're being forwarded to those URLs (some of which don't exist anymore). I'll try to circle around and make a caveat note in the documentation of this for others who may experience it (and not know why).
Perhaps there's some other glitch in my database causing this? Since @regan008 has tested it and confirmed on your side (and the code looks correct to me), I'll throw in the towel. Since I've got to make some of these additional GUID changes (along with some others) in my database anyway, I'll just go in and add values for all these older posts so they're "forced" to work anyway.
Thanks, as always, for such continued work on a fantastic tool!
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.