🎧 Episode 79: IndieWebCamp venue | Timetable

Episode 79: IndieWebCamp venue | Timetable by Manton Reese from Timetable
Manton discusses hosting (and attending) his first ever IndieWebCamp.

I’m excited to hear there will be at least one more IndieWebCamp before the end of the year.

Manton, I too once hosted an IndieWebCamp without ever having attended one myself. My advice is don’t sweat it too much. If you’ve got a location, some reasonable wifi, and even a bit of food, you’ll be okay. The interesting people/community that gather around it and their enthusiasm will be what really make it an unforgettable experience.

Incidentally it was also simultaneously the first ever Bar Camp I had attended and one of the originators of the concept attended! I remember thinking “No pressure here.” It was a blast for me, and I’m sure will be great for you as well.

Syndicated copies to:

Reply to Pingbacks: hiding in plain sight by Ian Guest

Pingbacks: hiding in plain sight by Ian Guest (Marginal Notes)
Wait! Aren’t you researching Twitter? I am indeed and the preceding discussion has largely centred on pingbacks, a feature of blogs, rather than microblogs. I have two points to make here: firstly that microblogs and Twitter may have features which function in a similar way to pingbacks. The retweet for example provides a similar link to a text or resource that someone else has produced. I’ll admit that it has less permanence than a pingback, patiently ensconced at the foot of a blog and ready to whisk the reader off to the linked blog, but then the structure and function of Twitter is one of flow and change when compared with a blog; it’s a different beast. The second is that my point of entry to the blogs and their interconnected web of enabling pingbacks was a tweet. Two actually. Andrea’s tweet took me to another tweet which referenced Aditi’s blog post; had I not been on Twitter and had Andrea and I not made a connection through that platform, the likelihood of me ever being aware of Aditi’s post and the learning opportunities that it and its wider assemblage brings together would be minimal.

I’m finding your short study and thoughts on pingbacks while I was thinking about Webmentions (and a particular issue that Aaron Davis was having with them) after having spent a chunk of the day remotely following the Dodging the Memory Hole 2017 conference at the Internet Archive in San Francisco.

It’s made me realize that one of the bigger values of the iteration that Webmentions has over its predecessor pingbacks and trackbacks is that at least a snapshot of the content has captured on the receiving site. As you’ve noted that while the receiving site has the scant data from the pingback, there’s not much to look at in general and even less when the sending site has disappeared from the web. In the case of Webmentions, even if the sending site has disappeared from the web, the receiving site can still potentially display more of that missing content if it wishes. Within the WordPress ecosystem simple mentions only show the indication that the article was mentioned, but hiding within the actual database on the back end is a copy of the post itself. With a few quick changes to make the “mention” into a “reply” the content of the original post can be quickly uncovered/recovered. (I do wonder a bit if you cross-referenced the Internet Archive or other sources in your search to attempt to recover those lost links.)

I will admit that I recall the Webmention spec allowing a site to modify and/or update its replies/webmentions, but in practice I’m not sure how many sites actually implement this functionality, so from an archiveal standpoint it’s probably pretty solid/stable at the moment.

Separately, I also find myself looking at your small example and how you’ve expanded it out a level or two within your network to see how it spread. This reminds me of Ryan Barrrett’s work from earlier this year on the IndieWeb network in creating the Indie Map tool which he used to show the interconnections between over three thousand people (or their websites) using links like Webmentions. Depending on your broader study, it might make an interesting example to look at and/or perhaps some code to extend?

With particular regard to your paragraph under “Wait! Aren’t you researching Twitter?” I thought I’d point you to a hybrid approach of melding some of Twitter and older/traditional blogs together. I personally post everything to my own website first and syndicate it to Twitter and then backfeed all of the replies, comments, and reactions via Brid.gy using webmentions. While there aren’t a lot of users on the internet doing something like this at the moment, it may provide a very different microcosm for you to take a look at. I’ve even patched together a means to allow people to @mention me on Twitter that sends the data to my personal website as a means of communication.

After a bit of poking around, I was also glad to find a fellow netizen who is also consciously using their website as a commonplace book of sorts.

Syndicated copies to:

🔖 Webrecorder: Create high-fidelity, interactive web archives of any web site you browse

Webrecorder (webrecorder.io)
Create high-fidelity, interactive web archives of any web site you browse.

This looks like a cool archiving tool!

h/t: Dodging the Memory Hole 2017

Syndicated copies to:

In honor of Dodging the Memory Hole 2017 this week, for free (hosting and domain registration not included) I’ll offer to build one journalist or academic a basic IndieWeb-capable WordPress-based portfolio website to display and archive their personal work.

Preference will be given to those in attendance at the conference, but any who need an “author platform” for their work are welcome. Comment or reply below by 11/25/17 to enter.


Syndicated copies to:

OPML files for categories within WordPress’s Links Manager

Last week I wrote about creating my following page and a related OPML file which one could put into a feed reader to subscribe to the list itself instead of importing it. I haven’t heard anyone mention it (yet), but I suspect that like I, some may be disappointed that some feed readers that allow OPML subscriptions don’t always respect the categorizations within the file and instead lump all of the feeds into one massive list. Fortunately there’s a quick remedy!

WordPress in its wisdom used a somewhat self-documenting API that allows one to create standalone OPML files by category. Thus if you only want to subscribe to just the feeds categorized as IndieWeb related in my OPML file, you can append the category id to the end of the URL to filter the others out.

The main OPML file: http://boffosocko.com/wp-links-opml.php
The IndieWeb only file: http://boffosocko.com/wp-links-opml.php?link_cat=1521

So in general, for WordPress sites one can append ?link_cat=[category id] (with or with out the brackets) to the main URL for the OPML file typically found at http://www.example.com/wp-links-opml.php.

I was going to post about this later this week after running across it this weekend, but by odd serendipity, while I was subscribing to Henrik Carlsson’s site I noticed that he posted a note about this very same thing recently! Thanks for the unintended nudge Henrik!

For quick reference, below are links to the specific OPML files for the following categories within my larger OPML file for those who’d like to subscribe to subsections:

Syndicated copies to: