#meta 2018-01-12

2018-01-12 UTC
tantek, j12t and vivus joined the channel
#
tantek
aaronpk, might be worth having webmention.rocks link to https://indieweb.org/Webm1m with a similar banner
#
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)
#
Loqi
Ok, I'll tell them that when I see them next
#
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?
#
Loqi
Ok, I'll tell them that when I see them next
#
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
#
Loqi
Ok, I'll tell them that when I see them next
#
Loqi
[Ryan Barrett] 1 Million Webmentions
#
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
#
Loqi
Ok, I'll tell them that when I see them next
[chrisaldrich], tantek, sebsel, AngeloGladding and [xavierroy] joined the channel
#
Zegnat
is working on the HWC event page again
#
Zegnat
I 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
#
Zegnat
Is the “When” section actually accurate still? What HWCs start at 17:30?
#
Zegnat
Amsterdam, Nürnberg, London, Baltimore, they all seemed to have later start times.
#
Zegnat
I was also asked to see if vHWC EU could start later to give people time to get home from work.
#
sknebel
noticed 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
#
sknebel
which I guess hasn't been done for permalink reasons?
#
Zegnat
Not sure. Would the event page make sense as an h-feed of h-event objects maybe?
#
sknebel
feed, or just top-level objects?
#
Zegnat
Theoretically a feed would make it possible to subscribe and watch as events are added to the page, right?
#
Zegnat
Let me just get the page up for next-hwc, then I’ll start a subpage on my user so we can try out some stuff!
#
Zegnat
(Or I can try out some stuff and you can complain.)
#
sknebel
Zegnat: do you mean /events or the individual hwc page?
#
sknebel
I was talking about the latter
#
Zegnat
individual
#
vanderven.se martijn
created /events/2018-01-24-homebrew-website-club (+5209) "Clone 2018-01-10. Assume Nürnberg, London, and SF are happening. Remove Regrets section."
(view diff)
#
vanderven.se martijn
edited /Events (+3) "/* April */ Even though chat lines didn’t change unique ID, they did change date in the URL..."
(view diff)
[sebsel] joined the channel
#
sknebel
jeremycherfas++ good edits for the intro text
#
Loqi
jeremycherfas has 1 karma in this channel (11 overall)
#
Zegnat
There 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.
#
jeremycherfas
My mistake
Loqi, [mlopatka] and vivus joined the channel
#
aaronpk
I just got a cpu alert
#
sknebel
good morning aaronpk
#
aaronpk
Oh I think Linode might be doing maintenance on my DB server
[mlopatka] joined the channel
#
aaronpk
hm, DB server rebooted and mysql is not starting up
#
aaronpk
and back
#
aaronpk
k all fixed! that was weird
#
aaronpk
That's awesome that the chat logs still log even when the db server is down
[eddie] joined the channel
#
Zegnat
Chat logs go straight into QuartzDB?
#
aaronpk
there isn't even a database connection made anywhere in that code anymore
#
Zegnat
That's good for logs. If file io fails you have different problems, haha
#
Loqi
nice
#
aaronpk
lol yeah
[colinwalker], [kevinmarks], gRegorLove, tantek and [xavierroy] joined the channel
#
tantek
alright, newsletter fixup time
#
tantek
what happened to the HWC Seattle location info here? https://indieweb.org/this-week/2018-01-12.html
#
tantek
schmarty: any photo for HWC Baltimore?
#
sknebel
seatlle loc has no marked up city
#
tantek
where? on the event permalink?
#
tantek
ok I think I fixed it but Loqi is not reporting wiki edits
#
Zegnat
Maybe Loqi’s db connection is still dead? aaronpk?
#
Zegnat
(DB was dead earlier, taking down indieweb.org)
#
aaronpk
Loqi doesn't use a DB for much either
#
Zegnat
Not to monitor wiki edits either?
#
aaronpk
no, the wiki sends those directly to Loqi via its recentchanges hook thingy
#
Zegnat
Then I guess something else is being wonky.
sebsel, tantek, [miklb], [colinwalker], [cleverdevil] and j12t joined the channel
#
Zegnat
The 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.
#
Zegnat
Alright. Request for comments. A more straight forward HWC page with every HWC being its own h-event: https://indieweb.org/User:Vanderven.se_martijn/hwc-template
#
Zegnat
The 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.
#
sknebel
Zegnat++
#
Loqi
zegnat has 22 karma in this channel (167 overall)
#
aaronpk
I like the precedent that sets for the eventual move to Calagator, where each city will be its own event as well
j12t_ joined the channel
#
Zegnat
The way this has been running, I felt like most cities are already running it as their own event anyway?
#
Zegnat
And 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!
#
aaronpk
even on separate websites
#
Zegnat
I 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.
#
Zegnat
Also 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
#
tantek
I like the simplifications re:regrets, and sort of re: when / what
#
tantek
the problem is "as separate events are clear separately contained divs that can be cut and pasted" <-- this is more error prone unfortunately
#
tantek
as we just saw with Seattle not getting the h-card right for the venue / city
#
tantek
this is why it is better to have just one h-event for the page
#
tantek
though the mix of one event, multiple locations, was also differently confusing
#
tantek
I'm just afraid that making every city get their h-event right will introduce *more* fragility, not less
j12t joined the channel
#
tantek
re: what. the "what" is too long to be up top like that now
#
Zegnat
People 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.
#
tantek
people 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
#
tantek
Zegnat: what part about adding extra h-event markup being required does not seem like adding extra fragility to you
#
tantek
getting two microformats marked up properly is harder than just getting one marked up properly - and harder = more fragile - is that not obvious?
#
tantek
people were getting timezones wrong *in the visible text*
#
tantek
no amount of markup futzing or adding mark up will fix content problems
#
Zegnat
The 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
#
tantek
no I disagree - very few people ever markup timezone information in an event
#
tantek
so therefore your assumption "isn't that hard" [for people] is false
#
tantek
because if they have never done it, I guarantee it is more "hard" than "easy"
#
tantek
I think you're underestimating sources of human error
#
Zegnat
The 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
#
tantek
how much of actual variance do we have with relative datetimes?
#
Zegnat
The 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
#
Zegnat
7 HWCs this year so far, 2 on the 17:30 time slot of those, if I count correctly.
#
Zegnat
Sorry, no, 3. But the third (vHWC) is probably moving as sknebel proposed that to me.
j12t_ joined the channel
#
Zegnat
18:30 (Baltimore, London), 18:00 (Nürnberg), 17:30 (vHWC, Seatle, SF), 19:00 (Amsterdam). Brighton was originally planned 18:00 but cancelled.
#
sknebel
for 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)
#
sknebel
I like the shortened beginning section of the page
#
Zegnat
No, 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.
#
sknebel
which is why I was talking about the timezones :)
[kevinmarks] and j12t joined the channel
#
sknebel
it'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
#
Zegnat
Very. 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
#
sknebel
if you convert to UTC without timezone info you are doing it wrong ;)
#
Zegnat
SF HWC will be 2018-01-25T03:30Z. So you can’t even say the date part if 2018-01-24 for the entire page.
#
Zegnat
Unless you somehow trigger implied dates but also provide the PDT timezone in the SF event specifically.
#
sknebel
if you convert to UTC, which you have no reason to do IMHO
#
Zegnat
Maybe not. I just standardised the datetime values. Any of them are valid of course.
#
Zegnat
I 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
#
Zegnat
Definitely also a posibility. Just wanted to get the ball rolling on cleaning the page up a bit. And I personally like per-event events.
#
Zegnat
Actually, I’ll offload the final decision to sknebel or aaronpk, as I think they are the only people parsing those pages.
#
Zegnat
Judging 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.
#
sknebel
the 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)
#
sknebel
we could have per-city feeds with the actual times with individual events if there is interest in that
j12t joined the channel
#
sknebel
(and everything that can be built on top)
#
sknebel
the main channels for communicating HWCs still are outside the wiki, this isn't going to change this
#
Zegnat
Yes, but will this make e.g. communicating HWCs in the newsletter easier?
#
Zegnat
Because I would see that as a big gain
#
sknebel
we could show the start times there
#
sknebel
(I don't actually think the newsletter is relevant for communicating HWCs, but I might be wrong)
j12t, [keithjgrant], [mrkrndvs], j12t_, [kevinmarks] and tantek joined the channel
#
tantek
reloads this-week
#
tantek
looking good! four photos! great
#
tantek
if you're hosting HWC in your city, please add it to the summary event(s) on https://indieweb.org/Events#Upcoming - that ought to do the trick
#
tantek
catching up in here
#
tantek
actual "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)
#
tantek
the quiet writing hours are more different - but perhaps that's ok, as that's not the primary focus on the meetup
#
tantek
and ok to not markup
#
tantek
sknebel, 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
#
tantek
(which shows up in the newsletter)
#
sknebel
not 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
#
tantek
perhaps we need to compress the event stuff then - as the current layout isn't very efficient
#
tantek
also, "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
#
sknebel
weekly digest of indienews and the wiki edit section is apparently something people like to keep track of what's going on once a week
#
sknebel
ughs, grammar. tired.
#
aaronpk
I think the photos are important, but we could definitely compact the event section some
#
aaronpk
maybe upcoming events are not the most important thing for example
#
tantek
they are in terms of planning
#
aaronpk
also maybe we drop the event descriptions entirely, and just list name/locations/link
#
tantek
the other random updates are all passive
#
aaronpk
I chose that order based on what I thought was most actionable at the top
#
tantek
after the most visually appealing - the photos
#
aaronpk
ah yea
#
tantek
which 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
#
tantek
how to join IRL
#
tantek
rather than just yet another rando internet group / mailing-list / IRC etc
#
sknebel
there's different audiences certainly
#
tantek
IRL > online
#
tantek
which is why the events matter
#
sknebel
that 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
#
tantek
just ask GWG how much he wishes there was a HWC NYC
#
tantek
he's asked for folks numerous times here (in various chat channels)
#
gRegorLove
sknebel, Do they definitely want it as an email? Could subscribe to h-feed of indienews instead?
#
tantek
sknebel: "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
#
tantek
when everything you read is text, you can't tell what's human and what's not
#
tantek
as 2016 demonstrated :P
#
sknebel
I'm talking about people that go to events and stuff
#
sknebel
still doesn't mean that info about HWCs somewhere else in the world is very relevant to them
#
sknebel
that's why I think it's different audiences
#
sknebel
gRegorLove: yes, the weekly digest thing and explicitly mentioned the wiki summary seem important
#
tantek
if you go back to before the photos, biggest complaint was wall of text by far
#
tantek
sknebel: I don't actually believe you that there are non-trivial audiences interested in weekly walls of text
#
sknebel
understood, will not rely feedback again
#
sknebel
good night
#
Loqi
see you in the morning!
#
tantek
something to consider re: audiences - "This Week" is the closest thing we have to regular outreach to the "next generation"
#
tantek
that is, if gen 1 folks want one thing from "this week", and gen 2 folks want something different, we should be optimizing for gen 2, not gen 1
#
tantek
gen 1 folks are either already here, or already subscribed to various rando RSS feeds (wiki recent changes etc.)
#
tantek
aaronpk, any chance of fixing the "X is /Y" handling in Loqi to minimize redirects?
#
tantek
e.g. if Loqi is handling "X is /Y" to create a redirect, before doing so, Loqi should follow /Y to /Y_actualpage and create a redirect to that
#
aaronpk
I wasn't aware there was a problem
#
tantek
e.g. see example from above, I looked for Facebook Algorithm, thought I'd found it, then did FB Algo is /Facebook_Algorithm
#
tantek
now go look at /FB_Algo
#
tantek
sorry - example from above is in #indieweb
#
tantek
(just fixed /FB_Algo to only have one redirect)
#
tantek
here is the double-redirect that Loqi created: https://indieweb.org/wiki/index.php?title=FB_Algo&oldid=44259
#
tantek
also missing, did the newsletter go out?
#
tantek
since it's after 15:00 PST
strugee, [colinwalker], [kevinmarks] and vivus joined the channel