18:03:24 RRSAgent has joined #social 18:03:24 logging to https://www.w3.org/2017/11/14-social-irc 18:03:26 RRSAgent, make logs public 18:03:29 Meeting: Social Web Working Group Teleconference 18:03:29 Date: 14 November 2017 18:03:45 I'm going to wait till 5 after the hour 18:03:54 present+ 18:04:08 present+ 18:04:22 present+ 18:04:29 IRC only for 5-10 minutes 18:04:30 sorry (again) 18:04:37 present+ 18:04:42 scribe please? 18:04:57 I can scribe 18:05:03 scribenick: rhiaro 18:07:03 Zakim, who is here? 18:07:03 Present: tantek, cwebber, npdoty, annbass, hadleybeeman, snarfed, torgo, rhiaro, ajordan, eprodrom 18:07:06 On IRC I see RRSAgent, eprodrom, ajordan, JanKusanagi, bengo, cdchapman, rowan, xmpp-social, csarven, dlehn, flackr, KjetilK, hadleybeeman, Zakim, Chocobozzz, Loqi, aaronpk, er1n, 18:07:06 ... cwebber2, adam, dlongley, DenSchub, jungkees, jaywink, raucao, saranix, bwn, erincandescent, jet, rhiaro, ben_thatmustbeme, Gargron, sknebel, melody, mattl, bigbluehat, 18:07:06 ... surinna, bitbear, howl, dwhly, tsyesika, sandro, nightpool, trackbot, puckipedia 18:07:08 dialing in! 18:07:11 roll up roll up everyone 18:07:15 present+ 18:07:42 present+ 18:07:45 bad poetry / oh noetry 18:07:56 cwebber2: oh my god 18:08:08 TOPIC: Last week's minutes 31st Oct 18:08:31 PROPOSED: Approve https://www.w3.org/wiki/Socialwg/2017-10-31-minutes as minutes for 31 Oct 2017 telecon 18:08:52 +1 18:09:06 +1 18:09:11 +1 18:09:15 +1 18:09:24 +1 18:09:29 eprodrom: any objections? 18:09:37 RESOLVED: Approve https://www.w3.org/wiki/Socialwg/2017-10-31-minutes as minutes for 31 Oct 2017 telecon 18:09:40 present+ 18:10:02 Eprodrom made 2 edits to [[Socialwg/2017-11-14]] https://www.w3.org/wiki/index.php?diff=105207&oldid=0 18:10:02 Rhiaro made 4 edits to [[Socialwg/2017-11-14]] https://www.w3.org/wiki/index.php?diff=105211&oldid=105207 18:10:25 eprodrom: Switching the agenda around. Starting with TPAC, then WebSub then AP 18:10:27 tantek has joined #social 18:10:29 TOPIC: TPAC update 18:10:36 ... can Chris and/or sandro tell us what happened? 18:10:41 sandro: I missed my flight, I wasn't at that part 18:10:53 cwebber2: It was more of a social CG gathering, but still interesting and relevant 18:11:16 ... Off the top of my memory, we started off with introducing people and what's happening in this space 18:11:26 ... including one of the mastodon node hosters was there, toot.cafe 18:11:30 regrets+ 18:11:31 ... we demo'd two mastodon sites interoperating 18:11:33 ... it was adhoc 18:11:38 ... we then moved to discussing anti abuse tooling 18:11:51 ... and what we could do to get the ideas effective. a lot about distributed block lists and other things 18:12:05 ... and then it went into something that's not currently work in the socialcg but a favourite rathole of mine 18:12:14 ... what would it bel ike ifyou had a federated MUD or other federated game 18:12:18 ... There may have been other things 18:12:19 timbl has joined #social 18:12:25 ... But people were excited about social spaces with rules 18:12:25 (we discussed Vouch a bit too as part of anti-abuse) 18:12:33 ... any questions? 18:12:51 SocialCG meeting at TPAC: https://www.w3.org/wiki/SocialCG/2017-11-06 18:12:52 Social Web Incubator Community Group Meeting at TPAC https://www.w3.org/wiki/images/3/36/2017-11-06-socialcg-f2f.jpg 18:12:54 eprodrom: was there any discussion by any Members who showed up about either of the specs that we're working on right now? 18:12:59 jankusanagi_ has joined #social 18:13:04 cwebber2: there were some people from the TAG who were interested in this stuff 18:13:12 ... There were two separate meetings! I'm mixing them up 18:13:40 ... We had a conversation where the TAG showed up and I'm tryign to remember everything that happened there. We spent more time talking about .. we also had somebody from bridgy (snarfed Ryan Barrett) 18:13:48 ... that's where most of the conversation about the anti abuse tooling happened 18:13:56 eprodrom, there were questions about like should brands/companies just install and launch their own Mastodon instances? and we discussed the Monoculture problem 18:14:08 ... The TAG didn't know mastodon were using our protocol 18:14:17 (like if everyone "just runs Mastodon", then AP becomes the Mastodon API instead of an open standard) 18:14:27 ... The majority of the conversation was anti abuse tooling 18:14:41 eprodrom: I'm pretty surprised about that 18:14:50 ... it doesn't seem like the network is active enough that abuse is a problem 18:14:56 cwebber2: there's a LOT of active moderation on mastodon 18:14:59 ... that's one of the biggest topics 18:15:07 ... a lot of mastodon users are pretty happy is because mastodon builds in a lot of tooling 18:15:16 q+ 18:15:35 ... there has been a culture clash between people from different communities 18:15:38 q- 18:15:51 ... people are concerned about making sure it keeps working 18:16:13 eprodrom: Talking about tooling, you mean like spam filters? Or is it more like stuff that's built into particular networks like silencing and so on? 18:16:21 cwebber2: people are interested in all of that across the board 18:16:38 ... there's the general feeling that we have to explore a number of different approaches and it's not clear which arethe most accessible or that we might need a combination ot really get the job done 18:16:41 q? 18:16:44 q+ 18:16:50 ... a lot of people are really interested in federated block lists and a web of trust and distrust 18:16:57 ... There was one more topic that was pretty big 18:17:06 https://github.com/tootsuite/mastodon/issues/177#issuecomment-344056590 18:17:08 [nightpool] Me and @Gargron and a couple other developers had a chat on Saturday, and we decided that this is currently the highest priority enhancement for us as a project. We hope to have at least partial fixes for this emerge soon, things that address some of... 18:17:11 ... and is increasing because it looks like this is going to be the next major topic in mastodon 18:17:17 ... is account migration 18:17:21 ... still a big issue that people are really intersted in 18:17:37 ... how to handle if your server goes down or you want to move for whatever reason 18:17:49 ... maybe you want to move becus eyou're not happy with the moderation policies, or you're not happy because.. or you want to host your own 18:17:58 ... These remain the two biggest conversations in the CG 18:18:03 q- 18:18:10 ... interesting also to see that the people who showed up without prior experience also wanted to talk about these issues 18:18:13 eprodrom: really interesting 18:18:18 ... definitely interesting questions 18:18:22 ... migration is a pretty fun one 18:18:33 ... a lot of stuff that does not necessarily seem to be standards questions 18:19:04 scribe? 18:19:41 I will 18:19:49 scribenick: bengo 18:20:02 Eprodrom made 2 edits to [[Socialwg/2017-11-14]] https://www.w3.org/wiki/index.php?diff=105214&oldid=105211 18:20:02 Strugee made 1 edit to [[Socialwg/2017-11-14]] https://www.w3.org/wiki/index.php?diff=105213&oldid=105212 18:20:03 eprodrom is there a cg meeting tomorrow? 18:20:06 cwebber2 no, next week 18:20:15 q+ 18:20:21 eprodrom there will be some things that are patterns, some are one-off APIs, other things that might be standardized 18:20:24 ack sandro 18:20:47 sandro my perception of mastodon is that the community there polices in a way that there are good people and bad people 18:21:09 rhiaro (take scribe back?) 18:21:21 sandro I happen to agree with their notion of good peopel and bad people, but not their policing 18:21:41 sandro obviously you could have a fork where someone uses a fork and deploy a node cut off from mian network 18:21:46 scribenick: rhiaro 18:21:53 eprodrom: it's interesting to see how these patterns work out 18:21:59 ... I think those are things we can talk about at the CG 18:22:15 eprodrom: wondering if we can do AS2 since I have to leave 18:22:25 ... tantek, anything about TPAC? 18:22:30 we can postpone too 18:22:44 no no no 18:23:01 rhiaro, sounds like cwebber2 covered it :) just dropped in the wiki page for our first SocialCG f2f! https://www.w3.org/wiki/SocialCG/2017-11-06 18:23:02 Social Web Incubator Community Group Meeting at TPAC https://www.w3.org/wiki/images/3/36/2017-11-06-socialcg-f2f.jpg 18:23:28 and npdoty took decent notes too in IRC https://socialwg.indiewebcamp.com/irc/social/2017-11-06#t1510012696205 18:23:29 [tantek] hey hey we're in the SocialCG f2f at TPAC!!! 18:23:42 TOPIC: WebSub 18:23:45 eprodrom: sandro, upate? 18:23:59 sandro: I'm a little confused about process here. There are two comments and I believe they are technically member confidential 18:24:05 ... I don't know how the group is supposed to respond to that 18:24:33 ... they both request the change but don't require it 18:24:46 sandro, I believe there is only substantive comment (HTTPS must vs should) 18:24:53 s/only/only one 18:25:21 the other is editorial about the WBS system vs what the spec says 18:25:40 sandro: one is that HTTPS should be a MUST rather than a SHOULD 18:25:54 ... our reply to that is that we can't for back compat 18:25:56 which we should log in GitHub and discuss 18:26:05 yes exactly. agreed with sandro 18:26:10 eprodrom: have we talked about this before? 18:26:12 aaronpk: I don't think we have 18:26:14 we can even resolve on that if someone can create the issue in GH fast enough :) 18:26:40 q+ 18:27:04 aaronpk: I agree we don't have to require it because it uses the secret to verify the payload 18:27:22 ... HTTPS just provides privacy on the transport, which is not a guarantee that we are claiming to make 18:27:38 ... The spec should be concerned about successfully delivering notifications, which can be verified by HTTPS or the secret 18:27:43 sandro: but if you don't use https when you send the secret? 18:27:48 The compat argument is the strongest one IMO 18:27:55 aaronpk: the hashing mechanism verifies the payload even over http 18:28:08 https://www.w3.org/TR/activitypub/#obj-id it's a SHOULD in ActivityPub 18:28:44 cwebber2: it's a SHOULD in AP because it might have some sort of use inside a corporate network with http 18:29:03 ... 2 is that you may use it with a scheme that's not http at all. At Rebooting WoT something about ids 18:29:21 ... URIs have schemes beyond http and https. I feel like that's a reasonable justification here 18:29:28 eprodrom: in AP they act as identifiers so that's fine 18:29:38 ... in websub we're talking about actual endpoints that are being used for posting and retreiving things 18:29:40 ... so it's a bit more important 18:30:01 ... it sounds like the question is is the verifiability of http with extra parameters in websub sufficient that we don't need to make this a MUST 18:30:05 ... and I think that that's the case 18:30:09 ... should we open and close an issue? 18:30:12 aaronpk: I guess so 18:30:18 eprodrom: Or we can have a resolution right now 18:30:24 aaronpk: let's resolve it on the call then we can reference a link 18:30:58 PROPOSED: retain HTTPS as a "should" or "recommended" requirement in WebSub 18:31:00 +1 18:31:04 +1 18:31:09 +1 18:31:10 +0 18:31:12 +1 18:31:17 sandro: I don't agree with the security claim but I do agree with the back compat 18:31:24 aaronpk: you don't agree that the hash is enough to verify the paylaod? 18:31:30 sandro: on the delivery it is but on the earlier part it isn't 18:31:35 +1 18:31:44 ... We don't say the hub must either do we? 18:31:55 ... it would be higher priority to make the hub do it 18:32:02 +1 for backward compatibility, extensibility 18:32:07 +1 18:32:08 eprodrom: basically we say it is strongly recommended 18:32:11 https://www.w3.org/TR/websub/#security-considerations 18:32:12 ... to use https for all requests 18:32:20 "It is strongly recommended to use HTTPS for all requests." 18:32:36 sandro: the notification endpoint, there's not that much reason but still probably a good idea 18:32:45 eprodrom: any objections? 18:33:00 RESOLVED: retain HTTPS as a "should" or "recommended" requirement in WebSub 18:34:25 sandro: second issue is editorial regarding editors list 18:35:47 ajordan has left #social 18:36:08 PROPOSED: add invited expert status for author and editors of WebSub 18:36:20 +1 18:36:20 +1 18:36:24 +1 as affiliation, in head matter 18:36:31 +1 18:36:32 ajordan_ has joined #social 18:36:38 +1 18:36:54 +1 18:37:15 eprodrom: any reservations to that? 18:37:24 RESOLVED: add invited expert status for author and editors of WebSub 18:37:48 eprodrom: do we need a proposal to publish? 18:37:52 sandro: at this point it's up to director not the WG 18:38:03 ... any other editorial changes? 18:38:06 uh, if they're employees of W3C members I'm not sure we can do that 18:38:11 like folks that work for Google 18:38:14 aaronpk: still a couple of open issues which might result in editorial changes 18:38:20 sandro: we should resolve that we'd like these changes 18:38:25 ... if we can do that in the next 10 minutes 18:38:26 sandro, perhaps ask if they could join the WG? 18:38:30 tantek, just julien and me 18:38:45 ok 18:38:51 tantek, as if who could join the WG...?? 18:39:02 sandro, Brad? 18:39:08 aaronpk: one review we got I split up into issues and we haven't talked about them yet 18:39:16 eprodrom: what are our options for incorporating those? 18:39:29 ... something we need to decide here or should we discuss as we go to PR 18:39:31 sandro: we're already at PR 18:39:34 eprodrom: REC 18:39:42 sandro: we should solve before we ask for transition to REC 18:39:48 we have to come up with responses to all the comments on the PR 18:39:54 eprodrom: so what is outstanding? 18:39:56 including the issues that aaronpk split-up from that one mega-issue 18:40:13 aaronpk: it's a bunch of really small things, should be editorial 18:40:17 ... but we do need to respond to all of them 18:40:26 tantek, feel free, but I'd be surprised if they'd do it, and I don't see why it would matter at this point 18:40:32 eprodrom: there are 17 items. I'm not sure we have time 18:40:46 we need 1) answers to those issues (either by aaronpk, or discussed here), and 2) resolutions from the WG on those answers 18:40:51 do we need a telcon next week for this? 18:42:05 LGTM 18:43:23 https://w3c.github.io/activitypub/ 18:43:34 https://github.com/w3c/activitypub/issues 18:43:54 TOPIC: AP 18:44:05 cwebber2: there are two open issues, one is a personal TODO so I'll move it out 18:44:18 ... The implementation reports for mastodon is also not an issue, we're just trying to wrap up their implementation reports 18:44:29 ... so no open issues left, just two things for the editors' sake that won't affect the spec 18:44:32 ... hoorraaayyy 18:44:32 https://activitypub.rocks/implementation-report/ 18:44:59 ... Good news, we have implementation reports page and 5 submissions, and 1 more pending 18:45:08 http://sebsauvage.net/paste/?433151b95b1eea98#lFE+VnEdmlK859Vl9VRonA0s3wtzqCRLL9jLC7xkE88= 18:45:16 ... things that don't yet have two submissions ^ 18:45:19 ... Most do 18:45:28 ... 6 client ones 18:45:35 ... 6 inbox delivery issues 18:45:39 ... and two security considerations 18:45:48 ... the bad news is it's today and we still have these 18:45:53 ... the good news is I think if I took a week we could get them 18:46:07 I can probably add some stuff to distbin where it helps get to 2 18:46:23 I need to catch up my implementation too :s 18:46:43 cwebber2: I assume we want to wait til next week to move to PR 18:46:49 sandro: we can't move forward until we have time 18:46:50 cwebber2: that's the state of things 18:46:58 ... bot for WebSub and AP we need a call next week 18:47:01 s/bot/both 18:47:15 eprodrom: working backwards, if we approve PR next week will that count? 18:47:59 sandro: technically we only have to go to PR by the end of the WG. It looks bad, but we can technically do it 18:48:15 ... to actually go to REC by the end of the WG maybe next week we can still do it 18:48:28 ... let's try for next week, but it's not the end of the world if we can't 18:48:34 cwebber2: I'm in favour of everything ready for PR next week 18:48:39 ... I'm very confident that will happen 18:49:07 eprdrom: will get mine in 18:49:13 eprodrom: will get mine in 18:49:15 evan can make activitypubcoin 18:49:16 ... Seems like we're moving along 18:49:17 if I go *really* hard I might be able to land AP in pump.io master 18:49:37 don't want to commit though because I have some papers due lol 18:49:39 eprodrom: it doesn' thave to go to master AJ, just has to exist 18:49:40 👍 18:49:43 ... Anything else about AP? 18:49:46 cwebber2: not as far as I know 18:49:48 Ooh! 18:49:48 present+ 18:49:49 I have a thing 18:49:51 eprodrom: any other business? 18:49:55 I bought activitypub.com 18:49:56 where should I redirect it? 18:50:02 Eprodrom made 1 edit to [[Socialwg/2017-11-14]] https://www.w3.org/wiki/index.php?diff=105215&oldid=105214 18:50:02 q+ 18:50:08 activitypub.rocks? 18:50:10 or spec? 18:50:12 ajordan_, it sounds like you don't need to do that for next week, but instead plan to have that for the REC announcement 18:50:20 bengo: I guess activitypub.rocks would be good! 18:50:24 cwebber2: why didn't i buy that...?? 18:50:26 I will 18:50:28 but for now... 18:50:29 eprodrom: hold onto it and sell it when AP is huge 18:50:29 sandro: noted, that's nice to know 18:50:29 bengo: thank youuu 18:50:30 activitypub.rocks 18:50:31 ack cwebber 18:50:32 will do this week 18:50:46 q? 18:50:53 ack ajordan_ 18:50:58 eprodrom: it looks like we have 10 minutes so ajordan_ are you here? 18:51:13 ajordan: was something else 18:51:16 q+ to note concern about outstanding issues on WebSub 18:51:41 ... I'm almost done weith a webmention implementation and websub shouldn't be too far off 18:51:49 ... something automatically do the right thing. 18:51:59 ... AS2 is really close to shipping in pump.io 18:52:05 ... There's one issue on the agenda 18:52:08 ... and AP isn't far behind that 18:52:31 ack tantek 18:52:31 tantek, you wanted to note concern about outstanding issues on WebSub 18:52:42 TOPIC: AOB 18:52:51 tantek: we have quite a few number as the result of comments on websub 18:53:16 ... I think we need to promptly have answeres to those that the group resolves on, either resulting in no changes or editorial changes, assuming there isn't an actual implementation problem 18:53:20 ... I feel a sense of urgency on that 18:53:42 eprodrom: we agreed earlier that aaron and julien are going to look through these, identify ones that don't require WG input and then we will next tuesday have another meeting where we'll vote on the rest of them 18:53:58 sandro: can we plan for next week being 90 mins? 18:54:00 tantek: I agree 18:54:01 +1 to a long meeting next week 18:54:27 I can't do longer than 60 minutes as usual but by all means go for it 18:54:46 tantek: Second thing.. because we're trying to wrap up our normative documents and there's a lot of activity going on, and stuff beyond in the CG 18:54:55 ... there are a lot of implementations that interoperate in ways that we ight not have fully covered 18:55:21 ... I think there's opportunity here if interest to close out the year with a few informative notes that are kind of capturing the state of interop of extensions or additons to existing specs 18:55:25 ... just want to put it out as something to think about 18:55:32 ... Thinking about treating PTD that way because it's evolving 18:56:15 scribenick: cwebber2 18:56:37 eprodrom: one thing the CG is discussing is what's missing, maybe we can talk about what can be done there and move to a note, or move that work to the CG 18:56:46 there's already a wiki page 18:56:48 tantek: I'd love to have the CG have a note about what topics are worth exploring 18:57:08 eprodrom: ok great, I want to move to ajordan_'s topic of discussion... if you want to bring it up now before 2:00? 18:57:12 ajordan_: I'll bring it up to the CG tomorrow 18:57:36 ajordan_: AS2 doc says how to transform AS1 -> AS2 but says nothing about the vocabulary 18:57:37 in particular I'd like to see us publish a number of "interop NOTEs" where we document uses of our specs with 3+ more interop impls 18:57:56 ajordan_: pump.io has to transform as1 to as2 as last step of response handler, but some of them have no equivalent in as2 18:57:58 q+ 18:58:13 q- 18:58:32 eprodrom: my first response is if we need to do that we'll do an extension vocabulary... I'm pretty suprised we have stuff in pump.io that didn't make it into as2 but sometimes that happens 18:58:46 ajordan_: I have no data on what verbs people are actually using, so I don't know if there's data out there for it 18:58:59 ajordan_: my assumpiton is a lot of verbs were dropped due to low evidence of implementation 18:59:14 eprodrom: why don't you and I talk about this, if parts of pump.io don't have a match we'll do an extension vocab 18:59:27 ajordan_: I was just consulting as1 stats 18:59:46 sandro: I encourage you put them in the as2 namespace, that's what the CG is meant to do 18:59:53 eprodrom: I don't think there's time for next week 18:59:58 sandro: I don't think there's time pressure 19:00:08 eprodrom: you had asked me about this earlier ajordan_, we'll deal with it soon 19:00:15 eprodrom: any other business? 19:00:49 eprodrom: no CG meeting tomorrow so we'll deal with this 1 on 1 ajordan_ 19:01:02 eprodrom: we have a meeting same time same place but longer next week 19:01:07 eprodrom: tantek, can you chair? 19:01:11 tantek: ACK, can chair 19:01:13 s/as1 stats/thee as1 spec/ 19:01:15 eprodrom: thanks everyone! 19:01:44 thanks all! hope the noisy hallway wasn't too bad lol 19:03:06 ha 19:03:11 OK, thanks everyone 19:03:22 trackbot, end meeting 19:03:22 Zakim, list attendees 19:03:22 As of this point the attendees have been tantek, cwebber, npdoty, annbass, hadleybeeman, snarfed, torgo, rhiaro, ajordan, eprodrom, aaronpk, bengo, sandro 19:03:30 RRSAgent, please draft minutes 19:03:30 I have made the request to generate https://www.w3.org/2017/11/14-social-minutes.html trackbot 19:03:31 RRSAgent, bye 19:03:31 I see no action items