@pfefferle I saw https:/
@EatPodcast I'd suspect you could do this and it should work fairly well. Have you tried it yet?
I'm not a fan of shortcodes, but as I recall, WP has a shortcode that supports mf1 (but not mf2) mark up: https:/
#40031 (Consider Adding Web Annotations to WordPress) – WordPress Trac https:/
Mostly to provide some additional resources to the conversation I'll add the following:
Web Annotation Working Group's [https:/
Prior to the WPTavern post which motivated the conversation, there was a [https:/
Keep in mind that some of the standard is geared specifically toward browsers and browser vendors, though WordPress could certainly implement some of the pieces from the CMS side.
Old posts with no value set for `pf_forward_to_origin` are automatically forwarded · Issue #899 · PressForward/pressforward https:/
This has probably been present for a while, but I just noticed after turning on forwarding posts to the canonical URL by setting a time >0 in the forward settings: all the old posts in my database (prior to having PressForward) auto forward as a default back to their own URLs. This means that every X seconds (as set in the setting) pages on my site automatically reload (or are redirected to themselves) and this makes the site relatively useless to attempt to read. (This seems to be a follow on error not noticed in https:/
Users adding PressForward on preexisting sites are going to have a tremendous shock if this is the default.
A better option is that all old posts (prior to installation) should default to no-forward (or at least not forward if there is no value set for `pf_forward_to_origin` in the database. PressForward should, in my mind, ideally default to no-forward in all new future posts with the possible exception of posts generated specifically by PressForward's nomination/draft workflow to default to `forward`/`no-forward` based on a possible new setting option in addition to the time setting.
It would be nice if the portion for null/non-existent values of `pf_forward_to_origin` was fixed before 4.2.2 rolled out into the WordPress repository if it hasn't been pushed already.
Running 4.2.2 on WP 4.7.2
Congratulations again to everyone, as always, on what I think is surely one of the most valuable plug-ins in the entire WordPress repository.
OPML link not working · Issue #898 · PressForward/pressforward https:/
## What I tried/expected:
From the page `/wp-admin/admin.php?page=pf-tools` under the `OPML Link` tab, the instructions indicate:
You can share your subscription list as an OPML file by linking people to http:/
## What happened:
Visiting the indicated link throws the following error:
`Warning: Creating default object from empty value in /htdocs/example/wp-content/plugins/pressforward-4.2.2/includes/opml/object.php on line 48
1`
## Additional information:
I've got a handful of feeds, so I should expect something to appear. Is there a setting I'm missing somewhere? I know that there's a setting for the /feedforward RSS functionality/plugin, is there a similar one for OPML that I'm missing?
Running GitHub version 4.2.2, WordPress 4.7.2
@MailChimp @MailChimpStatus @MailChimp_API @MailChimpUX Can you help WordPress community out here with a response? https:/
I'm always happy to help! Especially someone who's creating some wonderful content I enjoy consuming.
For motivation on embeds, your site supporting oEmbed would allow others to more easily and prettily embed your content, say from your podcast on their site.
Since most people may not take the time and effort to properly credit you or your work, or even attempt to make their re-post of your work look nice, you can have some control of the repost yourself by custom creating embeds, thus if one were to put the URL to one of your podcast posts into their own website it would display the way you designed it rather than whatever poor result they may come up with themselves. So instead of me needing to view the source of your web page and cut and paste the URL for your audio and/or other portions (like the photo and description perhaps), I could just cut and paste the URL and get something preformatted that just "works".
It's somewhat like Twitter Cards (https:/
If you want to try some examples of other sites, there's a list and more details at https:/
Jeremy, no worries, it's not openly transparent unless you look at the html source of the page directly. WordPress has a nifty feature that if you add an .mp3 URL to the text field, it will automatically format it as a player (much like embedding a youtube video), in my case I used an <audio> element wrapped around a .mp3 URL which creates a slightly different player (based on the web browser implementation of the spec) with somewhat different functionality.
As for replying to multiple sites at once on Known, on a "reply" post you'll have one URL in a field by itself, then you can click on the "Reply to a site" link under the "New Status Update" box to add another box, and so on. Thus, this particular post will send three replies. One to your response about the media player, one to your question about multiple replies, and a third which I'm sending to my original post which preceded your reply, so that it contains a full chain of the replies. There's also a "Remove URL" link in case you add too many--I don't think the post will publish if you have empty reply fields.
If you look on the wiki, there's a thing called salmentions (salmon+webmention) which programatically checks all the replies to replies and syndicates one's response everywhere so that all the posts in a chain of conversation get webmentions to have a complete record of a conversation. Few sites do this yet in practice, but if you're diligent on Known, you can effect salmentions manually.
Jeremy, this seemed a little long for Loqi to handle, and seemed worth keeping for later, so my response is below:
I understand your situation and have been following some of the discussion about content ownership and reposting. I'm all about giving credit where it's due, and bend over backwards (as far as I'm technically able) to do so. (Wait until you see some of the chicanery I'm trying to pull of for simple bookmark posts...)
It's for that reason that I provided a direct link to the podcast itself in the post as well as a blockquote synopsis in an effort to advertise on your show's behalf. Embedding the mp3 directly on my page was done as a means of helping people easily "sample" the podcast to get them hooked, in which case they would need to subscribe directly to the source. (I also did it to make it easier for me to relisten to it later if I like.) I'm still trying to get Twitter Player Cards to work properly so that could be an additional avenue for sampling on POSSE copies.
Additionally, by embedding the mp3 (I could have scraped it and then hosted it myself, but really, what's the point of that? unless I really wanted to steal it and run advertising against it for myself), your hosting server gets pinged for the "listen" or for any potential downloads because it's being served directly from your site (and not mine), which presumably most podcasters are tracking for advertising purposes. (YouTube and other video hosters do this for embedded videos.)
What I did was not much different than what Huffduffer is doing in bookmarking audio from your podcast on its site. Huffduffer isn't hosting a separate audio file itself, it's hosting a pointer to your file on its site and also syndicating it via RSS and/or Apple iTunes to others who will ultimately stream it or download it directly from your server. In fact, given this, I'm just acting like a mini-Apple iTunes without as much functionality, but I'm only advertising your podcast and not hundreds of thousands of others.
If you did have sponsors, you would presumably also give them airtime in your podcast which would then be heard as well, and tracked by your own server as a stream start or download. I suspect if you had visual advertising on your site, I could/might also embed that so you get a ping for the page load on my site as well. :)
If you're not aware or need it for clients, WordPress gives you the ability to customize your site's ability to provide oEmbeds, so with/for advertisers, you could add text, media, and even a visual advertisement to the pages for your audio podcasts. Other WordPress sites (or sites that consume oEmbed data) that include your URL in their pages then re-render it as a "player card" which presumably pings your server with a "hit" thus giving you credit for the work. Here's an example of an oEmbed for another WordPress site at the top of this post: http:/
Perhaps I'm mistaken about the process, and you may be far more knowledgeable than I given your experience in the space, but I'm pretty sure that by embedding and not copying and hosting it myself, you should be able to garner the lion's share of the credit while I'm just serving as free advertising on your behalf.
As an alternate example, things are somewhat different in Marty's case of creating a separate piece of audio and copying and embedding it into his podcast as aaronpk's music didn't register a ping of any sort (other than possibly a webmention which only happened once), so aaronpk couldn't have monetized his audio the way you could have with a sponsored podcast.
Duplication of links upon update · Issue #45 · dshanske/syndication-links https:/
With v3.1.1 and relying on SNAP for POSSE, I'm noticing that after publishing and syndicating, if one comes back and edits a post and then updates it, Syndication Links regrabs the URL's and duplicates the links.
The first unedited version that is shown seems to be a plain http link and after editing/updating, the second duplicated link that is added automatically is an https version.
Manually deleting either of the included links from the Syndication Links box doesn't get rid of the links.
This duplication of the links only happens on posts which have been later edited/updated.
example: http:/
Here the Twitter and Facebook links, which are generated from SNAP, are duplicated, first as http and then again as https. As a test, the two other syndication links are non-SNAP generated links: huffduffer was manually inserted, and the WordPress one was generated from the WordPress Cross Post plugin, so I'm guessing it's an issue caused by the storage of SNAP links (which are https) versus Syndications Links' storage.
Colin and David, I've been a long time Feedly user myself and certainly feel your pain. (And in particular, I'm a bit irked that I can't seem to get Feedly to discover alternate RSS Feeds being broadcast from my site to provide consumers with more options about what content they'd like to consume from my site, see also: http:/
While slowly hacking away at IndieWeb philosophies, one of the big issues I've always hated was using an outside feed reader that wasn't directly integrated into my own site. I've played around a lot with woodwind.xyz which has some great IndieWeb features, but doesn't have the massive developer team behind it that Feedly does.
Recently while doing some alternate research I also came across the WordPress plugin PressForward that was originally designed for journalists and academics, but in short is actually a built-in RSS feed reader that you can self-host as part of your WordPress install. I've been loving its general functionality and also use it somewhat like a self-hosted version of Pocket/InstaPaper as well, so it serves multiple uses. While it may not have everything that Feedly does, it's incredibly functional, and better, it's open on Github with lots of documentation, so you could potentially add the features you want. I've written a bit more about it (including some useful links) here if you'd like to explore it a bit more: http:/
Like both of you, I'm always eager to hear of other options should you come across them.
Does this help? http:/
It would be nice if Known had a media interface like WordPress or other CMSs, but where there's a will, there's a way.
JetPack has shortcode support for recipes that adds some markup (schema if I remember). I'm not a huge fan of shortcodes, but I've been meaning to finish tweaking their code to add microformats markup too. https:/
https:/
Retrieve Running Time for listen and watch post kinds? · Issue #71 · dshanske/indieweb-post-kinds https:/
For sites like Soundcloud, ITunes, Netflix, youtube (if it's available) it would be nice to retrieve the "running time" of the music, show, film, etc. to display as a running time in the UI for listen, watch, and jam types (rather than the published/updated) for other post types.
Sample URLs
https:/
https:/
https:/
https:/
https:/
WordPress blueberry podcasts: http:/
When not scrape-able, allowing one to simply enter a 0:00:00 time and a finish time and letting it display the appropriate running time (without entering a date) would be useful for these types as well. (I'm presuming it requires dates to calculate currently as I haven't yet checked....)