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
UI/UX: Publish default to Don't Forward unless PressForward functionality · Issue #936 · PressForward/pressforward https:/
## What happened
With PressForward installed/activated, the Site Options setting for "Seconds to redirect user to source. (0 means no redirect)" set to 1 or greater, and creating a new post (by almost any means including manually, API, micropub, and I suspect sources like the forthcoming Gutenberg interface) the drop down menu item in the Publish meta box to "Forward/Don't Forward" to item's original URL automatically defaults to "Forward".
## What I Expected
I would expect the Forward/Don't Forward setting to default to Forward _only_ when an item is created via the bookmarklet, through items entering the process via the RSS feeds, or from other PressForward specific functionality. All other posts should default to Don't Forward unless manually switched in the Meta box.
For posts created either manually or other automatic means from other sources (API, micropub, etc.) they default to Forward meaning that their URLs never resolve to view the page as they continually forward back to themselves in a never ending loop.
## Additional notes
With the Seconds to redirect set to 0, all new posts seem to be set to the default "Don't Forward" as one would expect.
@rachelandrew @sonniesedge @jensimmons If I had a commercial CMS, after Webmentions I would build in Micropub support: https:/
Cross reference: https:/
@BeakerBrowser Or if it had built in micropub support to my site like Omnibear does as a plugin for Chrome?
@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.
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:/
Manton, after having heard/seen your microcasts (and those of others) as well as your mention of podcasting tools above, I thought I'd point out that there's a micropub tool called Screech for podcasts: https:/
This bug mentioned in the micro.blog slack also makes it sound like posts coming in via micropub or other methods aren't automatically setting the post kind, which may be related to this issue:
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.
@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:/
@louisgray I hope that open W3C specs like Webmention and Micropub can help to turn the tide. #indieweb
OwnYourSwarm is awesome! #indieweb #FTW I love the fact that one can use the fantastically and cleanly engineered mobile UIs of services like Swarm/Foursquare and Instagram, but still also manage to own all of the related data (including GPS) on one's own website. Tools like OwnYourGram and OwnYourSwarm really show the power and value of micropub for the future of the internet.