#tantek!tell snarfed any way to get the response type (if any) of all the Bridgy (and other services's) webmentions? e.g. #/% comments, likes, reposts, rsvps, bookmarks, reacji, homepage mentions, other. I know webmention.io has that data. webmention.heroku should too (both offer response type specific APIs/embeds)
#tantek!tell aaronpk any way to tell what #s / %s of the webmention.io and Telegraph webmentions are what type of /response ? comment, like, repost, rsvp, bookmark, reacji, homepage mention, others?
#tantek!tell snarfed would be worth updating https://snarfed.org/1-million-webmentions with the % response types, that will help really hit home the user-visible impact that webmentions have had
#tantek!tell snarfed and third, re: "Long tail: Unknown; estimate 5-50k", presumably indiemap has crawled enough of our indieweb blogs / posts to be able to discover when/how many indieweb *posts* have how many in their comments sections to indieweb *responses* permalinks - each of those you should be able to count as at least one successfully sent webmention (not counting updates0
#ZegnatI am removing the “Regrets” header. I would rather we focus on getting people to RSVP at all. I also can’t find a single 2017 HWC that had someone put there name on Regrets.
jeremycherfas joined the channel
#ZegnatIs the “When” section actually accurate still? What HWCs start at 17:30?
#ZegnatAmsterdam, Nürnberg, London, Baltimore, they all seemed to have later start times.
#ZegnatI was also asked to see if vHWC EU could start later to give people time to get home from work.
#sknebelnoticed that too, thought about adding some weasel-words before that
#sknebel(the actual event markup is going to be wrong for some anyways, can't fix that without turning each city into their own h-event
#sknebelwhich I guess hasn't been done for permalink reasons?
#ZegnatNot sure. Would the event page make sense as an h-feed of h-event objects maybe?
#ZegnatThere used to be a separate category for the virtual HWCs, but it was decided to move them into their specific timeslot as all the events on the page are supposed to be sorted by start time. Thus vHWC Americas and vHWC EU have their separate headings.
#aaronpkno, the wiki sends those directly to Loqi via its recentchanges hook thingy
#ZegnatThen I guess something else is being wonky.
sebsel, tantek, [miklb], [colinwalker], [cleverdevil] and j12t joined the channel
#ZegnatThe header structure has been flattened. “Regrets” wasn’t used in a year, so it is out. “When” was mostly inaccurate as we see HWCs picking different times to fit their audiences, so it is out. “What” has simply become the main description at the top of the page.
#ZegnatThe hope is that this makes it slightly easier to start the page, as separate events are clear separately contained divs that can be cut and pasted, and that code for things like the newsletter and Kaja for automatic wiki updates can more reliably parse the event information.
#ZegnatAnd this way, if people are using selfhosted indie events (like the London crew) they can use that as the u-url of the h-event on the wiki as well!
#ZegnatI foresee having to watch the HTML like a hawk for the first few weeks. But once everyone has the event HTML of their city ready to copy and paste that issue should disappear.
#ZegnatAlso thanks to jeremycherfas for fixing the text at the top up for me while I was fuzzing with event markup!
j12t and j12t_ joined the channel
#tantekI like the simplifications re:regrets, and sort of re: when / what
#tantekthe problem is "as separate events are clear separately contained divs that can be cut and pasted" <-- this is more error prone unfortunately
#tantekas we just saw with Seattle not getting the h-card right for the venue / city
#tantekthis is why it is better to have just one h-event for the page
#tantekthough the mix of one event, multiple locations, was also differently confusing
#tantekI'm just afraid that making every city get their h-event right will introduce *more* fragility, not less
j12t joined the channel
#tantekre: what. the "what" is too long to be up top like that now
#ZegnatPeople were also getting timezones wrong copy pasting, and those have never been included in any of the microformats. Copying a wrong h-card is just as likely. I don’t see this adding extra fragility there.
#tantekpeople coming to an event typically want nothing more than a *short* (like 2-3 lines tops) description, the key information is Where and When
j12t_ joined the channel
#tantekZegnat: what part about adding extra h-event markup being required does not seem like adding extra fragility to you
#tantekgetting two microformats marked up properly is harder than just getting one marked up properly - and harder = more fragile - is that not obvious?
#tantekpeople were getting timezones wrong *in the visible text*
#tantekno amount of markup futzing or adding mark up will fix content problems
#ZegnatThe part where someone had to already go through wiki gardening to fix timezones that people weren’t copying right. If you have to go through anyway, this isn’t that hard to add.
j12t__ joined the channel
#tantekno I disagree - very few people ever markup timezone information in an event
#tantekso therefore your assumption "isn't that hard" [for people] is false
#tantekbecause if they have never done it, I guarantee it is more "hard" than "easy"
#tantekI think you're underestimating sources of human error
#ZegnatThe only thing this is adding as far as mf2 goes is correct start and end times (these were lacking before making the event mostly useless anyway) a single div element (where people previously were expected to copy the right amount of --- for a separator anyway) and a single p-name within the header.
j12t___ joined the channel
#tantekhow much of actual variance do we have with relative datetimes?
#ZegnatThe virtual EU one will probably move to accommodate people commuting after work. At that point I think not a single EU event is on the 17:30/18:30 time slot that was previously mentioned.
j12t joined the channel
#Zegnat7 HWCs this year so far, 2 on the 17:30 time slot of those, if I count correctly.
#ZegnatSorry, no, 3. But the third (vHWC) is probably moving as sknebel proposed that to me.
j12t_ joined the channel
#Zegnat18:30 (Baltimore, London), 18:00 (Nürnberg), 17:30 (vHWC, Seatle, SF), 19:00 (Amsterdam). Brighton was originally planned 18:00 but cancelled.
#sknebelfor non-remote events timezones aren't that important, so no need to keep them IMHO, at least not without a consuming use case. (and since wiki-consuming code tends to be custom for now, guessing timezones is sort of possible, at least from what I've seen with IWC pages)
#sknebelI like the shortened beginning section of the page
#ZegnatNo, but accurate time (even without timezone) is. And as 1 event of the page, only reporting from the “When” section, it just didn’t express correct times at all.
#sknebelwhich is why I was talking about the timezones :)
[kevinmarks] and j12t joined the channel
#sknebelit's to bad it seems like we're going to need the <time> elements, but getting the date somewhere page specific if at all possible is going to be hacky
#ZegnatVery. We can’t get times through implied times because they differ. If we try to do implied date parts only, you have to be very careful with timezones, because PDT is actually organised on a different date when converted to UTC (unless I messed up my timeconversion)
j12t_ joined the channel
#sknebelif you convert to UTC without timezone info you are doing it wrong ;)
#ZegnatSF HWC will be 2018-01-25T03:30Z. So you can’t even say the date part if 2018-01-24 for the entire page.
#ZegnatUnless you somehow trigger implied dates but also provide the PDT timezone in the SF event specifically.
#sknebelif you convert to UTC, which you have no reason to do IMHO
#ZegnatMaybe not. I just standardised the datetime values. Any of them are valid of course.
#ZegnatI just realised: nowhere on that page does it say on what date the events are 😅
#sknebel(just to have it mentioned, for a one event-per-page design we also could get rid of the explicit time in mf2 and intro text completely. people reading are going to read, parsers are at least not reporting a wrong time)
j12t joined the channel
#ZegnatDefinitely also a posibility. Just wanted to get the ball rolling on cleaning the page up a bit. And I personally like per-event events.
#ZegnatActually, I’ll offload the final decision to sknebel or aaronpk, as I think they are the only people parsing those pages.
#ZegnatJudging from who actually ends up editing those pages I do not think it actually adds too much fragility on top of errors we were already seeing copy-pasting.
#sknebelthe parsing we do right now doesn't really care as far as I can tell, since it's limited around the limitations of the current approach
#sknebel(as in, sure code has to be adjusted, but that's easy)
#sknebelwe could have per-city feeds with the actual times with individual events if there is interest in that
#tantekactual "IndieWeb meetup" part of HWC in various cities seems to be predominantly 18:30 (Balitmore, London, Seattle, SF), one 18:00 (Nürnberg), and one 19:00 (Amsterdam)
#tantekthe quiet writing hours are more different - but perhaps that's ok, as that's not the primary focus on the meetup
#tanteksknebel, re: newsletter is relevant for communicating HWCs, well, co-organizers need to add their cities to /Events#Upcoming HWC events, so far only SF is on Feb-Mar HWCs
#sknebelnot sure how that is related to the question if people actually use the newsletter to get informed about events. My impression from talk between organizers was that it isn't, and I even got people asking if there maybe is a hidden version of the newsletter without all the event stuff
#tantekperhaps we need to compress the event stuff then - as the current layout isn't very efficient
#tantekalso, "without all the event stuff" = zero photos = boring wall of text - so people asking that are basically asking for something that they will ignore even more
#sknebelweekly digest of indienews and the wiki edit section is apparently something people like to keep track of what's going on once a week
#tantekwhich makes sense, get people more interested, photos are emotionally appealing, make you want to read more, then the very next thing is how to meet some of those people - at the next events
#sknebelthat makes sense for someone finding the newsletter online/getting it forward as "look at this"/..., less so for someone subscribing to the mails to get kept up-to-date
#tantekjust ask GWG how much he wishes there was a HWC NYC
#tantekhe's asked for folks numerous times here (in various chat channels)
#gRegorLovesknebel, Do they definitely want it as an email? Could subscribe to h-feed of indienews instead?
#tanteksknebel: "to get kept up to date" - events with real people demonstrate actually healthy human community - rather than just yet another aggregation of random internet stuff that could be generated by robots
#tantekwhen everything you read is text, you can't tell what's human and what's not