Not sure if there are many/any podcasts about digital gardens and tangential topics, but I’ve started a tag on Huffduffer for those who’d like it for discovery or adding those they find themselves: https://huffduffer.com/tags/digital+gardens
If you find a podcast with some discussion about the topic, feel free to use Huffduffer’s bookmarklet to add it to the public list. This should also work with YouTube videos and it will convert the video into audio and save it to the list.
“To be transformed by a book, readers must do more than absorb information: they must bathe in the book’s ideas, relate those ideas to experiences in their lives over weeks and months, try on the book’s mental models like a new hat. Unfortunately, readers must drive that process for themselves. A...
I would like to have a one-click subscribe podcast feed that contains interviews with people I follow on Twitter — new releases and periodic highlights from the past. That’d be quite easy to build on top of the ListenNotes API. Anything to shift away from the “latest episodes” feed as the default, argh. Has someone done this? Breaker? ❧
You might be able to cobble something like this together with huffduffer.com using tags and some clever searches.
Annotated on August 15, 2020 at 11:04PM
Replied toa thread by pkamb and Kicks Condor (Hacker News)
pkamb :
> I use it to follow people
This is something I have a real need for. Specifically, podcast hosts. I want to follow certain hosts and listen to every random show they're on.
Some hosts do keep lists of their appearances across many shows: http://hypercritical.co/about/appearances/
But that forces me to manually find the episodes and add each one to my podcast app.
I want something that aggregates appearances into a cross-podcast RSS feed that I can subscribe to in my app. Automatically subscribe to every one of their appearances.
Kicks Condor:
This is a brilliant concept. Hosts could keep a feed of their appearances, but it would be interesting for someone to make a site that tracked this sort of thing (using user-submitted links I suppose).
https://huffduffer.com/ is another good discovery/bookmarking tool for podcasts. It has RSS feeds for everything on the site including custom searches that could potentially pick up your favorite contributors. The bookmarking functionality also makes it easy for you to quickly add things you find to one or more followable feeds for the one-off guest appearances you may hear about.
Someone took a nice photo of me recently. I'd like to use it as my avatar photo everywhere to present a consistent image. This is not easy to do.
I've had to manually change it on a dozen different Slacks, a bunch of social networks, a few forums, all my email accounts, and I'm still not done.
I jus...
Gravatar has some not-so secure issues relating to privacy that allow reverse lookups which isn’t good and could potentially leak information people don’t necessarily want to release.
My favorite solution to this problem and a few related others (like updating my bio and where you can find me on social media) is the meta data route using something like Microformats. Since I provide an h-card on my website’s homepage, it should be relatively easy for any service to take my URL as my identity (rather than one of my thousands of email addresses) parse my page and find my name, photo, bio, etc. and display them.
Nearly every social silo on the planet wants all of these details, so why should I need to incessantly have to input them manually much less keep them up to date? And I’ve yet to see a social service in the wild that hasn’t asked for my URL, so it’s obviously pretty universal.
Jeremy Keith‘s Huffduffer is a great example of something that already uses this data nicely. It doesn’t pull in my photo (though I think at one time he did have a set up that would poll Flickr avatars?) or my bio, but the “Elsewhere” section of my Huffduffer account lists where you can find me on dozens of social media accounts as well as my own websites. Huffduffer can do this because I gave it my domain name and the service parses my page looking for the rel="me" tags on my homepage. It could easily pull in my other provided data.
Incidentally Kevin Marks has also proposed a distributed verification system (remember the problem that Twitter had of attempting this?) that uses the rel="me" idea.
I’ll note that my own website will parse yours to pull in the author name, URL, and avatar to display a reply context for this response on my website! So hooray for microformats! (Though I’ll note that I did modify them a tad for my own idiosyncrasies.) My site does this with David Shanske‘s excellent Post Kinds plugin uses Parse This, which parses for microformats, JSON-LD, and then, if nothing is found it falls back to Open Graph Protocol. He’s been extending it lately to cover a handful of the bigger snowflake services like YouTube, IMDb, etc. to cover some additional edge cases that don’t have good mark up. Incidentally Aaron Parecki has a version of something like this called X-ray, which he uses for various things including microsub readers, not to mention the variety of other parsers available.
I’m sure there may be other versions of this in the wild, but it would be cool to see more social services provide functionality like this.
Pardon the English, parce que mon français est très mal.
You indicate at the bottom of the post (the rough English translation is mine)
Bonus : c’est bien plus facile pour moi d’ajouter un texte à wallabag (au hasard) que de stocker un fichier audio pour une « consommation » facile. L’audio me demande toute une mise en œuvre assez pénible, pas le texte.
Bonus: It is much easier for me to add text to wallabag (at random) than to store an audio file for easy “consumption”. The audio requires quite a painful implementation, but not so for the text.
If you’re a fan of Wallabag for bookmarking text for later, you might appreciate using Huffduffer.com for your audio. It has a simple bookmarklet that will pull audio files, text, and tags from webpages and save them to your account. Your account then has a variety of iTunes audio feeds that you can subscribe to in your podcatcher of choice so that you can listen to the audio at your convenience later. If your podcatcher supports it, you can play it back at speeds that suit you (vite, donc).
What follows may tend toward the jargon-y end of programming, but I’ll endeavor to explain it all and go step-by-step to allow those with little or no programming experience to follow along and use the tools I’m describing in a very powerful way. I’ll do my best to link the jargon to definitions and examples for those who haven’t run across them before. Hopefully with a bit of explanation, the ability to cut and paste some code, or even make some basic modifications, you’ll be able to do what I and others have done, but without having to puzzle it all out from scratch.
Most readers are sure to be aware of the ubiquitous “share” buttons that appear all over the web. Some of the most common are “share to Facebook” or “share to Twitter”. In my examples that follow, I’m doing roughly the same thing, but I’m using technology called webhooks and micropub to be able to share not just a URL or web address, but a variety of other very specific data in a specific way to my website.
This “share”–while a little more complicated–gives me a lot more direct control over the data I’m sending and how it will be seen on my website. I would hope that one day more social websites will have built in share buttons that allow for direct micropub integration so that instead of only sharing to corporate sites like Facebook, Twitter, et al. they’ll let people share directly to their own personal websites where they can better control their online identity and data. What I’m describing below is hopefully a temporary band-aid that allows me to keep using common social services like Pocket, YouTube, Meetup, Goodreads, Letterboxd, Diigo, Huffduffer, Reading.am, Hypothes.is, and hundreds of others but to also post the content to my site so that I own and control more of my own online data.
An example using Pocket
Following in the footsteps of Charlotte Allen and Jan-Lukas Else, I’ve been tinkering around with improving some of my syndication workflows for a number of social silos including Pocket, a social silo that focuses on bookmarking material to read later.
I have long used IFTTT (aka If This, Then That), a free and relatively simple web service that allows one to create applets that tie a large number of web-based and social services together, to send data from my Pocket account to my WordPress-based website. I’d done this using my Pocket RSS feed to create WordPress draft posts that I could then modify if necessary and publish publicly if I desired. Since I regularly use a number of Micropub clients in conjunction with the WordPress Micropub plugin and IFTTT supports webhooks, I thought I’d try that out as a separate process to provide a bit less manual pain in mapping the data for posts to appear like I want them to on my website.
Now I can use my Pocket account data and map most of it directly to the appropriate data fields on my website. Because Pocket has direct integration into IFTTT, I can actually get more data (particularly tags) out of it than I could before from the simple RSS feed.
Below, you’ll find what I’ve done with a quick walk through and some example code snippets. I’ll break some of it down into pieces as I go, and then provide a specific exemplar of some of the code properly strung together at the end. I’ll also note that this general procedure can be used with a variety of other silos (and either their integrated data or RSS feeds) within IFTTT to post data to your website. Those running platforms other than WordPress may be able to use the basic recipe presented here with some small modifications, to send similar data from their accounts to their sites that support Micropub as well.
Directions for connecting IFTTT to publish to WordPress via Micropub
Preliminaries
Install and activate the Micropub plugin for WordPress. This will give your website a server endpoint that IFTTT will use to authenticate and send data to your website on your behalf.
If you don’t already have it, install the IndieAuth plugin for WordPress and activate it. This will allow you to generate an authorization token (think password) with the appropriate scopes (think permissions to do specific actions on your website) to allow IFTTT to securely post to your website.
Within the WordPress administrative interface/dashboard go to Users >> Mange Tokens or go to the path /wp-admin/users.php?page=indieauth_user_token on your website.
At the bottom of that page under the section “Add Token” add a convenient name for your new token. You’ll see in the following screencapture that I’ve used “IFTTT for Webhooks”. Next click the check boxes to add scopes for “create” and “media”. Finally click the “Add New Token” button.
On the resulting page, copy the entirety of the returned access token in a safe place. You’ll need this token later in the process and once you’ve navigated away from the page, there’s no way to retrieve the token again later. The same token can be used for multiple different recipes within IFTTT, though one could create a different token for each different recipe if desired.
Sign up for an IFTTT account (if you don’t already have one).
Be sure to change example.com to the appropriate URL for your website. If you’re using a platform that isn’t WordPress in combination with the Micropub plugin, you can quickly find your appropriate endpoint by looking at your homepage’s source for a <link> element with a rel="micropub" attribute.
Method:POST
Content Type:application/x-www-form-urlencoded
More advanced users might experiment with other content types, but this will naturally require different data and formatting in the Body section.
Body:
The Body portion is one of the most complicated portions of the operation, because this is where you can get creative in how you fill this out and the end results you end up with on your website. You can use the available variables in the recipe to custom create almost anything you like and some services will give you a tremendous amount of flexibility. I’ll walk through a handful of the most common options and then tie them all together at the end. Ultimately the Body will be a string of various commands that indicate the data you want to send to your website and all of those commands will be strung together with an ampersand character (“&“) between each of them.
There are some small differences you may want to experiment with in terms of what you put in the Body field based on whether or not you’re using the Post Kinds plugin to create your posts and reply contexts or if you’re not.
Depending on which pieces you choose, I recommend doing a few test runs for your applets to make sure that they work the way you expect them to. (The Micropub plugin has a setting to mark incoming posts automatically as drafts, so you’re not spamming your readers while you’re testing options if you’re testing this on a live site.) Sometimes formatting issues (particularly with setting a publish time) may cause the post to fail. In these cases, experiment to find and excise the offending code and see if you can get things working with minimal examples before adding additional data/details.
For those who would like to get into more advanced territory with the programming and methods, I recommend looking at the W3C’s Webmention specification.
The first thing you’ll want in the Body will be your access token. This is similar to a password that allows the webhook to publish from IFTTT to your website. You’ll want a line that reads as follows with the AccessTokenHere replaced with the access token from your token provider which you created earlier and saved. You’ll want to keep this secret because it acts like a password for allowing remote applications to post to your website.
access_token=AcessTokenHere
Next will come the content you want to be published to your site.
I’ll mention that the content snippet can include almost anything you’d like using the variables provided by IFTTT as well as a reasonable variety of HTML. I’ve used it to add things like <blockquotes> for annotations and even <audio> tags for making listen posts or bookmarking audio with Huffduffer!
The following snippet tells your site what kind of content it’s receiving. Unless you’re doing something more exotic than bookmarks, likes, favorites, replies, or most post kinds (except maybe events), you’ll want to use the h-entry snippet as follows:
&h=entry
If you’d like your post to contain a formal title, then you’ll want to include the following code snippet. Generally with shorter content like notes/status updates, bookmarks, reads, likes, etc., I follow the practice of publishing titleless posts when they’re not required, so I personally skip this piece in most of my posts, but some may wish to include it.
&name=<<<{{Title}}>>>
To have your website create or use the correct category or tag taxonomies on your posts, you’ll want to have something similar to the following snippet. If you want to specify more than one category, just string them together with ampersands. If your category/tag has a blank space in it you can replace the spaces with %20. The Micropub server on your site should automatically check to see if you have categories or tags that match what is sent, otherwise it will create a new tag(s).
&category[]=Bookmark&category[]=Social%20Stream
I’ve found that in practice, some silos that allow for multiple tags will actually publish them via micropub using something along the lines of the following if the appropriate variables on IFTTT exist. In these cases, I append this to the other categories and tags I want to specify.
&category[]=<<<{{Tags}}>>>
If you’re using your Pocket account to send your bookmarked articles to read later, you’ll want to create a bookmark with the following line:
&bookmark-of=<<<{{EntryUrl}}>>>
Alternatively, if you were using your Pocket account to archive your articles once you’ve actually read them, you could have IFTTT post these archived items as “reads” to your site by choosing the “New Item Archived” element in the Pocket portion of the IF set up process. Here you’d replace the above bookmark-of line with the following:
&read-of=<<<{{EntryUrl}}>>>
If you were creating different sorts of posts you might also use the appropriate alternate verbiage: like-of, watch-of, listen-of, rsvp, etc. (find details for the appropriate mark up on the IndieWeb wiki or the correct microformats v2 property within the code for the Post Kinds plugin). If you are using the Post Kinds plugin, this is the piece of data that it receives to specify the correct post kind and create the reply context for your post and will likely preclude you from needing to send any data in the content portion (above) unless the services applet will let you send additional commentary or notes that you want to appear in the body of your post.
Next, if your site supports syndication links with a plugin like Syndication Links for WordPress, you would use the following line of code so that those are set and saved properly. (This presumes that the URL specified is the permalink of the content on the social silo. I’ll note that Pocket doesn’t provide these (easily) as most of their links are canonical ones for the original content, so I don’t use this on my IFTTT recipe for my Pocket workflow, but I do use it for others like Huffduffer and Reading.am. It conveniently allows me to find copies of my content elsewhere on the web.)
&syndication=<<<{{EntryUrl}}>>>
If you’d like to have the timestamp on your post match the time when you actually bookmarked the item in Pocket, you’ll need to add the following line of code. Without this line, the publication time will match the time of the Webhook action, which for most IFTTT things can be a delay of a minute or two up to an hour or more afterwards. In practice, I’ve noticed that most content posts to my website within about 10-15 minutes of the original, and this is based on the polling lag within IFTTT checking your triggers. (Sadly, I’ll report that I’ve never gotten this code snippet to work for me in practice, and I suspect it may be because the time format from IFTTT doesn’t match what is expected by the Micropub server on my website. Perhaps David Shanske or Ryan Barrett may have a more specific idea about what’s causing this or suggest a fix? I’ll try to dig into it shortly if I can. As a result, I generally have left this snippet of code off of my triggers and they’ve worked fine as a result. Until this issue might be fixed, if you want to have the exact timestamp, you could alternately include the data, if provided, in the content section instead and then copy it over manually after-the-fact.)
&published=<<<{{EntryPublished}}>>>
If you’ve got syndication endpoints set up properly with something like the Syndication Links plugin, you can use the following sort of code snippet. I generally eschew this and prefer to save my posts as drafts for potential modification prior to publishing publicly, but others may have different needs, so I’m including the option for relative completeness so people can experiment with it if they like.
&mp-syndicate-to[]=twitter-bridgy
This concludes the list of things that might commonly be included in the Body portion of the IFTTT applet. Tying these all together for combination in the Post Kinds Plugin one would want something along the lines of :
Here’s another example of the code I use in conjunction with a similar applet for Diigo, a bookmarking service. The “Description” portion allows me to add a note or comment on the bookmark when I make it and that note is transported over to the post on my website as well.
Note that when the string of commands is done, you do not need to have a trailing ampersand. Most of the examples I’ve used are from the Pocket set up within IFTTT, but keep in mind that other services on the platform may use alternate variable names (the portion in the braces {{}}). The differences may be subtle, but they are important so be careful not to use {{EntryTitle}} if your specific recipe expects {{Title}}.
To finish off making your new applet, click on the “Create Action” button. (If necessary, you can test the applet and come back to modify it later.)
Finally, give your applet an appropriate tile and click the “Finish” button. For my Pocket applet I’ve used the name “Pocket bookmark PESOS Micropub to WordPress”.
Now that your applet is finished, give it a whirl and see if it works the way you expect! Don’t feel discouraged if you run into issues, but try experimenting a bit to see if you can get the results you’d like to see on your website. You can always go back to your applet recipe and modify it if necessary.
Conclusion
Hopefully everyone has as much fun as I’ve had using this workflow to post to their websites. It may take some patience and experimentation to get things the way you’d like to have them, but you’re likely to be able to post more easily in the future. This will also let you own your data as you create it while still interacting with your friends and colleagues online.
I know that it may be possible to use other services like Zapier, Integromat, Automate.io, or other similar services instead of IFTTT though some of these may require paid accounts. I’d love to see what sorts of things people come up with for using this method for owning their own data. Can you think of other services that provide webhooks for potential use in combination with Micropub? (Incidentally, if this is your first foray into the Micropub space, be sure to check out the wealth of free Micropub clients you can use to publish directly to your website without all of the set up and code I’ve outlined above!)
Currently I’m using similar workflows to own my data from social services including Pocket, Diigo, Huffduffer, Reading.am, YouTube, Meetup/Google Calendar, and Hypothes.is. I’ve got several more planned shortly as well.
Thanks once again to Charlotte Allen and subsequently Jan-Lukas Else for the idea of using Micropub this way. Their initial documentation was invaluable to me and others are sure to find it useful. Charlotte has some examples for use with Facebook and Instagram and Jan-Lukas’ example may be especially helpful for those not using WordPress-specific solutions.
And as always, a big thank you to the entire IndieWeb community for continuing to hack away at making the web such a fun and vibrant space by making the small building blocks that make all of the above and so much more possible.
10 days ago I was sitting in a room in Los Angeles with 12 other folks listening to Marie Selvanadin, Sundi Richard, and Adam Croom talk about work they’re doing with Domains, and it was good! That session was followed by Peter Sentz providing insight on how BYU Domains provides and supports top-level domains and hosting for over 10,000 users on their campus. And first thing that Friday morning Lauren and I kicked the day off by highlighting Tim Clarke’s awesome work with the Berg Builds community directory as well as Coventry Domains‘s full-blown frame for a curriculum around Domains with Coventry Learn. In fact, the first 3 hours of Day 2 were a powerful reminder of just how much amazing work is happening at the various schools that are providing the good old world wide web as platform to their academic communities.
https://roadshow.reclaimhosting.com/LA/
I’m still bummed I couldn’t make it to this event…
One of the questions that came up during the SPLOT workshop is if there’s a SPLOT for podcasting, which reminded me of this post Adam Croom wrote a while back about his podcasting workflow: “My Podcasting Workflow with Amazon S3.” . We’re always on the look-out for new SPLOTs to bring to the Reclaim masses, and it would be cool to have an example that moves beyond WordPress just to make the point a SPLOT is not limited to WordPress (as much as we love it) —so maybe Adam and I can get the band back together.❧
I wonder if this could be used to create a SPLOT that isn’t WordPress based potentially using APIs from the Internet Archive and Huffduffer? WordPress-based infrastructure could be used to create it certainly and aggregation could be done around tags. It looks like the Huffduffer username SPLOT is available.
–annotated December 17, 2019 at 10:46AM
I am hoping to have a simple (to use) podcast where I can record pieces of lessons that are problematic and potentially have student guests for Q/A. Is there a domain app/plugin that is simple to use? What are you using?
In addition to all the other great recommendations, and in part to expose the idea, if you want to go really low tech, there are a variety of phone apps that will record audio in .mp3 format. If you give it a flexible enough license, you can upload/host your audio with notes and other meta data for free on Archive.org. (OER podcasting anyone?)
Then to quickly generate a subscribe-able podcast feed, create a free Huffduffer.com account (using the class name perhaps?) and use Huffduffer’s browser bookmarklet to save your Archive.org posts to your account. Huffduffer can provide podcast feeds out of individual user accounts, collectives, and even by tags, so you’ve got a lot of flexibility in how you and students can subscribe to content there. As an example you can subscribe to a “community podcast” for the tag A Domain of One’s Own.
If you create a custom/unique tag for the class, students can record and tag their own content to create an audio conversation back and forth if desired.
Over the weekend I was looking at the latest additions to Huffduffer. I noticed that Xavier Roy was using machine tags to tag a reading by Richard Dawkins. What an excellent idea!
I set aside a little time to do a little hacking with Amazon’s API. Now you can tag stuff on Huffduffer with machine t...
After I wrote about the hoops I had to jump through to get Amazon’s API to output JSON (via XSLT), Tom detailed a way of avoiding JSON by using XML-RPC. That’s very kind of him but the truth is that: I like dealing with JSON and the XSL transformation is done by Amazon, not me; that wouldn’t b...
So when I wanted to find a Last.fm user’s profile picture—having figured out through Google’s Social Graph API when someone on Huffduffer has a Last.fm account—it made far more sense for me to use hKit to parse the microformatted public URL than to use the API method. ❧
So the secret to having one’s image appear in their Huffduffer account is to add a rel=”me” to one’s home page? What triggers the reparsing? I’m not seeing it pop up…
— Annotated on December 06, 2019 at 10:37PM
I keep thinking of new and creative ways to use Huffduffer. If you haven’t heard of it, or used it, let me explain what it does.
It’s a service that creates a personal podcast feed out of audio links you add to it.
Karin mentions a lot of great material here that isn’t always obvious about how one an use Huffduffer. The one thing she didn’t mention was what her handle on the service is so others can follow her or some of the discovery related uses of Huffduffer.
While most of my readers will see all of my Huffduffer activity here on my own site, you can also follow all of my audio bookmarking there as well if you wish.
As I was reading through some of the subscriptions in Aaron Davis’well-curated blogroll which I’m subscribed to via OPML Subscription in Inoreader, I was reminded that I should be following my own Huffduffer Collective. This is a feed of audio that comes from all of the accounts I’m following on Jeremy Keith’s awesome Huffduffer audio service. For those looking for a great method for discovering new and interesting audio content and podcasts, this is by far the best discovery service I know.
While finding content which others have bookmarked is an excellent discovery mechanism, I think that finding it by means of things they’ve actually listened to would be even more powerful. By saying you’ve listened to something, it means you’ve put some skin in the game and spent some of your own valuable time actually consuming the content and then separately posting about it. I wonder how Huffduffer might incorporate this sort of “listen” functionality in addition to their bookmarking functionality? I can’t help but thinking that more audio applications should have Micropub functionality for posting listens.
Here I’ll remind people that my website provides just such a feed of my own listens, so if you want to hear exactly what I’ve been listening to, you can have your own feed of it, which I call my faux-cast and you should be able to subscribe to it in most podcatchers. I do roughly the same thing for all the things I read online and off as well. I may bookmark something as interesting, but you know it was even more valuable to me when I’ve spent the time to actually listen to or read it from start to finish.
Do you have a listen feed I could subscribe to? Perhaps a Huffduffer account I should follow? How do you discover audio content online? How could this be used in the education technology space?
The most comprehensive podcast database online. Discover best podcasts. Search podcast show notes and audio transcripts by people, places, or topics.
An interesting looking service to be sure. Reminds me a bit of some of the functionality of Jeremy Keith’s Huffduffer, but it’s also a social silo of sorts for listening related content. It allows you to bookmark podcast episodes to listen later and includes an RSS feed for those so you can subscribe directly to your feed in a podcast player. It also does listen clips and comments. Sadly it doesn’t look like its got listen posts to allow you to keep track of what you’ve actually listened to. It does have an API for those who want to play around with it though.
Huffduffer.com – a service I with audio related content I find online. I use its bookmarklet to save audio from web pages. Huffduffer then creates a custom RSS feed that I can subscribe to in any podcatcher for catching up on podcasts while I’m on the go.
URL Forwarder– This is an Android-based app that I’ve configured to dovetail with the Post Kinds Plugin and my website for posting to my site more quickly via mobile.
Jon Udell’s media clipper– I use this audio/video tool for finding and tagging the start and stop points of media so that I can highlight specific portions for others