@feedly @Inoreader @TheOldReader @reederapp @digg @NewsBlur @netvibes I wrote this for you: Feed Reader Revolution http://boffosocko.com/2017/06/09/how-feed-readers-can-grow-market-share-and-take-over-social-media/

@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.

@cdevroe I'll agree with Jeremy that you don't need to syndicate content or even backfeed to be a part of the Indieweb. Particularly when you're already doing the primary tenets: own your domain, own your data, publish on your own site. (Ideally this is what everyone should be doing in conjunction with webmentions and then all the social networks would be superfluous.)

@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.

This sounds more like an OGP problem relating to a social and/or SEO plugin (Yoast or All in One perhaps). Does Independent Publisher set meta tags with open graph protocol? I don't imagine it does.

If you view the source of the page (that does show the featured image in social media) you'll usually see something like the following in the header of the page:
<meta property="og:image" content="http://example.com/wp-content/uploads/photo_path.jpg">
This is the meta tag the social platform is likely pulling the image from.

It's possible that it's the case that the SEO/other plugin is automatically pulling the photo from the theme in one case but not the other. These plugins typically have settings to allow overriding the featured photo, using a default photo if one isn't specified, or not using one at all.

This sounds to me more like an issue with another plugin causing the problem and not the theme.

huffduffer and Not Huffduffer http://johnjohnston.info/blog/huffduffer-and-not-huffduffer

John describes an early experience with Huffduffer and then goes on to describe how he rolled his own version of something similar. While having your own tools is great, it does make it somewhat difficult to do the social sharing portion if you don't build that into the picture. I wish Jeremy Keith had been able to help him out as I'd love to have an idea of what John is regularly listening to and enjoying.

#podcast #discovery

Perhaps I'm not quite reading your meaning properly, but I'm curious about the portion about your having turned off comments. I also notice your link requesting to "Comment on this at Medium". Both seemed odd to me as some of the benefit of having an indieweb site is having things set up to have better two way communication with others, while still owning the and having control and agency over the conversation.

This being said, I have, however, been considering turning off generic public (and anonymous) comments in favor of receiving comments only via webmentions. I think the fact that users who wish to comment on my content needing to post it on their own site first helps cut down on the spam and poorly thought out me-too commentary.

To some extent I think this was the tremendous value of Tumblr's not having a native commenting system. In their paradigm, to comment on something, one needed to put their commentary into their own personal stream first to be able to push the comment to the receiver's site as a secondary action. The social consequences of this are much stronger in terms of cutting back on a lot of junk, spam, and personal attacks because it becomes personally identifiable as representing themselves first and foremost (especially on their own site). Some of the problems Twitter and others have stem from users not really owning their content or their identities on those platforms which makes it much easier to become a nameless/faceless bully.

In some sense I think of it by analogy as a "Christmas tree effect". One purchases a wonderful Christmas tree and only puts up the useful and pretty decorations on it because it's what they and others who visit will see in broad view--often even publicly through their window from the street outside their home. Very few will go out of their way to buy a shabby looking tree and festoon it with dreadful ornaments as it's something ugly that not only they see constantly within their own home, but which will publicly brand them as such to friends, family, and even outsiders within their community.

Separately, thanks for the example your site provides. There are many subtleties you've got within your theme that I've been slowly working my way toward as well. I appreciate the way you've laid out and delineated the content. I also love the idea of a microcast which is something I've been contemplating for ages, but have never gotten around to actually doing. Your version and conceptualization are inspiring me to take another hard look at actually doing something.

@schmarty Head's up on this week's podcast--the pages for Glow & Social Igniter are for defunct projects I moved over. Just ignore them.

A profound little post on "Social as Play" by Jeremy Cherfas https://www.jeremycherfas.net/blog/social-games

@MailChimp @MailChimpStatus @MailChimp_API @MailChimpUX Can you help WordPress community out here with a response? https://github.com/crowdfavorite/wp-social/issues/213#issuecomment-282094259

I'm curious what you've tried that you've now abandoned? I've tried a handful of methods and haven't been very happy with many of them myself.

JetPack's publicize is seemingly the simplest of the lot, but gives almost no control over the end result, so either you like it or you don't. Bridgy Publish plugin has gotten much better recently, but my theme has some quirks to it that need some work to get things there working smoothly. Most recently I've been using Social Network Auto Poster which has a huge number of POSSE targets, but also requires a lot of set up time and configuration (and also relies on other plugins like All in One SEO or Yoast to set appropriate Open Graph Protocol metadata so that versions that get sent to Twitter/Facebook display exactly what I want them to--and even then it's not always 100%. I've been tempted to try Keyring next, but I suspect it'll be much of the same convoluted dance.

If most of my readership wasn't hiding in the silos, I think I'd give up on POSSE too. I can't wait until the broader idea has completely taken over to the point that syndication is a useless function.