@cafenunDas NUN erwacht aus dem Winterschlaf!
Am Mittwoch starten wir mit dem HOMEBREW WEBSITE CLUB – KARLSRUHE.
Am Donnerstag geht es mit KLANGWERK weiter.
Am Freitag werden wir mit TO BE WE das erste Konzert in diesem Jahr abfeiern!
Beginn: 20:30 Uhr
Eintritt: frei
❤️ (twitter.com/_/status/1087311210213769216)
LoqiThe IndieWebCamp community is planning numerous upcoming events, including future IndieWebCamps, regular Homebrew Website Club meetups, talks, and other proposals — if you'd like to help, please contribute to this page! https://indieweb.org/Planning
@TaylorJadin↩️ That's awesome. I haven't seen too many IndieWeb folks doing doing syndication on JAM stack so I think it's worth writing up how you did it and crossposting that to the wiki (twitter.com/_/status/1087327039957491712)
vanderven.se martijnedited /Planning (+38) "/* 2019 */ Interested in both Germany events, though probably forced to pick only 1 at some point" (view diff)
ZegnatBut I think having a nice kick-off and a clear end time for demos is good. Then people can work on their stuff at their own pace in between, much like with the physical events
jgmac1106@zegnat yes we are going for shared kick off and demos bioth EU and NA, we are going to offer Aussie folks the chance to schedule their own if we get interest and organizer
jgmac1106aligning all three impossible. @eddie @zegnat @gwg @chrisalrdrich home all day so I can hop in at different time points wiith different folkgs
@featherOn the left: my blog logo from 10 yrs ago. On the right: my current blog logos. Need to make some changes...
#10yrchallenge #indieweb #2019goals (twitter.com/_/status/1087375960901468161)
[davidmead], [xavierroy] and [schmarty] joined the channel
[tantek]Two things. 1 you basically described what motivated the creation of Lanyrd (back when it was a passion project), including like maybe 90%+ of the same/overlapping use-cases of collecting and linking out to all the stuff "about" an event
[tantek]2 yes this is a hard problem, and the reason you're overwhelmed after outlining it is there are too many moving / unknown / unbuilt pieces to "keep it all in your head"
[tantek]3 if you can break it down to building blocks that are each useful on their own, and you can (help) solve one a time, maybe even in a community, it may (will) get less overwhelming
[tantek]4 one of the most "obvious" building blocks that's needed there are event permalinks, aka /event posts, which itself is a non-trivial thing to build, and yet, an essential piece of any "events site" that you would build (as you figured out when you added up all your requirements)
[tantek]5 this is why I strongly believe in iterating on /event posts (and related /rsvp/invitation/photo-reply posts etc.) here in the community, because collectively / in a distributed fashion, we have the best chance of making this/these work, and incrementally improving them until the interactions all feel smooth and good
[tantek]6 as the community solves the "event permalink" problem you (re)identified, then anyone can (re)think up what an event "aggregation" (what you call a list) would/could look like *on another site*
[tantek]and then /events would "just" link to those - this would all automtically work today (e.g. for the newsletter) because the stuff that consumes /events and the individual event pages just 1 follows a link, 2 parses it for h-event
[tantek]as long as Kaja creates event lists marked up with h-event (and backcompat hCalendar), we can use H2VX to auto-generate an ICS for subscribing in e.g. iOS iCal.app
[schmarty]but there are other cases where i would prefer to host the event permalink on a site other than my own. for example, my improv show GHOST PARTY has its own website.
[tantek]my larger point is, yes it's a big problem, therefore break it down into individually useful building blocks, the most obvious of which is event posts / permalinks, so keep iterating on those and responses to them until that building block works smoothly
[tantek]or if you want to work on the aggregations/lists piece then great, work on consuming h-event s from elsewhere (like from the wiki, our own sites etc.), not on making your own new event permalinks. focus on one piece or another, not trying to build all the pieces at once yourself
[schmarty]in my recollection we came up with something buildable for individual city HWCs permalinks/RSVPs/photos/blog posts that also works with aggregation.
[tantek]schmarty, we could start by literally re-using the headings from the home page and building manual lists on the individual city pages. e.g. "Upcoming Homebrew Website Club meetups", "Upcoming IndieWebCamps"
[tantek]if we re-use the headings from the home page, perhaps it will be easy/easier for Kaja to be updated to "just" update city-specific lists on those pages
[tantek]schmarty, when you do find (or feel free to braindump) "something buildable for individual city HWCs permalinks/RSVPs/photos/blog posts that also works with aggregation" please add it to a new subsection here: https://indieweb.org/Homebrew_Website_Club#Brainstorming
[schmarty]that could work! i plan to keep making individual city pages (to the extent that i am now an HWC NYC co-organizer) and would love to start work on showing responses automatically via webmention.
[tantek]I feel it is more work to show "responses" on a mediawiki page, than it is to keep iterating on indie /event posts many/most of which can already show responses
[schmarty]i am still torn about having the events on my site. specifically, i am no longer an organizer for HWC Baltimore and it feels odd to have my site be the "home" for these events.
[tantek]past events are fine on your site. I think it's great to show the individual diversity of who helped what during any period of indieweb community development!
[tantek]I found https://chat.indieweb.org/2011-02-12 where the "Prev" button is greyed out so presumably that's our oldest archive of the channel. Maybe when we started it? From the chatter there, it sounds like the site was setup already, which seems curious. I'd have expected channel chatter before the site setup
[schmarty]oof, i don't think we captured all of the three-tracks homepage redesign stuff we talked about at /2018/Organizers (where we discussed "IndieWeb Meetup" (beginner) vs "HWC" (advanced) vs "WordPress Meetups" (the one that made me exclaim "omg i organize a wordpress meetup and i don't even use wordpress")
[tantek]GWG, maybe? I mean at this point we need more just capturing of all the ideas onto the wiki, which anyone can do who was there, asynchronously. no need to bottleneck on any discussion
[tantek]and even then, anyone interested can start to play with prototype structure / content / style on a sub-page of their wiki user page if they like
[tantek]!tell sknebel are we ready to switch to using city-specific HWC event wiki pages for February (and have Kaja auto-create aggregates per date)? Or should we do February like we did January and postpone the switch another month?
LoqigRegorLove_: [tantek] left you a message 1 week, 2 days ago: WDYT of adding an event_photo field to https://indieweb.org/Template:one-day-event so we can easily add a photo URL (maybe show thumbnail?) to the h-event that it generates to more easily get a photo from an event to show-up in the newsletter (rather than always having to create a separate one-off page after the fact for an indieweb-related event that happened to have a photo)
[tantek]We have enough events on enough days in /timeline that it makes me wonder what would it take to have an "On This Day" box for IndieWeb major events (things from /timeline)
aaronpkrelatedly, i'm currently working on updating my quarterly review summary and wondering what this might look like to automate it and turn it into a digest format that's fun to read
[tantek][schmarty] I sympathize with how much work it took *every* week to do the This Week podcasts. Would monthly be "easier"? Or just as much work as doing it every week for a month?
[schmarty]i'd like to figure out some processes to make the TWITIWAE summarizing more piecemeal (which could also be more collaborative and enhance the published newsletter)
[schmarty]tantek: a lot of TWITIWAE time is spent reading through wiki page diffs to see if anything "notable" happened. some automation and pre-filtering could save a lot of time there.
[tantek]that's a good insight. I wonder if that's a clue that we could improve the quality of the signal in the "changed wiki pages" portion of the newsletter
aaronpksure, not a huge deal to bump that up. it does involve a lot of crawling so i'm not sure every 30 minutes is a good idea, but I can definitely add a bunch more regens
[tantek]weekly filtering / summarizing analysis could be helpful with auto-generating *personal* newsletters for folks that want a weekly summary instead of reading all your posts
[tantek]I really dislike the weekly summary from Swarm - see what your friends were up to - always massive FOMO-inducing and feelings of not having "done" enough 😕
[tantek](and I assume that means my prolific Swarm checkins may be unintentionally having a similar affect or just annoying people in their "see what your friends were up to" summaries 😕 )
[tantek]Since it's possible to automate decent monthly summaries (as [cleverdevil] has), it must be similarly possible to automate decent weekly summaries
[schmarty]aaronpk: i went looking for a permalink for the most recent percolator on your site so i could reply to you somewhere we could have a back-and-forth