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:/
I view replies to be similar to notes in not needing/requiring titles.
For metadata it can often be useful to have an actual title in the admin UI to identify the post in those administrative views.
What I find even more interesting/useful is having the ability to put in a custom title for automatic POSSE purposes, and the title is often used by many (most? all??) POSSE plugins for just this. In this UX/UI case it can mean some of the content could be displayed multiple times, once in the title and again in the body, which isn't ideal.
I'm certainly in the boat that stripping the title is a theme issue. I'd argue that for the best possible broad usage, Post Kinds should strip it out (using CSS) as a default and allow those who'd prefer to display it on the front end, just untoggle the CSS setting.
If this is the case, then the final consideration is the duplication of content between the title and body within RSS as well.
Thrilled to be able to POSSE posts from @WithKnown to Mastodon now courtesy of @nxd4n using https:/
Can't wait to try POSSE from @withknown to Mastodon! #Indieweb https:/
@EduCaaS @pgonyan @Withknown es un proyecto que permite POSSE a Github https:/
Jonathan, perfect, the new version fixes the issues with the content showing on the permalink.
The separate, but somewhat related issue is that the post interface still shows all of the UI for syndicating to all of the options (facebook, twitter, WordPress, Tumblr, LinkedIn, etc.), yet choosing those options doesn't actually syndicate the content. (Typically I wouldn't POSSE these post types anywhere anyway, but other users may expect this piece to work if it's shown.) I know some post types in Known hide the syndication targets when they're not supported (ie, only audio related posts can be syndicated to soundcloud), but I'm not sure how these are done.
Interestingly, when editing these types of posts, the syndication targets (correctly) aren't shown in the editable version.
Replies not working · Issue #4 · dg01d/KnownPnut https:/
When trying to reply to a pnut post and syndicating to pnut, the post not only doesn't thread, but doesn't even post to pnut, nor does it return the permalink of the post.
Example:
Original: http:/
Manual POSSE: https:/
New silo: pnut.io · Issue #736 · snarfed/bridgy https:/
@dg01d has created a [Known plugin](https:/
He and @jeremycherfas were chatting on https:/
Instructions for adding a new silo: https:/
Testing the ability to POSSE posts to pnut.io via @WithKnown courtesy of @dgold.
#client71 https:/
@EddieHinkle Clicking through will show that the text in the Twitter card is a quote of the original, in some part a reminder to me about what it was I had listened to. (It also serves as an advertisement for the thing itself--I like to promote good podcasts.) Most often these posts are just an emoji indicating the post type with the title and source of the thing I listened to. Occasionally I'll add some bit of a reply or commentary and bury the true post type into the Twitter Card along with a quote from the original. eg: https:/
Once in a rarer blue moon I'll throw a snippet of commentary into the Twitter card, but not often. See also https:/
If you want to listen to what I'm listening to, you can subscribe to it via http:/
@EddieHinkle Looking back on it, I think that the Swarm App/Foursquare decided to send three copies, one for each of the photos I took on the checkin. I've never seen that behavior before. I'm not sure how it decided to arbitrarily add the mention of erteencouncil on the Tweet however. I suppose this is what happens when you accidentally put together a POSSE like this.
@EddieHinkle Thanks for the heads up. The weird part is that I didn't mean to posse it at all. Quirk in 4square perhaps?
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.