I have been working away at some of my end of the year archiving projects, and one that has been taking more time then I planned has been my various attempts to migrate and archive Known to WordPress. I started using Known back in 2014, and I was pretty excited about the possibilities and I blogged about them a few times. But as 2017 comes to a close, so does my exploration of the Known world. I still think Known is one of the best instantiations of the POSSE philosophy, but the inability to marry that with a space to read and interact on the various social media spaces you are pushing to meant it was often, sadly, an afterthought.
I used it fairly robustly for documenting the Wire106 course:
Amazing Wire106 bumper by the great Grant Potter.
The UMW Console fun:
As well as a bathroom renovation:
Those are a few highlights of my Known posts, I went through the archive pretty thoroughly and far and away the UMW Console is the biggest of the image/media posts (there were 300 in all). After that there were about 24 blog posts (cross-posted) and 6 streaming media posts (or audio). The other 1000+ posts on my Known site were either status updates/notes or bookmarks. I used the notes and bookmarks as recently as this month. In fact, those were the only features I used over the last year and a half or so. I stopped posting photos to Known, and basically became a place for bookmarking stuff on the web or recording things I wanted to return to. That said, I knew this was not the right tool for the job. I checked in Diigo—a tool I have logged into maybe 3 times in my life—and I saw there were 400+ cross-posted bookmarks. That was useful, but the bookmarks stopped cross-postingafter I had some issues with the Known plugin for Diigo. I am imagining there are at least a hundred more bookmarks not posted to Diigo, which leaves anywhere from 500-800 notes and status updates as the remaining posts.
I say all this because I tried to grab the Known feed for all content (https://example.withknown.com/content/all?_t=rss) and using FeedWordPress (FWP) to pull it into a WordPress site, but FWP choked on the feed. But thanks to Rob Fairhead I found another feed plugin called RSS Post Importer that could read the feed, but balked at pulling in all the posts. However, I could pull in particular types of content feeds such as posts, photos, and streaming media.:
I was able to use that plugin to pull all my photos, posts, and audio into this WordPress site: http://known.jimgroom.com/
The issue was that the feeds for status updates and bookmarks would not pull, so none of those came over and the WordPress archive site remains incomplete. [Would love hints from anyone that knows how I might do this.]
The other thing I tried was using Site Sucker to archive the entire known.jimgroom.com site, and that worked really well. You can see the results online at archive.known.jimgroom.com. Site Sucker keeps the styles nicely, and it even archived according to content types, which I was pleasantly surprised by.
You can see images here: archive.known.jimgroom.com/content/photos/index.html
Posts here: archive.known.jimgroom.com/content/posts/index.html
Bookmarks here: archive.known.jimgroom.com/content/bookmarkedpages/index.html
Right now the archived site has everything as it was,
but there may be one potential issue once I shutdown Known and move the archived site. I was using a feature through Known to upload all the images to an Amazon S3 bucket, and I am wondering if they will work given they point to known.jimgoom.com. Making sure the images work in the archive site is the last bit to figure out, then I’ll switch it over and archive the Known database and files.† It would be nice to find a way to syndicate the bookmarks and status updates, but at this point having an HTML version of the site should be more than enough, especially given I can sort by content—which was the extent of organizational metadata I added anyway.
So, long story short, that’s it for Known. Although I do think moving forward I want to use a WordPress site for bookmarks and notes (maybe just bavatuesdays, and hide them from plain blog sight and remove them from the feed). One thing I did use well with Known was the Bookmarklet for adding sites as notes and bookmarks, and in the new version of my bookmarking/notes site I plan on using the bookmarklet—-which is an under-used tool—right Tom! : )
†Turns out the image are preserved, but the links to them on the old Known site are dead. I moved the Site Sucker archive over to known.jimgroom.com and it is working brilliantly. I am loving Site Sucker for these archiving/cleaning up projects.
It’s unclear to me after reading this what exactly you wanted Known to do that it didn’t do.
You write: “I still think Known is one of the best instantiations of the POSSE philosophy, but the inability to marry that with a space to read and interact on the various social media spaces you are pushing to meant it was often, sadly, an afterthought.”
Does this mean you couldn’t use Known to read other people’s things? Or does it mean you couldn’t use Known to post things to WordPress? Or…?
I want to be clear about this because I want to avoid making the same mistake with my own work. Thanks.
Thanks for the push to clarify, the issue for me was Known was contextless for social media. I often post across various sites in response to things and share my photos as part of a conversation, so doing it through Known seemed a bit like working in a vacuum. I use Twitter less and less for discussion, so I wonder if I would feel different about this now, but what I wanted from Known was a way to also view and respond to Tweets, Facebooks statuses, photos on Flickr, Instagram, etc. A kind of reader for my content that would collapse those various conversations for me, and I could respond through my Known as if I was within those apps. I increasingly thought Known would make an awesome read//write feed reader if it had such a feature. The main reason Known fell by the wayside for me was I was not using it to publish in all these spaces, rather doing it post-facto if at all. Does that make sense?
Pingback: Known Issues with the Web Garden | bavatuesdays