Read Why You Should Never Pay For Podcast Hosting by Nir ZichermanNir Zicherman (Medium)
Thanks to modern cloud services, the cost of storing and serving content on the internet is incredibly cheap in 2018. With a podcasting platform like Anchor, there is no need for podcasters to pay anymore. So why are traditional podcast companies still charging creators to host files like it’s 2008?
He’s definitely got a major business behind this pitch, and he’s pitching people awfully hard to get them to give away all of their data for a “free” product. There’s the old adage though, “when the product is free, you’re the product.”

I’ve had friends online who’ve noted that this is at least the third time that Anchor.fm has “pivoted”, always seemingly to a larger and larger audience. I find myself wondering when the company is going to finally eat itself? Given that their product seems to change every six months or so, I also wonder if they last another 6 months?

Apparently he’s so bought into the idea of not owning your own data, that at least he’s posting this on one of the worst social silos out there. Just give it all away.

Reply to Sara Soueidan about front end development feeds

Replied to a tweet by Sara SoueidanSara Soueidan (Twitter)
I tinker on my own website and frequently write about IndieWeb related technologies because the web is my social media platform. The feed you might appreciate most is https://boffosocko.com/category/indieweb/feed/.

I have feeds for nearly every tag/category or post type on my site for convenience (just add /feed/ to almost anything). You could subscribe to my firehose feed, but I suspect even my mother would tire of it quickly.

I’m curious if you have OPML files or similar bundles of feeds you follow that are shareable or subscribe-able?

👓 Soon There Will Be Only One Blockbuster Left in the United States | The New York Times

Read Soon There Will Be Only One Blockbuster Left in the United States (nytimes.com)
The upcoming closings of two Blockbuster video stores in Alaska will leave one store in central Oregon as the last one in the United States.

👓 Columnist Retracts Harvey Weinstein Interview, Says Conversation Was a "Social Visit" | Hollywood Reporter

Read Columnist Retracts Harvey Weinstein Interview, Says Conversation Was a "Social Visit" (The Hollywood Reporter)
'The Spectator's' Taki Theodoracopulos quoted the disgraced mogul as saying, "Yes, I did offer [women] acting jobs in exchange for sex, but so did, and still does, everyone."
Aren’t “social visits” what got Weinstein in trouble in the first place? When is he going to learn?

👓 Community Review | Kathleen Fitzpatrick

Read Community Review by Kathleen FitzpatrickKathleen Fitzpatrick (Kathleen Fitzpatrick)
In my last book, Planned Obsolescence, I argued for the potentials of open, peer-to-peer review as a means of shedding some light on the otherwise often hidden processes of scholarly communication, enabling scholars to treat the process of review less as a mode of gatekeeping than as a formative moment in which they could learn from and contribute to their communities of practice. In Generous Thinking, my focus is somewhat different—less on the ways that scholars communicate with one another and more on the ways we invite the world into our work—but the emphasis on opening up our processes and imagining the ways that they might invite new kinds of conversations remains.

👓 Sourcing Content: Sara Sargent of HarperCollins Children’s Books on Working With Wattpad | Publishing Perspectives

Read Sourcing Content: Sara Sargent of HarperCollins Children’s Books on Working With Wattpad (Publishing Perspectives)
‘I’m now dedicating myself to doing things in a completely different way,’ HarperCollins Children’s Books’ executive editor Sara Sargent says, ‘combining a non-traditional way of sourcing books with traditional storytelling’ with Wattpad. Sara Sargent By Porter Anderson, Editor-in-Chie...
Finding material can be difficult and this certainly sounds like an interesting partial solution. Seems like there could be much larger solutions as well.

IndieWeb Summit 2018 Recap

Last week was the 8th annual IndieWeb Summit held in Portland, Oregon. While IndieWeb Camps and Summits have traditionally been held on weekends during people’s free time, this one held in the middle of the week was a roaring success. With well over 50 people in attendance, this was almost certainly the largest attendance I’ve seen to date. I suspect since people who flew in for the event had really committed, the attendance on the second day was much higher than usual as well. It was great to see so many people hacking on their personal websites and tools to make their personal online experiences richer.

The year of the Indie Reader

Last year I wrote the post Feed Reader Revolution in response to an increasingly growing need I’ve seen in the social space for a new sort of functionality in feed readers. While there have been a few interesting attempts like Woodwind which have shown a proof-of-concept, not much work had been done until some initial work by Aaron Parecki and a session at last year’s IndieWeb Summit entitled Putting it all Together.

Over the past year I’ve been closely watching Aaron Parecki; Grant Richmond and Jonathan LaCour; Eddie Hinkle; and Kristof De Jaeger’s collective progress on the microsub specification as well as their respective projects Aperture/Monocle; Together; Indigenous/Indigenous for iOS; and Indigenous for Android. As a result in early May I was overjoyed to suggest a keynote session on readers and was stupefied this week as many of them have officially launched and are open to general registration as relatively solid beta web services.

I spent a few minutes in a session at the end of Tuesday and managed to log into Aperture and create an account (#16, though I suspect I may be one of the first to use it besides the initial group of five developers). I also managed to quickly and easily add a microsub endpoint to my website as well. Sadly I’ve got some tweaks to make to my own installation to properly log into any of the reader app front ends. Based on several of the demos I’ve seen over the past months, the functionality involved is not only impressive, but it’s a properly large step ahead of some of the basic user interface provided by the now-shuttered Woodwind.xyz service (though the code is still available for self-hosting.)

Several people have committed to make attempts at creating a microsub server including Jack Jamieson who has announced an attempt at creating one for WordPress after having recently built the Yarns reader for WordPress from scratch this past year. I suspect within the coming year we’ll see one or two additional servers as well as some additional reading front ends. In fact, Ryan Barrett spent the day on Wednesday hacking away at leveraging the News Blur API and leveraging it to make News Blur a front end for Aperture’s server functionality. I’m hoping others may do the same for other popular readers like Feedly or Inoreader to expand on the plurality of offerings. Increased competition for new reader offerings can only improve the entire space.

Even more reading related support

Just before the Summit, gRegor Morrill unveiled the beta version of his micropub client Indiebookclub.biz which allows one to log in with their own website and use it to post reading updates to their own website. For those who don’t yet support micropub, the service saves the data for eventual export. His work on it continued through the summit to continue to improve an already impressive product. It’s the fist micropub client of its kind amidst a growing field of websites (including WordPress and WithKnown which both have plugins) that offer reading post support. Micro.blog has recently updated its code to allow users of the platform the ability to post reads with indiebookclub.biz as well. As a result of this spurt of reading related support there’s now a draft proposal to add read-of and read-status support as new Microformats. Perhaps reads will be included in future updates of the post-type-discovery algorithm as well?

Given the growth of reading post support and a new micropub read client, I suspect it won’t take long before some of the new microsub-related readers begin supporting read post micropub functionality as well.

IndieAuth Servers

In addition to David Shanske’s recent valiant update to the IndieAuth plugin for WordPress, Manton Reece managed to finish up coding work to unveil another implementation of IndieAuth at the Summit. His version is for the micro.blog platform which is a significant addition to the community and will add several hundred additional users who will have broader access to a wide assortment of functionality as a result.

The Future

While work continues apace on a broad variety of fronts, I was happy to see that my proposal for a session on IndieAlgorithms was accepted (despite my leading another topic earlier in the day). It was well attended and sparked some interesting discussion about how individuals might also be able to exert greater control over what they’re presented to consume. With the rise of Indie feed readers this year, the ability to better control and filter one’s incoming content is going to take on a greater importance in the very near future. With an increasing number of readers to choose from, more people will hopefully be able to free themselves from the vagaries of the blackbox algorithms that drive content distribution and presentation in products like Facebook, Twitter, Instagram and others. Based on the architecture of servers like Aperture, perhaps we might be able to modify some of the microsub spec to allow more freedom and flexibility in what will assuredly be the next step in the evolution of the IndieWeb?

Diversity

While there are miles and miles to go before we sleep, I was happy to have seen a session on diversity pop up at the Summit. I hope we can all take the general topic to heart to be more inclusive and actively invite friends into our fold. Thanks to Jean for suggesting and guiding the conversation and everyone else for continuing it throughout the rest of the summit and beyond.

Other Highlights

Naturally, the above are just a few of the bigger highlights as I perceive them. I’m sure others will appear in the IndieNews feed or other blogposts about the summit. The IndieWeb is something subtly different to each person, so I hope everyone takes a moment to share (on your own sites naturally) what you got out of all the sessions and discussions. There was a tremendous amount of discussion, debate, and advancement of the state of the art of the continually growing IndieWeb. Fortunately almost all of it was captured in the IndieWeb chat, on Twitter, and on video available through either the IndieWeb wiki pages for the summit or directly from the IndieWeb YouTube channel.

I suspect David Shanske and I will have more to say in what is sure to be a recap episode in our next podcast.

Photos

Finally, below I’m including a bunch of photos I took over the course of my trip. I’m far from a professional photographer, but hopefully they’ll give a small representation of some of the fun we all had at camp.

Final Thanks

People

While I’m thinking about it, I wanted to take a moment to thank everyone who came to the summit. You all really made it a fantastic event!

I’d particularly like to thank Aaron Parecki, Tantek Çelik, gRegor Morrill, Marty McGuire, and David Shanske who did a lot of the organizing and volunteer work to help make the summit happen as well as to capture it so well for others to participate remotely or even view major portions of it after-the-fact. I would be remiss if I didn’t thank Martijn van der Ven for some herculean efforts on IRC/Chat in documenting things in real time as well as for some serious wiki gardening along the way. As always, there are a huge crew of others whose contributions large and small help to make up the rich fabric of the community and we wouldn’t be who we are without your help. Thank you all! (Or as I might say in chat: community++).

And finally, a special personal thanks to Greg McVerry for kindly letting me join him at the Hotel deLuxe for some late night discussions on the intersection of IndieWeb and Domain of One’s Own philosophies as they dovetail with the education sector.  With growing interest and a wealth of ideas in this area, I’m confident it’s going to be a rapidly growing one over the coming years.

Sponsors

I’d also like to take a moment to say thanks to all the sponsors who helped to make the event a success including Name.com, GoDaddy, Okta, Mozilla, DreamHost, and likely a few others who I’m missing at the moment.

I’d also like to thank the Eliot Center for letting us hosting the event at their fabulous facility.

Reply to Ian O’Bryne on annotations

Replied to a tweet by William Ian O'ByrneWilliam Ian O'Byrne (Twitter)
Ian, thanks for putting together all of these examples. I think my preference is for option three which provides the most context and seems easiest to read and understand. I like the way you’ve incorporated the blue arrow, which makes semantic sense as well.

I’m sure I’ve seen other versions, but Jon Udell has at least one example of some annotations on his own website like yours too.

When it comes to the “conversation” side of what you’re looking for, I think the biggest piece you’re really missing and which some on the Hypothes.is side (except perhaps for Nate who may have a stronger grasp of their value after the recent IndiewWeb Summit) are apt to miss is that Hypothes.is doesn’t support sending webmentions. Presently you’re putting your data out there in a one-sided manner and Hypothes.is isn’t pushing the other side or any of the follow up back to you. As a result it’s operating as a social silo the same way that sites like Facebook and Twitter do. Based on their GitHub repository, I know that they’ve considered webmentions in the past, but apparently it got put on a back burner and hasn’t been revisited.

Ideally they’d want to have webmentions work in two places. It would be great if they could send webmentions of annotations/highlights to the original page itself, so that the site owner is aware that their content is being marked up or used in this manner. This also means that Hypothes.is could be used as a full-blown and simple commenting system as well so that those who aren’t using their own sites to write replies could use Hypothes.is as an alternative. The second thing it might want to do is to send webmentions, particularly for replies, to the original page as well as to any URLs that are mentioned in the comment thread which appears on Hypothes.is. This would mean that you’d want to add the permalink to your post back to the copy you put on Hypothes.is so that you and your website stay in the loop on the entirety of the conversation. In many senses, this is just mirroring what is going on in threaded Twitter conversations that get mirrored back to your WordPress website. [I’ll note that I think I’ve got the last of the moving pieces for this Twitter/WordPress workflow properly linked up in the past week.] Since Twitter doesn’t support webmentions itself, Brid.gy is handling that part for you, but in Hypothes.is’ case you don’t have any of the details coming back for allowing you to display the discussion on your site except by doing so manually. Doing it manually for extended conversations is going to become painful over time.

From an IndieWeb perspective, you’re primarily implementing a PESOS workflow in which you post first on Hypothes.is and then send a copy of it to your own website. Naturally it would be better if you were posting all the details on your own website and using the Hypothes.is API to syndicate your copy there for additional public conversation outside of the readership of your website. Unfortunately building the infrastructure to do this is obviously quite daunting. Since they’ve got an API, you might be able to bootstrap something webmention-like onto it, but for your purposes it would obviously be easier if they had direct webmention support.

It would also be wonderful if Hypothes.is supported the micropub specification as well. Then you could ideally log into the system as your website and any annotations you made could be automatically be published to your website for later storage, display, or other use. In some sense, this is what I’m anticipating by making  explicit standalone annotation and highlight post kinds on my website. In practice, however, like you, I’d prefer to have a read, like, or bookmark-type of post that aggregates all of my highlights, annotations, and marginalia of a particular piece for easier future use as well as the additional context this provides. I suspect that if I had the additional tag within the Hypothesis Aggregator plugin for WordPress that would let me specify the particular URL of an individual article, I would have most of the front side PESOS functionality we’re all looking for. The rest will require either webmention or a lot more work.

I may have mentioned it before, but in case you hadn’t found it I’ve got a handful of posts on annotations, many of which include some Hypothes.is functionality.

Not itemized in that list (yet?) are some experiments I’d done with the Rory Rosenzweig Center’s PressForward plugin for WordPress. It allowed me to use a simple browser bookmarklet to save a webpage’s content to my personal website with a rel=”canonical” tag for the page pointing at the original page. (Here’s a good example.) Because of the way the canonical set up works within Hypothes.is, I noticed that annotations I (and others) made on the original were also mirrored and available on my website as well. In my case, because PressForward was copying the entirety of the article for me, I used the <mark> HTML tag to make the highlights on my page, but with Hypothes.is enabled, it also shows the other public annotations as well. (Use of the title attribute adds some additional functionality when the mark tagged text is hovered over in most browsers.)

In another example, I annotated a copy of one of Audrey Watters’ articles (after she’d disabled the ability for Hypothesis to work on her site, but before she changed the Creative Commons licensing on her website). But here I added my annotations essentially as pull-quotes off to the side and syndicated copies to Hypothes.is by annotating the copy on my website. If you visit Audrey’s original, you’ll see that you cannot enable Hypothesis on it, but if you’re using the Chrome extension it will correctly indicate that there are five annotations on the page (from my alternate copy which indicates hers is the rel=”canonical”).

In any case, thanks again for your examples and documenting your explorations. I suspect as time goes by we’ll find a more IndieWeb-centric method for doing exactly what you’ve got in mind in an even easier fashion. Often doing things manually for a while will help you better define what you want and that will also make automating it later a lot easier.

 

 

I’ve come across many journals (and particularly many talking about Altmetrics1,2) that are supporting the old refback infrastructure and wonder why they haven’t upgraded to implement the more feature rich webmention specification?

I’ve been thinking more lately about how to create a full stack IndieWeb infrastructure to replace the major portions of the academic journal ecosystem which would allow researchers to own their academic papers but still handle some of the discovery piece. Yesterday’s release of indieweb.xyz, which supports categories, reminds me that I’d had an idea a while back that something like IndieNews’ structure could be modified to create a syndication point that could act as an online journal/pre-print server infrastructure for discovery purposes.

A little birdie has told me that there’s about to be a refback renaissance to match the one currently happening with webrings.

References

1.
Akers KG. Introducing altmetrics to the Journal of the Medical Library Association. Journal of the Medical Library Association. http://jmla.mlanet.org/ojs/jmla/article/view/250/403. Published July 3, 2017. Accessed July 2, 2018.
2.
Roemer RC, Borchardt R. Chapter 2. Major Altmetrics Tools. ALA Tech Source. https://journals.ala.org/index.php/ltr/article/view/5746/7187. Published July 1, 2015. Accessed July 2, 2018.

👓 How Facebook Punked and then Gut Punched the News Biz | TPM

Read How Facebook Punked and then Gut Punched the News Biz by Josh Marshall (Talking Points Memo)
In the digital publishing world, there’s been a buzz about this article in Slate in which slate staffer Will Oremus detailed the impact on the publication of Facebook’s dramatic retreat from the news business. The numbers are stark but not surprising for people in the industry. Indeed, Oremus makes the point that most news organizations are not willing to release these numbers. (We’ll come back to that point in a moment.) In January 2017 Slate had 28.33 million referrals from Facebook to Slate. By last month that number had dropped to 3.63 million. In other words, a near total collapse.

👓 B&N Posted Loss of $125 Million on 6% Sales Drop in FY ’18 | Publishers Weekly

Read B&N Posted Loss of $125 Million on 6% Sales Drop in FY '18 (PublishersWeekly.com)
Total sales at Barnes & Noble fell 6.0% in the fiscal year ended April 28, 2018, compared to fiscal 2017, and the retailer posted a net loss of $125.5 million last year, compared to net income of $22.0 million in fiscal 2017.

👓 Interviewing my digital domains | W. Ian O’Byrne

Read Interviewing my digital domains by W. Ian O'ByrneW. Ian O'Byrne (W. Ian O'Bryne)

Alan Levine recently posted a series of questions to help others think through some of thoughts and motivations as we develop and maintain a domain of our own.

I’ve written a lot about this in the past, and I’ll try to include some links to content/posts as I respond to the prompts. This is a bit long as I get into the weeds, so consider yourself warned.

And now…let’s get to it…

Highlights, Quotes, & Marginalia

Having a domain is important to me as I research, develop, and teach.

example of a domain as thinking out loud or thought spaces
blogging as thinking


This should be a space where you can create the identity that you want to have. You can write yourself into existence.

I like this sentiment. Had René Descartes been born a bit later might he have said “Blogeō, ergo sum”?


Most of this work is focused on collaboration, transparency, and working/thinking in the open.


The plan is to use the site to share surveys, interviews, and researcher notes.

Note to self: I need to keep documenting examples of these open labs, open notebooks, etc. in the open science area.


teachers hid their Facebook accounts for fear of being fired.

The sound of this to me know reminds me of the type of suppression of thought that might have occurred in the middle ages. Of course open thought and discussion is important for teachers the same way it is for every other person. However there are a few potential counterexamples where open discussion of truly abhorrent ideas can run afoul of community mores. Case in point:


PLN

personal learning network perhaps marking it up with <abbr> tags would be useful here?


luck

lucky


.A

space


I feel like this culture in academia may be changing.


academia is built on the premise (IMHO) of getting a good idea, parlaying that into a job and tenure, and waiting for death. I’ve had a lot of colleagues and acquaintances ask why I would bother blogging. Ask why I share all of this content online. Ask why I’m not afraid that someone is going to steal my ideas.

Though all too true, this is just a painful statement for me. The entirety of our modern world is contingent upon the creation of ideas, their improvement and evolution, and their spreading. In an academic world where attribution of ideas is paramount, why wouldn’t one publish quickly and immediately on one’s own site (or anywhere else they might for that matter keeping in mind that it’s almost trivially easy to self-publish it on one’s own website nearly instantaneously)?
Early areas of science were held back by the need to communicate by handwriting letters as the primary means of communication. Books eventually came, but the research involved and even the printing process could take decades. Now the primary means of science communication is via large (often corporate owned) journals, but even this process may take a year or more of research and then a year or more to publish and get the idea out. Why not write the ideas up and put them out on your own website and collect more immediate collaborators? Funding is already in such a sorry state that generally, even an idea alone, will not get the ball rolling.
I’m reminded of the gospel song “This little light of mine” whose popular lyrics include:
“Hide it under a bushel? No! / I’m gonna let it shine” and
“Don’t let Satan blow it out, / I’m gonna let it shine”
I’m starting to worry that academia in conjunction with large corporate publishing interests are acting the role of Satan in the song which could easily be applied to ideas as well as to my little light.


Senior colleagues indicate that I should not have to balance out publishing in “traditional, peer-reviewed publications” as well as open, online spaces.

Do your colleagues who read your work, annotate it, and comment on it not count as peer-review? Am I wasting my time by annotating all of this? 🙂 (I don’t think so…)


or at least they pretend

I don’t think we’re pretending. I know I’m not!


PDF form

Let me know when you’re done and we’ll see about helping you distribute it in .epub and .mobi formats as e-books as well.


This is due to a natural human reaction to “Google” someone before we meet them for the first time. Before we show up to teach a class, take a class, interview for a job, go on a date…we’ve been reviewed online. Other people use the trail of breadcrumbs that we’ve left behind to make judgements about us. The question/challenge is that this trail of breadcrumbs is usually incomplete, and locked up in various silos. You may have bits of your identity in Facebook or Twitter, while you have other parts locked up in Instagram, Snapchat, or LinkedIn. What do these incomplete pieces say about you? Furthermore, are they getting the entire picture of you when they uncover certain details? Can they look back to see what else you’re interested in? Can they see how you think all of these interests fit together…or they seeing the tail end of a feverish bout of sharing cat pics?

I can’t help but think that doing this is a form of cultural anthropology being practiced contemporaneously. Which is more likely: someone a 100 years from now delving into my life via my personal website that aggregated everything or scholars attempting to piece it all back together from hundreds of other sites? Even with advanced AI techniques, I think the former is far more likely.
Of course I also think about what @Undine is posting about cats on Twitter or perhaps following #marginaliamonday and cats, and they’re at least taking things to a whole new level of scholarship.


Guide to highlight colors

Yellow–general highlights and highlights which don’t fit under another category below
Orange–Vocabulary word; interesting and/or rare word
Green–Reference to read
Blue–Interesting Quote
Gray–Typography Problem
Red–Example to work through

Visually indicating post types on blogs and microblogs

It’s been a while since I’ve actively read Om Malik‘s blog, but I noticed that he’s using graphical indicators that add some semantic detail about what each post is. It’s a design element I’ve only seen lately out of the IndieWeb community with plugins like the Post Kinds Plugin for WordPress or done manually with emoji in post titles the way Aaron Davis has done relatively religiously, particularly on his “Collect” site.

Om Malik is using some graphical indicators to give quick additional semantic meaning to what he’s posting.

I highly suspect that he’s using the Post Formats functionality from WordPress core to do some of this using a custom theme. Sadly it’s generally fallen out of fashion and one doesn’t see it very often any more. I suspect that it’s because WordPress didn’t take the functionality to its logical conclusion in the same way that the Post Kinds Plugin does.

The way Aaron Davis uses emoji in his posts helps to provide additional context about what is being written about to indicate what is going on in a link before it’s clicked.

I think some of my first experience with its resurgence was as helpful UI I saw suggested by Tantek Çelik on the Read page of the IndieWeb wiki. I’ve been doing it a lot myself, primarily for posts that I syndicate out to micro.blog, where it’s become a discovery function using so-called tagmoji (see books, for example), or Twitter (reads, bookmarks, watches, listens, likes). In those places, they particularly allow me to add a lot more semantic meaning to short notes/microblog posts than others do.

I do wish that having emoji for read posts was more common in Twitter to indicate that people actually bothered to read those articles they’re sharing to Twitter, the extra context would be incredibly useful. I generally suspect that article links people are sharing have more of a bookmark sentiment based on their click-bait headlines. Perhaps this is why I like Reading.am so much for finding content — it’s material people have actually bothered to read before they shared it out. Twitter adding some additional semantic tidbits like these would make it much more valuable in my mind.

It doesn’t appear that Om has taken this functionality that far himself though (at least on Twitter). Perhaps if WordPress made it easier to syndicate out content to Twitter with this sort of data attached it would help things take off?

🔖 Pressbooks | Create Books. Print & Ebooks.

Bookmarked Pressbooks :: Book Publishing & Ebook Formatting Software | Create Books. Print & Ebooks. (Pressbooks)
Pressbooks makes it easy to create professionally designed books & ebooks. Discover how our user friendly epublishing software can help you publish today!
This looks like an interesting platform. Saw it as a subdomain on someone’s personal website, so perhaps it’s self-hostable?