tiaramiller.com — Relaunched her site as a Hugo site hosted on Netlify during the recent IndieWebCamp NYC. Since then, has been working on adding features. Set up voxpelli's webpage-micropub-to-github on Heroku and was able to log into Indigenous and create a new like post! webpage-micropub-to-github is designed for Jekyll, so it created the post file in an unexpected place, but she should be able to tweak that and get things working. Also added herself (back) to the IndieWeb Webring.
mfgriffin.com — Upon some (possibly bad) advice from Marty and Tiara, Matt worked towards hosting his Hugo-powered site via GitHub and Netlify, rather than compiling it on his laptop and uploading the finished HTML to a server. Ran into issues with git submodules, and then a version mismatch between the theme he was using and the version of Hugo on Netlify. He was able to update the published HTML pages to let himself login to indieweb.org to review his todo list, meaning he made it to "step zero" on his list of goals for the day.
martymcgui.re — Working on indieweb.nyc, a site for IndieWeb events in and around New York City. Mostly spent time on plumbing, setting up a barebones Hugo site and hosting it on Netlify. Keeps finding himself pulled between desires: to get barebones content up, to allow interested folks to add events to their calendar, to work on plumbing that will make it easier to manage events via micropub, and to work on styling, theming, and logo.
Thanks to everyone who came out and braved the crowded weekend tables. Apparently it was midterms time at NYU? We hope that you'll join us for the next meetup, on November 16th. Watch indieweb.nyc for info about the exact time and location!
In honor of the IndieWeb in Practice session, I’m curating some of my photos and videos from the weekend.
And, since I’m thinking about the event as I look through them, I’ll capture some lessons learned for next time, as well!
First up, some photos I took while I wanted for others to join for the pre-event meetup on Friday. I forgot that the Stone Street tables, while they appear to be open seating, actually belong to restaurants who may chase you away.
A couple of lessons learned for this event: ask for RSVPs to the Friday social when people register for tickets. Also, pick a place that takes reservations!
Then it was time to help set up the camp at the Pace Seidenberg school. Thanks to Aaron we had a table full of IndieWeb pins and stickers, as well as pronoun pins for ask/he/she/they. I also brought in some simple stick-on name badges and markers, but before next camp I want to pick up some multi-colored lanyards instead, as a way of letting attendees state their preferences for our photo policy.
While we waited for folks to show up, David set up our tech setup and Greg worked with our keynotes Amira (on site) and Amanda (remote). After a brief kick-off, it was keynote time!
A couple of lessons-learned, here.
Out of something like 50 registrants, we had about 12 folks actually show up. A pretty dismal attrition rate! In the future, I think we will charge at least a small registration fee for IndieWebCamp NYC, so that registrants have something at stake if they don’t come.
For an introduction to the weekend, we really should have followed past examples like the Day 1 introduction for IndieWeb Summit. I think the Saturday discussions would also have benefitted from a 10-minute “What is the IndieWeb?” intro from one of the organizers.
Saturday Intros and Demos
Following keynotes, we had an introduction and demo session where anyone could introduce themselves and show off some features of their website. There were a couple of lessons learned here, as well!
David did a great job with our tech, setting up self-contained stations consisting of low-cost Android TV boxes that connect to a display over HDMI, can be controlled via an infrared remote, and are pre-configured to sign into a pre-set Zoom meeting, which can be recorded. One thing we didn’t prep for very well was that in order to present with such a setup, all presenters and folks giving demos need to dial into the Zoom meeting and share their screen or browser window. This allows remote participants to not only see and hear but also join in on presenting, which is great. This extra bit of setup wasn’t much work, but it was time-consuming and frantic when not expected.
One final note, we should set clear expectations at the start of intros and demos for how and what to present, how much time each person has, and should have an emcee to keep them moving with minimal commentary (and only positive commentary, if any at all).
After keynotes and demos, it was time to do some session planning and build out the grid of discussions for the day.
Building out the Saturday discussion session grid is always an interesting challenge, and I often step up to try and help emcee it if I am co-organizing. We had many attendees who were new to the IndieWeb community, and it was sometimes tricky to find concise wording for a given topic. That said, I think we came away with some particularly interesting things to discuss!
But before discussion sessions, some lunch. Matt and I went to 150 Market, which had a perfectly mediocre lunch hot bar.
I didn’t take any photos during the sessions, though I did help with note-taking in many of them. I’ll have to jot down my experiences with those in another post.
During the last session, Greg and I cleaned up all the uneaten food (we definitely bought too much!) and picked up the space. Then we closed for the day, with the organizers taking a brief trip to One Pace Plaza, which would be our location for day two.
Getting to the room was a little confusing, so I made a quick video to send out to registrants that night.
After that, it was time for dinner, cocktails, and winding down.
Feeling burned by our bagel-and-fruit over-buy on Saturday, Tiara and I decided to provide coffee and let folks get breakfast on their own. The Dunkin Donuts where we picked up coffee also had the Beyond Meat faux-sausage patties, so I took the opportunity to try it.
Lesson learned here: out of two Starbucks in the Pace area where I tried to buy boxed coffee, none of them had this available!
After morning of hacking on my demo (post TBD!) and lending an assist with Tiara’s Hugo setup, it was lunchtime! Greg was kind enough to sponsor a delivery from Dos Toros Taqueria which, despite their nearly impossible to use website, worked out well and was delicious.
With food and more coffee in our stomachs, we hacked until demo time!
After demos was a quick cleanup, break for dinner, a stop outside 177 Bleecker St., and a short round of cocktails before I headed home, exhausted. 😅
Note: much of this was taken from the “thank-you” email that Greg, Tantek, Tiara, and I put together to send attendees after camp
Thanks to all organizers and attendees for making this year’s IndiewebCamp NYC a success! From the enlightening keynotes and in-depth discussions on Saturday, to the successful launch of several new personal websites and other projects on Sunday, we are extremely pleased with how it went.
Here’s a quick recap of the weekend.
Six of us met up at Adrienne’s pizzabar on Stone Street for pizza, pasta, and discussion of the weekend to come! Thanks to Mozilla for sponsoring this pre-event social!
Amira Dhalla opened the day with a keynote on data privacy in this age of online surveillance. You can find her slides here.
Amanda Rush walked us through some concrete steps that we can take to make our websites more accessible. Look for a link to her talk transcript on indieweb.org/2019/NYC as soon as we can make it available.
We then made a schedule of attendee-facilitated discussions, covering topics like Automation, Getting Started, Why We Publish, and many more!
Sunday was a day of making, with 10 of us convening at One Pace Plaza to create and hack on our personal sites and projects. We kicked off by having each participant stick notes for their planned projects on the wall for accountability, then dove in!
Three participants were able to demonstrate brand new personal sites, and many more folks had made incremental improvements or fixes! You can find the full details on what was demoed at https://indieweb.org/2019/NYC/Demos
I’ll post some of my own, shortly, but we also want to see yours!
Did you take photos? Write a blog post about the experience? Want to share? We encourage everyone to help us get the word out about IndieWebCamp NYC. Please hashtag your posts with #IndieWebCamp!
IndieWebCamp NYC would not have been a success without attendees like you! Of course, we’d also like to thank our sponsors (Pace, ReView, Mozilla, and all our Open Collective donors) for making this event possible!
And, of course, thanks to all my fellow co-organizers: Tiara, Greg, David.
If you’d like weekly updates and event invitations, sign-up for our This Week In The IndieWeb newsletter!
rasulkireev.com (new!) — New to the IndieWeb and attending his first meetup! Has been building his own websites for a while, learning a lot about web development. Currently working on a version of his site based on Django, and interested in adding IndieWeb building blocks, starting with rel=me.
martymcgui.re — Working on his write-up(s) post-IndieWeb Summit. Made some small progress today. 😅 Also wanting to streamline his iOS Shortcuts-based workflows for posting to his site, taking personal notes, etc.
We should bring signs or other IndieWeb indicators to these meetups! I'm so used to a few regulars that I didn't expect new folks. Thankfully Rasul found me! 😬
We talked about soooo many building blocks! Webmention (and how to use them to RSVP), Micropub (and how iOS Shortcuts can post using it), backfeed (responses from Twitter), storing data, hosting sites and content, learning new languages, learning new libraries, how and why to learn new web dev skills, and much more.
How did you get started building websites? Despite starting many years apart, we both had stories of building websites for groups we were part of or businesses we knew people from.
Staying in touch with the IndieWeb community, from chat (very high attention if you're in there all the time to low attention with the help of Loqi the chat bot and !tell commands) to the weekly newsletters.
Thanks to Rasul for coming out for his first IndieWeb Meetup! We missed Tiara, who was stuck on Long Island due to extreme train schedule changes. We also missed Matt G, who was at a wedding, but working on his website in spirit.
We look forward to seeing folks at the next meeting! Watch the Events page for details about the next meetup!
Here are notes from the "broadcast" portion of the meetup.
amyhurst.com — Did not work on her site today. Been updating her NYU-generated faculty page, instead, and thinking about how it fits in with her site. Trying to fix links to things like research papers, which are normally behind paywalls.
mfgriffin.com — Managing TODO lists today! Trapped in a "oh all these wonderful tools to choose from" situation. Made a lateral move to put his notes about IndieWeb into a local notebook in OneNote, re-reading them and splitting things up. Finding lots of old TODOs from IndieWebCamp and other meetings. Got FTP to his website functioning again. Amy reminds him to set up griff.fun to redirect to his main site, as it's parked right now.
tiaramiller.com — Been learning Amazon Web Services stuff, finding lots of IndieWeb examples of folks hosting on S3 and other services there. Doing research and making lists for things to try and learn next.
martymcgui.re — Updated his homepage feed of upcoming events. Previously, it would show future events that he had posted on his site, but it now also shows RSVPs
Other topics of discussion
We got a pretty decent table and an outlet, even! Sundays are pretty quiet here so that's good. The A/C was quite aggressive, though!
AWS does so many things and also has a very steep learning curve!
IndieWebCamp shirts are available now in two styles!
We didn't really have a "broadcast" portion of the meetup, but we discussed some things and worked on personal projects! I'm writing this up nearly a month late, so I have forgotten many of the things we talked about. 😬
Matt (mfgriffin.com) and myself (martymcgui.re) researched ways for Matt to capture and process the many text, audio, image, and video artifacts that he creates across many projects, both personal and professional.
I showed off a bit about how I do this on my own non-public notes site, and spent some time working on an iOS Shortcut to post notes more quickly to that personal site.
We look forward to seeing folks at the next HWC NYC, at another weekend meetup on June 9th. We'll be meeting at the same location, and may even be able to grab some outlets this time!
We didn't really have a "broadcast" portion of the meetup, but we discussed some things and worked on personal projects!
mfgriffin.com (new!) — Has been to IndieWeb events in the past, but is looking to get re-started. Went over his past notes about some of his hopes and plans for his site, and how he wants to use it for personal notes, writing, drawing, and blogging projects, and more. Got started on a stripped-down system of using Hugo to track plaintext notes, with tags, so he can worry about how to organize it more later.
dmitri.shuralyov.com — Interested in being "done" with his notification system updates. In general, wants to be able to iterate faster on his site updates, and finds that a lot of his time is absorbed in HTML/CSS design processes. Started working on some text-only designs, which get a minimal amount of styling by being converted from Markdown to HTML. By using text and emojis, he was able to prototype a couple of quick things during the meetup.
martymcgui.re — Recently decided that he disagrees with how Granary processes his site's feed (which is HTML+Microformats2) into JSON Feed and Atom. The result is that his feeds often have missing info and show up as weirdly empty posts on micro.blog or in Atom feed readers. At the meetup, finished writing and adapter that will take his main feed and spit out a JSON Feed. Managed to break his site's build process trying to integrate it, but will get it working soon enough.
A couple Dmitri's cool game projects
The recent release of the original source for Zork and other Infocom games, as they would have been worked on originally, for a compiler that no longer exists. Really neat to see how that info is organized.
We want to start later! Folks often need until 6 or 6:30pm to arrive.
We're also open to venue options!
Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, May 1st from 6:30pm - 8:30pm!
Here are some notes from the "broadcast" portion of the meetup!
zazzyzeph.biz (new!) — Learning about Progressive Web Apps and their features, like web app manifests. Started out wanting to learn ES6 and decided to roll back to some basics. Doesn't have a specific project in mind, yet, so doing lots of reading.
dmitri.shuralyov.com — Continuing work on "v2" of his website, specifically notifications API. "v2" is more package-based than repository-based, as a single repo can hold multiple packages, and it's very helpful to reason about the projects individually. Demonstrated showing unread notifications from Gerrit and GitHub, new presentation to show
martymcgui.re — Re-organized his homepage to be much simpler, moving incrementally towards having easier ways for people to discover the newer parts of his site, like where he displays photos, listens, and more interesting ways than his main "river of posts" timeline view. Also added book cover photos to his reading posts (example) using the Open Library Covers API with lookup by ISBN.
Building your own organizational and self-management tools. Balancing time spent on that tooling versus actually getting things done.
Updating, migrating, and archiving old behaviors and versions in APIs. "Gradual code repair". Making "v2" versions of pieces of an API while allowing "v1" apps to work, hybrid apps to work. Semantic versioning when "v2" could change wildly - is it "really v2-pre-0.0.1", for example? A name like that should warn away folks starting new projects that expect a stable API.
Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, April 17th at 6:30pm!
Here are some notes from the "broadcast" portion of the meetup!
dmitri.shuralyov.com — Working on his notification system, specifically tracking (un)read status of notifications from Gerrit. Today was exploring pieces of the system he'll have to modify to get this to work and now has a list of which pieces need updates. In his previous notification system, any fetch of a notification marked it as read, but that will change because it gives him more control over the system. Also made an update to the Homebrew Website Club main page to make the event description clearer, using text that we include on individual HWC event pages now.
martymcgui.re — Did a lot of digging into what's possible with MediaWiki templates, with the goal of simplifying the creation of Homebrew Website Club event pages on the IndieWeb wiki. He was able to get an "hwcdate" template together that outputs the date portion (2019-03-20) of event pages like events/2019-03-20-homebrew-website-club-nyc. Maybe created some tech debt, given how that locks in our URLs, but hopefully it will save some copy-paste-tweak labor.
rootedfromnature.com — Got stuck on a train and super delayed! 😭
MediaWiki and its relation to Wikipedia and as an open source project. Many mediawiki installs become stale quickly, for some good reasons! Finding documentation on parts of mediawiki can also be confusing, as the common terms may point to similar but unrelated topics, may be outdated, may refer to plugins or extensions you don't have, or may refer to functionality available in newer versions of mediawiki.
How we learn and modify the tools we use to write and edit code. The trade-offs between using something we're comfortable with versus trying to pick up and become proficient with new tools. Sublime and vim and emacs and VisualStudio Code and all their plugins and ways of integrating with services and supporting different languages.
The Language Server Protocol for standardizing how editors can provide "smart" features like autocomplete for different languages and projects.
Synchronizing work-in-progress code. Is Git too much overhead? Maybe! Dmitri likes using Dropbox.
Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, April 4th at 6:30pm!