We got Lily, a German Shepherd rescue, almost a year ago this month in the same situation. Hit by car with pelvis, legs, and ankle broken (while pregnant). She’s also awfully sweet too given her past trauma. But be prepared for all the shedding! #germanshedder #furminator
A Twitter List
I started a bit of the Twitter scavenger hunt for Equity Unbound early this morning by creating a Twitter list of people who have been participating thus far with the #unboundeq hashtag.
For those new to the Twitter scene in education, knowing about Twitter lists, how to build them, and how one can use them are an invaluable set of tools and experiences. I highly recommend you spend a few minutes searching the web for these ideas and trying it out for yourself.
For those who are already well-versed in the idea of Twitter lists (no cheating; you’re only cheating yourselves if you’ve never done this before), feel free to subscribe to it or use it to quickly follow your peers. (Teachers are busy people and the 50+ of us don’t need to spend an inordinate amount of time doing the aggregation game, particularly if you’re doing it manually and not somewhat automated the way I’ve done.)
I’m sure the list will grow and I’ll update it over time, so check back if you don’t subscribe or use the list in a tool like TweetDeck. Apologies for those I’ve managed to have missed, please send me a tweet reply, comment below, or just keep using the hashtag and I’ll be more than happy to add you.
Even if you subscribe to the list or quickly follow everyone on it, I’d still highly recommend you spend a few minutes scrolling back into the Twitter timeline for the hashtag for the course and read what is going on. You’ll definitely have a better idea of who your class, teachers, and personal learning network are.
Perhaps I’ll also start a planet or subscribe-able OPML list of RSS feeds for those in the class soon as well for those who want to follow along in their feed readers? If you’ve got a particular tag/category/other that you’re using to aggregate all of your Equity Unbound participation on your own website, let me know in the comments below as well. As an example I’m using the tag UnboundEq, so all the related posts on my site can be seen at https://boffosocko.com/tag/unboundeq/ or subscribed to via https://boffosocko.com/tag/unboundeq/feed/. Let me know what yours are.
If enough people are doing this, I’ll publish a subscribe-able OPML file to make it easier for everyone to use these without us all spending the time to track them all down individually and put them into our feed readers to keep up with each other.
Kevin, your comic really resonates, particularly for someone who’s got over 200 social media related accounts and identity presences in various places on the internet.
It reminds me of a line I wrote a few months back in an article about the IndieWeb idea of Webmentions for A List Apart entitled Webmentions: Enabling Better Communication on the Internet:
Possibly worst of all, your personal identity on the internet can end up fragmented like so many horcruxes across multiple websites over which you have little, if any, control.
Inherent in this idea is that corporate interests and others who run social sites can disappear, delete, or moderate out of existence any of my writing, photos, audio, video, or other content into the memory hole at any time and for almost any reason. And just like a destroyed horcrux, their doing so takes a bit of my soul (identity) with it each time.
A few years back, I decided to take back my own identity on the web and post everything of interest to me on my own website on my own domain first–a digital commonplace book if you will. Only then do I syndicate it into other communities, websites, or areas as needed. (Even this reply is on my own site before I syndicate it to yours.) As a result, I own a tremendously large part of my online identity (though even at that, a lot of it is published privately for myself or select small audiences).
I hope that as Equity Unbound continues and we explore the ideas of identity, public/private, and related topics, people might consider some of these ideas and implications and potentially work on expanding solutions for students, teachers, and the rest of the world.
I know of a few folks in the IndieWeb and WordPress communities like Ryan Barrett (with FedBridgy) and Mathias Pfefferle (with OStatus plugin) who are actively working on helping bridge the technology between websites and the Fediverse so that one could use their WordPress install as a stand-alone “instance” of Mastodon.
It already seems somewhat obvious that moving from Twitter to Mastodon is bringing along some of the problems and issues that Twitter users are facing, so being able to use your current WordPress (or other) website to interact with other instances, sounds like a very solid idea. In practice, it’s the way I’ve been using my website with Twitter 1 2 (as well as Google+, Instagram, Facebook and other social silos) for some time, so I can certainly indicate it’s been a better experience for me. Naturally, both of their efforts fall underneath the broader umbrella of the web standards solutions generally pushed by the IndieWeb community, so I’m also already using my WordPress-based site to communicate back and forth in a social media-like way with others on the web already using Webmention, Micropub, WebSub, and (soon) Microsub.
These federation efforts have got a way to go to offer a clean user experience without a tremendous amount of set up, but for those technically inclined, they are efforts certainly worth looking at so one needn’t manage multiple sites/social media and they can still own all the data for themselves.
Maybe like this?
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!
Thanks for this Nathan. I did write a somewhat longer response to a few critiques late last week that clarified my position. In some sense I wanted to raise the idea of version control and it’s power/value more so than to just add on another “requirement” on the permissions side.
That was such a depressing exhibit wasn’t it?
Here’s a good example: http://v.hierofalco.net/2018/08/23/weird-indieweb-idea-of-the-day-guestbooks/
There’s a mention from https://ramblinggit.com/ in the comments, but it’s incredibly difficult to find that mention or what it contains, because there isn’t a linked URL on the avatar that goes to ramblinggit.com’s (Brad Enslen’s) content. In this particular case, it’s probably the most important piece of content on the page because the post itself is about a theoretical idea or “blue sky”, while the mention itself actually puts the theoretical idea into actual use and provides a great example. Sadly as it stands this value is completely hidden because of the UI. In some sense hiding the mention is also potentially contributing to unnecessary context collapse within hierofalco’s post’s comments and lessens the value of the mention itself.
While I appreciate the UX/UI desire to limit the amount of data displayed in one’s comment section since it is rarely, if ever, used, there’s a lot of value in the bi-directionality of webmentions and how they’re displayed. I’ve suggested before that newspapers, magazines and journalism sites (not to mention academics, researchers, and government sites) might benefit from the verifiable/audit-able links from their material to the reads, likes, favorites, and even listens (in the case of podcasts). If the comments sections simply have an avatar and a homepage link to the original, some of this (admittedly) marginal value is then lost. What about when Webmention is more common? Sites could simply display avatars and homepage links without actually linking to the original location of the webmention. They might do this to imply an endorsement(s) when none exists and the viewer is left with the difficult task of attempting manual verification.
I do love the fact that one can facepile these reactions, but why not simply have the facepile of avatars with URLs that direct to the original reaction? To me these should ideally have a title attribute that is the sending account’s name wrapped with the URL of the original webmention URL itself. While these are seemingly “throwaways” for likes/favorites, I often personally post “reads” and “listens” that also have notes or commentary that I use for my own purpose and thus don’t send them as explicit replies. If the facepiles for reads & listens are avatars that link back to the original then the site’s admin as well as others can choose (or not) to click through to the original. Perhaps the site administrator prefers to display those as replies, then they have the option in the interface to change the semantic linkback type from the simple response to a more “featured” response. (I’ve documented an example of this before.)
The issue becomes even more apparent in the case of “mentions” which are currently simply avatars with a homepage. There’s a much higher likelihood that there’s some valuable content (compared to a like certainly) behind this mention (though it still isn’t a specific reply). Readers of comment sections are much more likely to be interested in them and the potential conversation hiding behind them. As things stand currently, it’s a difficult and very manual thing to attempt to track down. In these cases, one should ideally be able to individually toggle facepile/not facepile for each mention depending on the content. If shown as a comment, then, yes, having the ability to show the whole thing, or an excerpted version, could be useful/desirable. If the mention is facepiled, it should be done as the others with an avatar and a wrapped URL to the mentioning content and an appropriate title (either the Identity/name of the sending site, the article title, or both if available).
For facepiled posts (and especially mentions) I’d much rather see something along the lines of:
<a title="Brad Enslen" href="https://ramblinggit.com/2018/08/new-guestbook/"><img src="https://secure.gravatar.com/avatar/0ce8b2c406e423f114e39fd4d128c31d?s=100&r=pg&d=mm" width="100" height="100"/></a>
(with the appropriate microformats markup, of course.)
As an example, what happens in the future when a New York Times article has webmentions that get hundreds or thousands of webmentions? Having everything be facepiled would be incredibly useful for quick display, but being able to individually go follow the conversations in situ would be wildly valuable as well. The newspaper could also then choose to show/hide specific replies or mentions in a much more moderated fashion to better encourage civil discourse. In the case where a bad actor/publisher attempts to “game” the system by simply showing thousands of likes/favorites/reads, what is to prevent them from cheating by showing as many as they like as “social proof” of their popularity when the only backtrack record is an avatar and a homepage without the actual verification of a thing on a site if someone chooses to audit the trail?
Perhaps even a step further in interesting UI for these semi-hidden mentions would be to do a full page preview (or hovercards) in a similar method for how WordPress handles hovercards for Gravatars or they way the hover functionality works for links at
Going even farther from a reader’s perspective, I could also see a case that while the site admin wants to slim down on the UI of all the different types of interactions for easy readability, perhaps the reader of a comments section might want to see all the raw mentions and details for each one and scroll through them? Perhaps it would be nice to add that option in the future? As things stand if a site facepiles even dozens of mentions, it’s incredibly painful and undesirable to track their associated commentary down. What if there was UI for the reader to unpack all these (especially per reaction category as it’s more likely one would want to do it for mentions, but not likes)?
I hope that as you wean yourself away from Twitter that you regain the ability to do longer posts–I quite like your writing style. This is certainly as well-put a statement about why one should leave Twitter as one could imagine.
I remember those old days and miss the feel it used to have as well. The regrowing blogosphere around the IndieWeb and Micro.blog are the closest thing I’ve seen to that original feel since ADN or smaller networks like 10 Centuries and pnut. I enjoy finding that as I wean myself away from Twitter, I do quite like going back to some of the peace and tranquility of reading and thinking my way through longer posts (and replies as well). Sometimes I wonder if it doesn’t take more than ten minutes of thought and work, it’s probably not worth putting on the internet at all, and even then it’s probably questionable… I’m half tempted to register the domain squirrels.social and spin up a Mastodon instance–fortunately it would take less than the ten minute time limit and there are enough animal related social silos out there already.
As an aside, I love the way you’ve laid out your webmentions–quite beautiful!
I’ve been (slowly) pecking away at trying to own all of this type of data on my own website. It sounds like what you’re hoping for is a cross between Derek Sifford’s Academic Blogger’s Toolkit which has a pretty slick WordPress interface for looking up and importing references and David Shanske’s Post Kinds Plugin which allows one to create specific post types like bookmarks, reads, notes, highlights, annotations, etc.
I think if Academic Blogger’s Toolkit could create an internal database within WordPress and an interface to allow you to easily import/export it as well as use it within your own instance, that might be the simplest solution to have ownership over all of one’s reference data. The Post Kinds plugin would give you the rest including the ability to hide your posts as private just to you or others granted access on your site.
Like Greg McVerry, Ian O’Byrne, Aaron Davis, and others I use my own site like a commonplace book and store bookmarks of things I’d like to read as well as things that I have read, usually along with notes, highlights, annotations, and other marginalia that I think would be of use.
Perhaps by adding one or two extensions, WordPress could be the perfect platform for doing this type of work without reliance on external sites?
I’ve had this book and his others on my list for quite a while, but I’ve been worried that they may fall short like this. I’ve started his most recent one in the past few weeks prior to it’s release this weekend. Jeremy’s review makes me even more reticent.
Perhaps it’s better to stick with the better sourced materials within the topic of “big history” by David Christian and others?
I’m glad the video helped out.
I’ve been a big fan of the Post Kinds Plugin as well. Honestly I wished that WordPress had gone the extra mile and adopted something more like it when it was working on the Post Formats concept a few years back. I’ve written a bit about the Post Kinds Plugin in the past and perhaps you’ll appreciate some of those pieces, particularly the bookmarklet portions for desktop and details about mobile posting.
Because Post Kinds and Post Formats are not one-to-one or onto functions, doing the mapping in both directions is difficult, but when posting using a Post Kinds first method, you should be able to set the Post Formats you prefer. There are some useful defaults within the plugin, but they can be manually changed in the code available in the class-kind-taxonomy file in a relatively obvious way. In my case, while the mapping of “notes” to “asides” is a useful one, I prefer them to map to “status” for my current theme, so I just manually change that one word in the code to reflect my particular preference.
There’s a lot hiding under the hood if you want to tinker in the code. If you have issues or feature requests, I know that the developer David Shanske is very receptive to feedback towards improving the set up. (And similarly for almost all of the IndieWeb-related plugins which can be found on GitHub.)
Feedly and custom sharing
Apparently there were a bunch of us thinking and writing about feed readers and the open web a year ago last June. Several week’s prior to Richard’s article, I’d written a piece for Richard’s now defunct AltPlatform entitled Feed reader revolution (now archived on my site), which laid out some pieces similar to Paul’s take here, though it tied in some more of what was then the state of the art in IndieWeb tech.
Around that time I began tinkering with other feed readers including Inoreader, which I’ve been using for it’s ability to auto-update my RSS feeds using OPML subscriptions from the OPML files I maintain on my own website. Currently I’m more interested in what the Microsub specification is starting to surface in the feed reader space.
I’m not sure if he’s played around with it since, but, like Paul, I was using some of the Press This bookmarklet functionality in conjunction with David Shanske’s Post Kinds plugin for WordPress to make posting snippets of things to my website easier.
Feedly has a Pro (aka paid) functionality to allow one to share content using custom URLs.
While one can use the Share to WordPress URL functionality, I’d recommend the Custom Sharing feature. Using the Post Kinds plugin, one can use the following example URL to quickly share things from their Feedly account to their personal website:
One should change the URL to reflect their own site, and one can also change the word “bookmark” to the appropriate desired kind including “like”, “favorite”, “read”, or any of the others they may have enabled within the Post Kinds plugin.
I personally don’t use this method as it only allows one custom sharing URL (and thus allows only one post kind), and instead (again) prefer Inoreader which allows one to configure custom sharing similarly to Feedly, but doesn’t limit the number of kinds and the feature is available in their free tier as well.
In addition to some of what I’ve written about the Post Kinds plugin before, I’ve also detailed how to dovetail it with sharing from my Android phone quickly in the past.
Highlights and Annotations
Also like Paul, I was greatly interested in quickly creating highlights and annotations on web content and posting them to my own website. Here I’m using a modified version of the Post Kinds plugin to accomplish this having created highlight posts and annotation posts for my site. Next I’m utilizing the ability to prepend
http://via.hypothes.is to URLs on my mobile phone to call up the ability to use my Hypothesis account to easily and quickly create highlights and annotations. I then use some details from the outline linked below to capture that data via RSS using IFTTT.com.
Naturally, the process could be streamlined a lot from a UI perspective, but I think it provides some fairly nice results without a huge amount of work.
I will mention that I’ve seen bugs in trying to annotate easily on Chrome’s mobile application, but haven’t had any issues in using Firefox’s mobile browser.