aaronpkit's misleading to show RSVPs on events.indieweb.org when there's also a ticket link elsewhere, since people may think that posting the RSVP is enough
[tantek]do we have instructions for how to create/clone a page on 2020.indieweb.org for this? I feel it's still something that is non-obvious (there are multiple folders/files to create etc.)
[tantek]foo is jargon that is sometimes used in computer language programming examples to express the name of a variable, usually with another variable βbarβ, to illustrate a concept or algorithm; FOO is also an acronym for βFriends Of O'Reillyβ typically seen in the phrase βFoo Campβ, the predecessor of [[BarCamp]], which the IndieWeb community uses as a model for [[IndieWebCamps]].
[tantek][schmarty] would you consider a re-imagined TWITIW podcast that was live interview-based rather than script based? E.g. start with your usual pre-recorded intro, then do a live interview with whichever community volunteers you've gotten to commit to your Friday afternoon/evening timeslot that week (perhaps 1-2 minimum, max 3?) and prompt *them* to pick out something from the newsletter to share / expand on, then close the podcast with your
[tantek]That would eliminate the (your) time spent researching everything mentioned in the newsletter, and hopefully minimize subsequent editing as well to "mostly" prepending intro/outro. They might be a bit longer (like 15 minutes instead of 5) but I think that's ok? Anyway, just a thought if you ever feel a draw to attempting a re-imagined weekly indieweb podcast.
[schmarty]tantek: that is a cool idea! i have been playing with some of the tech to do livestreams where the audio can be extracted into a final podcast.
[tantek][schmarty] to be clear this is mere ideating, not voluntelling or shaming or pressuring in anyway. If it's not something that inspires you like YEAH! then it's totally ok to ignore. π
[schmarty]haha, thanks. i like the pitch! your proposal really helps knock down some of the major challenges by timeboxing it and spreading out the effort of choosing what to report on and how to summarize it.
[schmarty]one hang-up i have about taking it on myself is coordinating with volunteers each week. i don't want to lean too heavily on the same people, for example, so there's work to be done with outreach. particularly important would be working to make sure e.g. white cis male voices are not over-represented. π€
[tantek][schmarty] I'm willing to help with coordinating with volunteers each week to help with sharing that part of the responsibility. I am sensitive to and agree with your concerns about overrepresenting white cis male voices.
[tantek][schmarty] I do think we'd want to pick from folks who are semi-active in chat so they have a context for what is already in the newsletter and speak to it meaningfully (with zero prep time), rather than burdening someone inactive with doing research (and thus adding work for someone that may already be burdened).
[schmarty]tantek: very true! and reminds me of the timezone issue when doing a live show, haha. i could see pre-recording a segment or two just before or after an online HWC.
[snarfed]ok! as long as that can happen fast at least. if not, pointing to the existing page might be a worthwhile stopgap to make sure we don't lose any possible attendees who see the other pages first