Group photos — Aaron PareckiThis weekend I attended Indie Web Camp in Baltimore. It’s a fun gathering of people who believe we should own our online identities — pictures, thoughts, short and long posts (and even check-ins in some cases). Post to your own domain, then syndicate to social networks, but remain in control. Core principles of the movement are listed on indieweb.org. A breif personal indie web history. I’ve been blogging and building websites and CMSes...
Today, we published the last of the two W3C specs I am editing! WebSub was published as a W3C Recommendation, and IndieAuth was published as a Working Group Note. WebSub WebSub is a standardized way for publishers to notify subscribers when new content is available. It was formerly known as PubSubHubbub, which was hard to say, so I'm glad we...
jonathanprozzi.net — Recently finished a draft of a 45-60 minute activity for new folks to HWC to register their first domain. None of tonight's attendee's need a domain, so we'll punt on that for next time. Spent the time tonight setting up a notebook.jonathanprozzi.net subdomain to be a publicly accessible version of the Hugo site that he set up recently to take notes. He used it over the weekend at IWC Baltimore and now wants it available on his phone. He also subscribed to all the IWC Baltimore attendees on Woodwind.
derekfields.is — Working on VR world project where the server is a microcontroller with sensors that can directly manipulate the VR world. Dealing w/ issues serving an A-Frame VR web app from his nodemcu microcontroller. The nodemcu serves a big opaque string for content and he wants to have it load A-Frame and other third-party resources from a CDN. The trouble is that when your computer is connected to the nodemcu's access point, there is no access to the internet. He is looking at another possibility of serving those minified scripts directly from the nodemcu.
angelosresu.me — Just noticed his website is down, oops. Not been working on his site much. Has been working on setting up his first OAuth implementation at work.
Lots of discussion about what IndieAuth is, vs RelMeAuth, PGP
W3C governance is interesting! And confusing!
Showed off Woodwind as an example of IndieAuth dance. Also got Jonathan set up with Micropub via Woodwind so he can send replies.
Open Graph Protocol, microformats
Moving the idea of computing out of the default idea of a screen and keyboard/mouse/touch and a bunch of storage and computing right in front of you into more interesting paradigms like little internet-connected microcontrollers, virtual worlds.
The idea of needing indie readers to start consolidating how people can read and respond to IndieWeb content as easily as on silos. We may all be asking Aaron for accounts on Monocle.
Thanks to everybody who came out! We hope to see you all again at our next meetings:
February 6th (Note: this is a Tuesday). We'll have a new activity for new folks during this meeting starting at 6:30pm – getting started with web hosting!
When planning IWC Baltimore, one of the things I wanted to prioritize was having high-quality discussion sessions on Saturday, to take on issues that attendees have on their minds, and to get their creative juice's going for the Sunday project hack day.
Aaron, Tantek, and I sat down after IWC Austin to do some (re-)planning of the typical IWC Saturday schedule based on lessons learned in 2017. We had some things in mind:
People start to get tired and distracted after about 45 minutes.
Each facilitator often had a different way of running their session. This sometimes led to discussion ending early, but often meant going over time.
Attendees need time to move between sessions, grab water, use the restroom, etc.
We mapped out several combinations of time for lunch, session length, break length, expected end-of-day, and even decoy time ("we'll tell them they have 5 minutes when actually they have 10").
With the constraints that we wanted to break for lunch at noon, and end the day before 6pm, we settled on a schedule of 5 sessions:
1 hour 15 minutes for lunch, with sessions beginning at 1:15
Facilitators should show up 10 - 15 minutes early to be briefed on how to facilitate well
5 sessions at 45 minutes per session
10 minute break between sessions
A final "Intro to Day 2" session to prepare attendees for the Sunday hackday, which we could shorten if needed.
To encourage more consistent facilitation, I created a "Running an IndieWebCamp Session" card that we handed out to facilitators encouraging them to assign at least one note taker a time keeper with checks at 10, 5, and 1 minute. The card also included tips on how to kick off the discussion.
Overall I think our planning really paid off. We were able to stick almost entirely to the schedule (very few sessions went over time, and none started late), the day ended on time, and informal feedback suggests that the discussions weren't hampered by the format.
Of course, there were some changes:
Our morning session went long, so there were 55 minutes for lunch rather than an hour and 15. Still, we started sessions on time.
Rather than pre-prepping facilitators, we gave them the facilitator cards and explained their contents in the time between sessions.
In addition to the per-session timekeepers, one of the organizers (me!) was responsible for loudly calling the end time for all sessions.
Having the extra time allowed for the unexpected, such as taking extra time to end the live stream for one session and begin it for the next.