Started playing around with PressBooks for WordPress tonight. Some interesting and useful book collaboration, editing, and production tools hiding in here.
Category: Publishing
👓 Why We Removed Pressbooks from the WordPress Plugin Repository | PressBooks
Ned Zimmerman (Pressbooks)A couple weeks ago, we removed Pressbooks from the WordPress Plugin Repository. We want to offer an explanation for this decision to our users, and give some insight into our plans for the distribution of Pressbooks moving forward. Press...
Wondering why @sfiscience’s excellent website has no RSS, ATOM, JSON, or other feed available? #scicomm
👓 Digital Literacy, Identity and a Domain of One’s Own | Connected Learning Alliance
Doug Belshaw (Connected Learning Alliance)Ten years ago, if I knew someone primarily through online means, you could guarantee they had their own domain name. It was just before the big explosion in social media use which meant that if you wanted a space online, you had to create it. This provided a barrier to entry in terms of the digital literacy skills required to register a domain, set up the necessary software and, of course, design, build and upload a website. The upside was that your digital identity was yours. That domain name could be your gamer tag, it could be your real name, it could be a heteronym — it was up to you!
Highlights, Quotes, Annotations, & Marginalia
Ten years ago, if I knew someone primarily through online means, you could guarantee they had their own domain name. It was just before the big explosion in social media use which meant that if you wanted a space online, you had to create it. This provided a barrier to entry in terms of the digital literacy skills required to register a domain, set up the necessary software and, of course, design, build and upload a website. The upside was that your digital identity was yours. ❧
Why have we gotten away from this? In short, I think it’s because it was easier for big companies with massive resources to do the initial heavy lifting.
If we look at history, Gutenberg created the first printing press and guarded it heavily for years. Eventually others figured out how to do it and printing presses spread like wildfire. Now, with some modest means and some time, almost anyone can publish.
With simple standards and accessible hosting people can now broadly own their own domain name and create their own websites using a variety of content management systems. In a few years, this will be even more ubiquitous. Facebook is going to be just like Gutenberg attempting to hold onto his monopoly, but failing miserably.
The best part, I think, is that the speed of digital technology means that the Facebook edifice is going to crumble faster than Gutenberg’s.
Twitter and Facebook are publicly-traded companies and beholden to shareholders looking to make a profit. Google, which owns YouTube and processes over 70% of the world’s search traffic, is likewise legally obliged to return a profit. ❧
legally obligated? they’re definitely supposed to try or shareholders may move their money elsewhere, but why can’t they create things for the common good as well?
A world where one’s primary identity is found through the social people-farms of existing social networks is a problematic one. Educators and parents are in the privileged position of being able to help create a better future, but we need to start modeling to future generations what that might look like. ❧
This is exactly what I’ve been attempting to do with my own website. Naturally I use it selfishly for my own purposes, but I’m also using it to model potential behaviours for friends, family and colleagues.
I’m sometimes tempted to change the tagline on my website to “A digital canary in the coalmine”.
Some thoughts on silos, divisions, and bridges
Cruce Saunders (Twitter)Instead of 'eliminating' divisions, or 'blowing up' silos....let's use metaphors about bridging, connecting, unifying, transcending, collaborating across borders.... connecting all of the groups within an organization in a coherent way so that they all work seemlessly together.
— Cruce Saunders (@mrcruce) July 31, 2018
The #IndieWeb community has been working on this for a while. There’s even a service called Brid.gy to help enact it. At the same time, as Ben Werdmüller indicates, we need to be careful not to put too much reliance on silos’ APIs which can, and obviously will, be pulled out from underneath us at any moment.
As any kindergartner can tell you, “It’s difficult to play ball when the local bully owns the ball and wants to make up their own rules or leave in a huff.”
One of the things I love about IndieWeb is that we’re all trying to create a way for balls to be roughly standardized and mass manufactured so that everyone can play regardless of what the bully wants to do or what equipment people bring to the game.1
And as Nikhil Sonnad has reminded us very recently, we also need more than just connections, we need actual caring and thinking human interaction.2
References
1.
Aldrich C. Webmentions: Enabling Better Communication on the Internet. A List Apart. https://alistapart.com/article/webmentions-enabling-better-communication-on-the-internet. Published July 19, 2018. Accessed July 31, 2018.
2.
Sonnad N. Everything bad about Facebook is bad for the same reason. Quartz. https://qz.com/1342757/everything-bad-about-facebook-is-bad-for-the-same-reason/. Published July 30, 2018. Accessed July 31, 2018.
🎙 The IndieWeb and Academic Research and Publishing
Running time: 0h 12m 59s | Download (13.9 MB) | Subscribe by RSS |
Huffduff
Overview Workflow
Posting
Researcher posts research work to their own website (as bookmarks, reads, likes, favorites, annotations, etc.), they can post their data for others to review, they can post their ultimate publication to their own website.
Discovery/Subscription methods
The researcher’s post can webmention an aggregating website similar to the way they would pre-print their research on a server like arXiv.org. The aggregating website can then parse the original and display the title, author(s), publication date, revision date(s), abstract, and even the full paper itself. This aggregator can act as a subscription hub (with WebSub technology) to which other researchers can use to find, discover, and read the original research.
Peer-review
Readers of the original research can then write about, highlight, annotate, and even reply to it on their own websites to effectuate peer-review which then gets sent to the original by way of Webmention technology as well. The work of the peer-reviewers stands in the public as potential work which could be used for possible evaluation for promotion and tenure.
Feedback mechanisms
Readers of original research can post metadata relating to it on their own website including bookmarks, reads, likes, replies, annotations, etc. and send webmentions not only to the original but to the aggregation sites which could aggregate these responses which could also be given point values based on interaction/engagement levels (i.e. bookmarking something as “want to read” is 1 point where as indicating one has read something is 2 points, or that one has replied to something is 4 points and other publications which officially cite it provide 5 points. Such a scoring system could be used to provide a better citation measure of the overall value of of a research article in a networked world. In general, Webmention could be used to provide a two way audit-able trail for citations in general and the citation trail can be used in combination with something like the Vouch protocol to prevent gaming the system with spam.
Archiving
Government institutions (like Library of Congress), universities, academic institutions, libraries, and non-profits (like the Internet Archive) can also create and maintain an archival copy of digital and/or printed copies of research for future generations. This would be necessary to guard against the death of researchers and their sites disappearing from the internet so as to provide better longevity.
Show notes
Resources mentioned in the microcast
IndieWeb for Education
IndieWeb for Journalism
Academic samizdat
arXiv.org (an example pre-print server)
Webmention
A Domain of One’s Own
Article on A List Apart: Webmentions: Enabling Better Communication on the Internet
Synidicating to Discovery sites
Examples of similar currently operating sites:
IndieNews (sorts posts by language)
IndieWeb.xyz (sorts posts by category or tag)
Kathleen did you own the domain where Planned Obsolescence1 was peer-reviewed? It may be one of the first major examples of book-length online academic samizdat of which I’m aware. Perhaps you know of others which could be documented? I suspect we could help provide additional exemplars and links to other web technology, platforms, plugins, etc. to make this an easier and more commonplace practice.
James Shelley, I’ve noticed your draft efforts2,3 as well. I’m curious if you could take a moment to document them, i.e. what you’re using, how you’ve planned it, etc. to help others as well.
If you’ve already blogged about these in the past, then even links to those could be helpful to others using similar publishing practices in the future. Thoughts on brainstorming, best practices, pros/cons, could be highly useful as the landscape changes.
References
1.
Fitzpatrick K. Planned Obsolescence: Publishing, Technology, and the Future of the Academy. NYU Press. https://amzn.to/2NAfIPF. Published November 1, 2011. Accessed July 23, 2018.
2.
Shelley J. System Thinker Notebook. James Shelley. http://jamesshelley.com/drafts/simple.html. Published July 11, 2018. Accessed July 23, 2018.
3.
Shelley J. On the Simple Life. James Shelley. http://jamesshelley.com/drafts/simple.html. Published July 22, 2018. Accessed July 23, 2018.
Nir 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
Sara Soueidan (Twitter)If you have a blog and write/share useful things (big or small) about Web design / front-end dev and you provide an RSS feed to the blog, please respond to this tweet w/ the URL for it — I’d like to add more useful content feeds to my reader.
— Sara Soueidan (@SaraSoueidan) July 20, 2018
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?
👓 Community Review | Kathleen Fitzpatrick
Kathleen 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.
RSVP for DrupalCamp LA 2018
The Los Angeles area conference for all west-coast things Drupal — July 21-22, 2018
👓 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.
Flight from LAX to SFO en route to PDX
Pre-Summit meetup at Pine Street Market
social meetup at Pine Street Market
A view onto Portland from the Hotel deLuxe
The Eliot Center where IndieWeb Summit 2018 will take place.
The entrance of the Eliot Center
The Eliot Center provided a fantastic location for this year’s Summit
Aaron Parecki kicks off the 2018 IndieWeb Summit
A packed room for the start of the summit
Everyone held in rapt attention.
Tantek provides a solid overview of the State of the Indieweb
Manton Reece and Jean MacDonald present a keynote on the Micro.blog Community and Progress
Manton discusses some of the philosophy behind Micro.blog
Jean MacDonald of Micro.blog talks about community
William Hertling, author of Kill Process, imagines the future of the IndieWeb in his keynote
The conversation on How can we encourage diversity on the IndieWeb?
The diversity conversation continues
Microsub: how to build servers and clients
Microsub: how to build servers and clients
The Microsub conversation continues
The session grid for day one of the Summit
My home away from home during the summit: the Hotel deLuxe
Manton Reece chats with Aaron Parecki at the Micro.blog meetup at Von Ebert Brewing.
Conversations begin over breakfast at the beginning of day two.
Hack day on day two of the summit is about to begin.
Early morning sessions for hack day are announced.
Thanks GoDaddy for sponsoring the caffeine to keep us all going.
It’s a beautiful day at the Eliot Center for the Hack Day at IndieWeb Summit 2018.
I finally take my name tag off as I depart the conference on the way back home to Los Angeles. Thanks everyone!
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
William Ian O'Byrne (Twitter)Also, if this post is the best example of @hypothes_is annotations baked into WordPress site, I'd like to see some #IndieWeb connections so the great discussion with @heatherstaines is pulled into the comments/mentions on the post. This would be just like tweets or other comments
— William Ian O'Byrne (@wiobyrne) July 5, 2018
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.