Diva Limousine sues Uber, claims its reliance on contractors is illegal.
I wonder what percentage of their valuation is built upon screwing their employees out of benefits by calling them independent contractors?
Marco, your post about supporting rel=”payment” for Overcast made me start thinking about other potential solve-able problems in the podcast space. Now that you’ve solved a piece of the support/payment problem, perhaps you can solve for a big part of the “who actually listened to my podcast” problem?
In a recent article on the topic of Webmention for A List Apart, I covered the topic of listen posts and sending webmentions for them. In addition to people being able to post on their own website that they’ve listened to a particular episode, the hosting podcast site can receive these mentions and display them as social proof that the episode was actually listened to. In addition to individual websites being able to do this, it would be awesome if podcast players/apps could send webmentions on behalf of their users (either with user specific data like Name, website, avatar, etc. if it’s stored, without it, or anonymized by the player itself) so that the canonical page for the podcast could collect (and potentially display) them.
As a proof of concept, here’s a page for a podcast episode that can receive webmentions. Someone listens to it, makes a “listen post” on their site, and sends a webmention of that fact. The original page can then collect it on the backend or display it if it chooses. Just imagine what this could do for the podcast world at scale for providing actual listening statistics?
In addition to aggregate numbers of downloads a podcast is receiving, they could also begin to have direct data about actual listens. Naturally the app/player would have to set (or allow a configuration) some percentage threshold of how much was played before sending such a notification to the receiving site. Perhaps the webmention spec for listens could also include the data for the percentage listened and send that number in the payload?
The toughest part may be collecting the rel=”canonical” URL for the podcast’s post (to send the webmention there) rather than the audio file’s URL, though I suspect that the feed for the podcast may have this depending on the feed’s source.
If you want to go a step further, you could add Micropub support to Overcast, so that when people are done listening to episodes, the app could send a micropub request to their registered website (perhaps via authentication using IndieAuth?). This would allow people to automatically make “listen posts” to their websites using Overcast and thereby help those following them to discover new and interesting podcasts. (Naturally, you might need a setting for sites that support both micropub and webmention, so that the app doesn’t send a webmention when it does a micropub post for a site that will then send a second webmention as well.)
One could also have podcast players with Micropub support that would allow text entry for commenting on particular portions of podcasts (perhaps using media fragments)? Suddenly we’re closer to commenting on individual portions of audio content in a way that’s not too dissimilar to SoundCloud’s commenting interface, but done in a more open web way.
As further example, I maintain a list of listen posts on my personal website. Because it includes links to the original audio files, it also becomes a “faux-cast” that friends and colleagues can subscribe to everything I’m listening to (or sub-categorizations thereof) via RSS. Perhaps this also works toward helping to fix some of the discovery problem as well?
Thanks, as always, for your dedication to building one of the best podcast tools out there!
We've had some challenges using Hypothesis on PDFs in Google Classroom and Google Drive. This video shows exactly how to get around this problem and quickly get back to your web annotations.
Anyone who isn’t an expert on the internet would be hard-pressed to explain how tracking on the internet actually works. Some of the negative effects of unchecked tracking are easy to notice, namely eerily-specific targeted advertising and a loss of performance on the web. However, many of the harms of unchecked data collection are completely opaque to users and experts alike, only to be revealed piecemeal by major data breaches. In the near future, Firefox will — by default — protect users by blocking tracking while also offering a clear set of controls to give our users more choice over what information they share with sites.
John Eckman blogs here about Open Source, the Next Generation Internet, the Assembled Web, and Web Application Strategy, Design, and Development. He also works at Optaros.
I’m the CEO of 10up, a digital agency focused on designing and building compelling, content-centric experiences on open source platforms, especially WordPress.
Why is this blog called Open Parenthesis?
It’s meant to bring together two key concepts that have dominated my professional career – writing and coding:
1. Parentheses in writing are often used to insert explanatory text not directly related to the main point (see the wikipedia entry). (I did a PhD in literature & culture, and spent years teaching in a university English environment).
2. Parentheses in software development are used for a variety of reasons in different languages, but often they’re used to pass parameters to functions (or to indicate the parameters a function receives). (I’ve spent the last decade working in software development, specifically on the web).
The site’s called “Open Parenthesis” (the singular of parentheses) because the idea is that the conversation is open ended.
It starts an explanatory insertion (like this one), but it can’t yet be closed.
It resembles a function taking parameters, but we can’t yet close the parentheses because we don’t know yet what the possibilities are.
Finally, there’s also the notion of “Open” because I’m focused on open source software, as well as open-ness and transparency of conversation in general.
Dr. David Wiley is Chief Academic Officer of Lumen Learning, an organization dedicated to increasing student success, reinvigorating pedagogy, and improving the affordability of education through the adoption of open educational resources by schools, community and state colleges, and universities. He is also currently the Education Fellow at Creative Commons, an Ashoka Fellow, and adjunct faculty in Brigham Young University's graduate program in Instructional Psychology and Technology, where he leads the Open Education Group (and was previously a tenured Associate Professor).
As an academic, Dr. Wiley has received numerous recognitions for his work, including an National Science Foundation CAREER grant and appointments as a Nonresident Fellow in the Center for Internet and Society at Stanford Law School, a Peery Social Entrepreneurship Research Fellow in the BYU Marriott School of Business, and a Shuttleworth Fellow. As a social entrepreneur, Dr. Wiley has founded or co-founded numerous entities including Lumen Learning, Degreed, and Mountain Heights Academy. In 2009, Fast Company named Dr. Wiley one of the 100 Most Creative People in Business.
David was born and grew up in West Virginia. He is an active member of the Church of Jesus Christ of Latter-day Saints (the Mormons). He served a two-year mission for the church in Fukuoka, Japan, and now serves as bishop of a student congregation at Brigham Young University. David lives in Utah with his wife and five children and enjoys hiking, running, playing basketball, listening to and making music, and reading.
Primary blog at https://opencontent.org/blog/
I suppose it should cease to amaze me that educators are so far ahead of the curve on owning so much of their identities and content online. Many seem to be OG IndieWeb. I like the way his primary page sets up his identity and he’s owning at least all of his bigger article output. And then there’s a lovely blogroll on his blog page, with so many names I recognize and several more I’m going to have to add to my own.
As I look at his bio and see Degreed, it reminds me while shadowing Greg McVerry’s EDU 522 course, that I’ve been wanting to own more of my learning online. I’ll have to take a look again at how Degreed is set up from a UI perspective and see what I can glean from it, particularly as it takes data from multiple other platforms and pulls it into it’s own platform in a very PESOS sort of workflow. I wonder if Degreed might take personal websites as a source of content and then be able to add certifications? This might also fit in with using Webmention as infrastructure for doing badges and credentialing.
Webmention is the more modern specification now as some have mentioned. I wrote a piece on it in @alistapart recently which includes some background, UI examples, and links to more technical resources:
It is a small part of an #IndieWeb suite of open protocols including Micropub, WebSub, and Microsub for allowing site to site communication and interaction which goes to the broader scope of your question about RSS feeds and blogs. See also: Lost Infrastructure
I keep meaning to provide a better overview of it all, but this recent pencast overview captures a chunk of it. Aaron Parecki’s article Building an IndieWeb Reader captures some of the rest of the microsub/reader portion.