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.
@ricmac In particular a lot of this type of open architecture already exists as plugins for @WordPress
http:/
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.
@davidmead, Not directly related, but in lieu of OwnYourGram, which is very solid, you might also want to take a look at https:/
@jackbaty There are many who are using Known as part of a "multi-site" solution: https:/
I'm actually using both WordPress and Known, depending on what I'm posting and why. Sometimes two is better than one, and it helps me have the best of all worlds. I also often use Known for posting from mobile quickly: https:/
@davidmead I'm curious what method you're using for syndicating to twitter that's causing this? That may be the better question to address. It's likely if you're having a problem, others will as well.
In the interim, you can find all the prior releases here: https:/
You might also find it easier to create a [child theme](http:/
I saw your note in the chat last night and had a good laugh as I feel exactly the same way though I suspect that instead of 10, it's sometimes more like 15.
I suspect that I'm still spending far too much time fiddling with WordPress on the small niceties particularly with regard to syndication, so before jumping ship, just remember: "the grass is always greener..."
I do like the subtle overhaul of the CSS and typography!
Doug, I suspect that you may be using something like OwnYourGram to attempt to import photos to WordPress. While it does generally work pretty well, you might also appreciate https:/
@Tamaracks There's no need to explicitly set a Post Format in WordPress as it will automatically be set based on the Post Kind setting in Post Kinds on initial publish. (You can also tweak them by hand if necessary, so for example when using the `note` kind it automatically sets the Post Format to `aside`, but I prefer to use `status`, so I replaced `aside` with `status` just under 'note' => array( in the code here: https:/
I also think @dshanske fixed the proper kind settings on micropub in the latest development branch of post kinds as well. https:/
@jimmymansaray I'm sure it's not an Independent Publisher issue. You might also ask Colin where he got it and if it had actually worked for him. I think I saw that snippet floating around last week. I think Colin has ultimately changed to the following instead: https:/
It adds the kind of date/time stamp you're looking for (or is modifiable with some research) and has the added benefit that micro.blog should ignore the time stamp and just import the_content() of your status update instead.
Honestly, I'd recommend going without a title if you can manage it. If you need something in your admin UI, you might try this suggestion as well: http:/
I notice that https:/
@Mercy They seem like completely different products to me.
Known is a CMS which allows you to own your data, then publish and syndicate it to multiple platforms (including uploading to Anchor). It doesn't have any audio creation or editing functionality. I have seen people using this and WordPress lately for small personal microcast "channels" which can be subscribed to or syndicated out to other social platforms.
Anchor appears to have some production and publishing tools as well as a distribution platform of sorts. It looks like the material you publish to your own station can be listened to for 24 hours, but then disappears unless you archive it to your account privately. Fortunately you can export your audio with a little bit of gymnastics, but it's not intuitive. This seems more like an ephemeral audio version of snapchat to me.
I'm curious what you're looking for in a minipodcast? I'm considering something shortly myself and have been looking at Anchor as well as Opinion2, Spreaker Studio, audioBoom, tryca.st, and even others as simple as using my LiveScribe Echo pen to record and then distribute via my Known or WordPress sites.
I like the ability to put URLs on crossposted versions as well.
If you include the ability to link to cross posted versions, particularly for hosted, be sure to include a u-syndication (microformat) class on it: see also: http:/
For those on WordPress, it would be nice if there were built in support for the Syndication Lins plugin https:/