One overhyped technology fades as another surges.
There are plenty of reasons why teachers join ambassador programs. For some, this is how they gain access to potentially great tools that…
Back in April, Audrey Watters’ decided to block annotation on her website. I understand why. When we project our identities online, our personal sites become extensions of our homes. To some online writers, annotation overlays can feel like graffiti. How can we respect their wishes while enabling ...
I’ve compiled a twitter list of people related to #openEd, #edTech, #DoOO, #indieweb, and related topics who tweeted about #domains17 in the past week. The list has multiple views including members and by tweets.
Feel free to either subscribe to the list (useful when adding streams to things like Tweetdeck), or for quickly scanning down the list and following people on a particular topic en-masse. Hopefully it will help people to remain connected following the conference. I’ve written about some other ideas about staying in touch here.
If you or someone you know is conspicuously missing, please let me know and I’m happy to add them. Hopefully this list will free others from spending the inordinate amount of time to create similar bulk lists from the week.
For more information see the blog post for the event at http://virtuallyconnecting.org/blog/2017/05/31/domains17/
Indieweb for Education: Some thoughts after the Domains 17 Conference
There’s some interesting discussion of Indieweb-related principles in this live-streamed (and recorded) conversation (below) from the Domains 2017 conference for educators and technologists which covers a lot of what I’d consider to be Indieweb for Education applications.
In particular, some asked about alternate projects for basing education projects around which aren’t WordPress. Some suggested using WithKnown which is spectacular for its interaction model and flexibility. I suspect that many in the conversation haven’t heard of or added webmentions (for cross-site/cross-platform conversations or notifications) or micropub to their WordPress (or other) sites to add those pieces of functionality that Known comes with out of the box.
Another section of the conversation mentioned looking for ways to take disparate comments from students on their web presences and aggregating them in a more unified manner for easier consumption by the teacher and other students (as opposed to subscribing to each and every student’s RSS feed, a task which can be onerous in classrooms larger than 20 people). To me this sounded like the general concept of a planet, and there are a few simple ways of accomplishing this already, specifically using RSS.
An Invitation to Attendees
I’d invite those in attendance at the Domains 17 conference to visit not only the Indieweb wiki, but to feel free to actively participate in the on-going daily discussions (via IRC/Slack/Matrix/Web). I suspect that if there’s enough need/desire that the community would create a dedicated #education channel to help spur the effort to continue to push the idea of owning one’s own domain and using it for educational purposes out into the mainstream. The wiki pages and the always-on chat could be useful tools to help keep many of the educators and technologists who attended Domains17 not only connected after the event, but allow them to continue to push the envelope and document their progress for the benefit of others.
I’ll admit that one of my favorite parts of the Indieweb wiki is that it aggregates the work of hundreds of others in an intuitive way so that if I’m interested in a particular subject I can usually see the attempts that others have made (or at least links to them), determine what worked and didn’t for them, and potentially find the best solution for my particular use case. (I suspect that this is some of what’s missing in the “Domains” community at the moment based on several conversations I heard over the past several days.)
If you’d like, please add yourself to the growing list of Indieweb related educators and technologists. If you need help connecting to any of the community resources and/or chat/IRC/Slack, etc. I’m more than happy to help. Just call, email, or contact me via your favorite channel.
For more information see the blog post for the event at http://virtuallyconnecting.org/blog/2017/05/31/domains17/
I’m writing a multi-part series for academics on #Indieweb & Education based on these links.
May have to come up with something related for @mattervc based on @benwerd‘s tweet https://twitter.com/benwerd/status/847115083318607872
— Ben Werdmuller (@benwerd) March 29, 2017
In #Indieweb fashion, I’ve archived this tweetstorm using NoterLive.com on my own site: http://boffosocko.com/2017/03/29/indieweb-and-education-tweetstorm/
WithKnown is a fantastic, free, and opensource content management service that supports some of the most bleeding edge technology on the internet. I’ve been playing with it for over two years and love it!
And today, there’s another reason to love it even more…
This is also a great reminder that developers can have a lasting and useful impact on the world around them–even in the political arena.
You can now import your reference library directly from Mendeley to Overleaf, to make it easy to manage your references and citations in your projects
Clint, first, congratulations on your first PR!
Oddly, I had seen the VERY same post/repo a few weeks back and meant to add a readme too! (You’ll notice I got too wrapped up in reading through the code and creating some usability issues after installing the plugin instead.)
Given that you’ve got your own domain and website (and playing in ed/tech like many of us are), and you’re syndicating your blog posts out to Medium for additional reach, I feel compelled to mention some interesting web tech and philosophy in the #IndieWeb movement. You can find some great resources and tools at their website.
In particular, you might take a look at their WordPress pages which includes some plugins and resources you’ll be sure to appreciate. One of their sets of resources is allowing you to not only syndicate your WP posts (what they call POSSE), but by using the new W3C webmention spec, you can connect many of your social media resources to brid.gy and have services like twitter, facebook, G+, instagram and others send the comments and likes on your posts there back to your blog directly, thereby allowing you to own all of your data (as well as the commentary that occurs elsewhere). I can see a lot of use for education in some of the infrastructure they’re building and aggregating there. (If you’re familiar with Known, they bake a lot of Indieweb goodness into their system from the start, but there’s no reason you shouldn’t have it for your WordPress site as well.)
If you need any help/guidance in following/installing anything there, I’m happy to help.
Congratulations again. Keep on pullin’!
As a researcher, I fully appreciate the pro-commonplace book conceptualization of the first post, and the second takes things amazingly further with a plugin that allows one to easily display one’s hypothes.is annotations on one’s own WordPress-based site in a dead-simple fashion.
This functionality is a great first step, though honestly, in keeping with IndieWeb principles of owning one’s own data, I think it would be easier/better if Hypothes.is both accepted and sent webmentions. This would potentially allow me to physically own the data on my own site while still participating in the larger annotation community as well as give me notifications when someone either comments or augments on one of my annotations or even annotates one of my own pages (bits of which I’ve written about before.)
Either way, kudos to Kris Shaffer for moving the ball forward!
My Hypothes.is Notebook
My IndieWeb annotations
I can also easily embed my recent annotations about the IndieWeb below:
[ hypothesis user = 'chrisaldrich' tags = 'indieweb']
Marginalia and Revision Control
At the end of April, I read an article entitled “In the Margins” in the Johns Hopkins University Arts & Sciences magazine. I was particularly struck by the comments of eminent scholar Jacques Neefs on page thirteen (or paragraph 20) about computers making marginalia a thing of the past:
I actually think that he may be completely wrong and that current technology actually allows us to keep far more marginalia! (Has anyone heard of digital exhaust?) The bigger issue may be that many writers just don’t know how to keep a better running log of their work to maintain all the relevant marginalia they’re actually producing. (Of course there’s also the subsequent broader librarian’s “digital dilemma” of maintaining formats for the future. As an example, thing about how easy or hard it might be for you to read that ubiquitous 3.5 inch floppy disk you used in 1995.)
A a technologist who has spent many years in the entertainment industry, I feel compelled to point everyone towards the concept of revision control (or version control) within the realm of computer science. Though it’s primarily used in tracking changes in computer programs and is often a tool used by large teams of programmers, it can very easily be used for tracking changes in almost any type of writing from novels, short stories, screenplays, legal contracts, or any type of textual documentation of nearly any sort.
Example Use Cases for Revision Control
As a direct example, I’m using what is known as a Git repository to track every change I make in a textbook I’m currently writing. I can literally go back and view every change I’ve made since beginning the project, so though I’m directly revising one (or more) text files, all of my “marginalia” and revisions are saved and available. Currently I’m only doing it for my own reference and for additional backup not supposing that anyone other than myself or an editor possibly may want to ever peruse it. If I was working in conjunction with otheres, there are ways for me to track the changes, edits, or notes that others (perhaps an editor or collaborator) might make.
In addition to the general back-up of the project (in case of catastrophic computer failure), I also have the ability to go back and find that paragraph (or multiple pages) I deleted last week in haste, but realize that I desperately want them back now instead of having to recreate them de n0vo.
Because it’s all digital, future scholars also won’t have problems parsing my handwriting issues as has occasionally come up in differentiating Mary Shelley’s writing from that of her husband in digital projects like the Shelley Godwin Archive. The fact that all changes are tracked and placed in a tree-like structure will indicate who wrote what and when and will indicate which changes were ultimately accepted and merged into the final version.
Screenplays in Hollywood
One particular use case I can easily see for such technology is tracking changes in screenplays over time. I’m honestly shocked that every production company or even more likely studios don’t use such technology to follow changes in drafts over time. In the end, doing such tracking will certainly make Writers Guild of America (WGA) arbitrations much easier as literally every contribution to a script can be tracked to give screenwriters appropriate credit. The end results with the easy ability to time-machine one’s way back into older drafts is truly lovely, and the outputs give so much more information about changes in the script compared to the traditional and all-too-simple (*) which screenwriters use to indicate that something/anything changed on a specific line or the different colored pages which are used on scripts during production.
I can also picture future screenwriters using services like GitHub as platforms for storing and distributing their screenplays to potential agents, managers, and producers.
Redlining Legal Documents
Having seen thousands of legal agreements go back and forth over the years, revision control is a natural tool for tracking the redlining and changes of legal documents as they change over time before they are finally (or even never) executed. I have to imagine that being able to abstract out the appropriate metadata in the long run may actually help attorneys, agents, etc. to become better negotiators, but something like this is a project for another day.
In addition to direct research for projects being undertaken by academics like Neefs, academics should look into using revision control in their own daily work and writings. While writing a book, paper, journal article, essay, monograph, etc. (or graduate students writing theses) one could use their own Git repository to not only save but to back up all of their own work not only for themselves primarily, but also future scholars who come later who would not otherwise have access to the “marginalia” one creates while manufacturing their written thoughts in digital form.
I can easily picture Git as a very simple “next step” in furthering the concept of the digital humanities as well as in helping to bridge the gap between C.P. Snow’s “two cultures.” (I’d also suggest that revision control is a relatively simple step one could take before learning a particular programming language, which I think should be a mandatory tool in everyone’s daily toolbox regardless of their field(s) of interest.)
Start Using Revision Control
“But how do I get started?” you ask.
Know going in that it may take parts of a day to get things set up and running, but once you’ve started with the basics, things are actually pretty easy and you can continue to learn the more advanced subtleties as you progress. Once things are working smoothly, the additional overhead you’ll be expending won’t be too much more than the old method of hitting Alt-S to save one of your old Word documents in the time before auto-save became ubiquitous.
First one should start by choosing one of the myriad revision control systems that exist. For the sake of brevity in this short introductory post, I’ll simply suggest that users take a very close look at Git because of its ubiquity and popularity in the computer science world and the fact that it includes a tremendously large amount of free information and support from a variety of sites on the internet. Git also has the benefit of having versions for all major operating systems (Windows, MacOS, and Linux). Git also has the benefit of a relatively long and robust life within the computer science community meaning that it’s very stable and has many more resources for the uninitiated to draw upon.
Once one has Git installed on their computer and has begun using it, I’d then recommending linking one’s local copy of the repository to a cloud storage solution like either GitHub or BitBucket. While GitHub is certainly one of the most popular Git-related services out there (because it acts, in part, as the hub for a large portion of the open internet and thus promotes sharing), I often recommend using BitBucket as it allows free unlimited private but still share-able repositories while GitHub requires a small subscription fee for keeping one’s work private. Having a repository in the cloud will help tremendously in that your work will be available and downloadable from almost anywhere and because it also serves as a de-facto back-up solution for your work.
I’ve recently been playing around with version control to help streamline the writing/editing process for a book I’ve been writing. Though Git and it’s variants probably seem more daunting than they should to the everyday user, they really represent a very powerful tool. I’ve spent less than two days learning the basics of both Git and hosted repositories (GitHub and Bitbucket), and it has been more than well worth the minor effort.
There is a huge wealth of information on revision control in general and on installing and using Git available on the internet, including full textbooks. For the complete beginners, I’d recommend starting with The Chronicle’s “A Gentle Introduction to Version Control.” Keep in mind that though some of these resources look highly technical, it’s because many are trying to enumerate every function one could potentially desire, when even just the basic core functionality is more than enough to begin with. (I could analogize it to learning to drive a car versus actually reading the full manual so that you know how to take the engine apart and put it back together from scratch. To start with revision control, you only need to learn to “drive.”) Professors might also avail themselves of the use of their local institutional libraries which may host small sessions on learning such tools, or they might avail themselves of the help of their colleagues or students in the computer science department. For others, I’d recommend taking a look at Git’s primary website. BitBucket has an excellent step-by-step tutorial (and troubleshooting) for setting up the requisite software and using it.
What do you use for revision control?
I’ll welcome any thoughts, experiences, or additional resources one might want to share with others in the comments.