17:01:45 RRSAgent has joined #social 17:01:45 logging to http://www.w3.org/2017/05/30-social-irc 17:01:47 RRSAgent, make logs public 17:01:47 Zakim has joined #social 17:01:49 Zakim, this will be SOCL 17:01:49 ok, trackbot 17:01:50 Meeting: Social Web Working Group Teleconference 17:01:50 Date: 30 May 2017 17:01:56 present+ 17:02:16 present+ 17:02:19 present+ 17:02:30 cwebber2: are you calling in? 17:02:36 eprodrom: yes 17:02:40 Awesome 17:02:56 scribe? 17:03:13 scribe: sandro 17:03:38 scribenick: sandro 17:03:52 present+ 17:04:18 present+ 17:04:31 present+ 17:05:20 https://www.w3.org/wiki/Socialwg/2017-05-30 17:05:41 eprodrom: This is our new meeting time 17:05:46 TOPIC: Approval of previous minutes 17:05:50 tantek has joined #social 17:06:04 PROPOSED: approve https://www.w3.org/wiki/Socialwg/2017-05-23-minutes as minutes for 23 May 2017 meeting 17:06:41 +1 17:06:42 +1 17:06:45 good morning 17:06:46 present+ 17:06:54 +1 17:07:02 +1 17:07:04 +1 from what I recall reading it later that day 17:07:08 +1 17:07:12 +1 17:07:23 RESOLVED: approve https://www.w3.org/wiki/Socialwg/2017-05-23-minutes as minutes for 23 May 2017 meeting 17:08:29 sandro: Please keep trying to find AC Reps to vote 17:08:47 https://www.w3.org/2002/09/wbs/33280/socialweb-exnt/ 17:08:56 (access controlled link) 17:09:11 until June 16 17:09:31 https://www.w3.org/Member/ACList 17:10:17 I think Evan can read this, but maybe not. 17:10:21 tantek: curious 17:10:38 eprodrom_ has joined #social 17:11:22 can you see this? https://www.w3.org/2000/09/dbwg/details?group=33280 17:11:22 https://www.w3.org/Consortium/Member/List 17:11:39 eprodrom: okay, we'll try to figure out who we know 17:12:03 sandro: to remind them to give feedback 17:12:09 tantek: not authorized for me 17:12:46 tantek: we'd love feedback as part of those conversations as well 17:12:55 topic: Next Telcon 17:12:58 June 6 17:13:34 topic: ActivityPub 17:13:39 eprodrom: test suite? 17:14:09 cwebber2: life took over, family emergency, etc, still not ready 17:14:29 ... one issue for discussion 17:14:51 eprodrom_ vs eprodrom 17:15:02 https://github.com/w3c/activitypub/issues/225 17:15:03 [brianolson] #225 Needs provisions for encrypting content for privacy 17:15:16 cwebber2: someone's asking for end-to-end encryption 17:15:18 Fixed! 17:15:32 cwebber2: Can we say it's worth exploring, but not feasible in the spec at this time 17:15:35 +1 17:15:40 +1 17:16:14 eprodrom: If you literally are going to encrypt activities as posted to your outbox, so they're only readable to recipients who know it, the server couldn't do the routing 17:16:20 https://github.com/w3c/activitypub/issues/225#issuecomment-304938193 17:16:20 [cwebber] So there are two ways to encrypt things. You can encrypt things between servers, which is done via SSL/TLS. You could also give each user a public/private keypair on the server, but at that point you're nearly in "as good/bad" of a situation as HTT... 17:16:37 cwebber2: I think I captured that in the issue. 17:17:03 .. If you just want an encrypted wrapper, we could maybe support that in extension, but s2s side effects wouldn't work 17:17:21 .. server can't, eg, increase likes, add someone to list, etc 17:17:37 .. encrypted wrapper would have lots of side effects. Just delivery of an object. 17:17:57 eprodrom: it would be possible to do encrypted-content property 17:18:38 .. or to have an encrypted-note type, that has much of the same properties as node, but we expected 'content' value to be opaque. That would cover much of what people expect from end-to-end. 17:19:17 cwebber2: or encrypted-payload field, with json object. 17:19:44 .. like email, as far as envelope being visible 17:20:06 .. still, not something we're going to do in this WG 17:20:13 runyourownserver++ :) 17:20:14 runyourownserver has 1 karma 17:20:14 eprodrom: the usual answer is 'run your own server' 17:20:34 eprodrom: I agree, closing that 17:21:14 sandro: invite commenter to propose extension in CG 17:21:15 cwebber2: Sure 17:21:33 cwebber2: I will have a better update next week 17:21:54 ajordan: Did we ever cover Direct-Message issue? 17:22:02 issue number? 17:22:07 https://github.com/w3c/activitypub/issues/196 17:22:07 [annando] #196 How to differentiate between posts and private (direct) messages? 17:22:39 ajordan:We talked about this, but I can't remember what we said 17:22:46 ajordan, you can bring up any substantive issue in github on our CRs, the agenda items for those specs are inclusive of that "open issues" 17:23:23 cwebber2: evan made the case we covered this with to,bto,cc,bcc 17:23:42 ajordan: Let's remember our state on this for next week 17:24:03 eprodrom: it was two weeks ago 17:24:15 ajordan: let's move on for today 17:24:24 topic: websub 17:24:45 https://github.com/w3c/websub/issues/106#issuecomment-304121737 17:24:46 [aaronpk] Here is some proposed text to add this to the spec. 17:24:46 Before: 17:24:46 > The successful response from the subscriber's callback URL MUST be an HTTP [[!RFC7231]] success (2xx) code. The hub MUST consider all other subscriber response codes as failures; tha... 17:24:47 grep of minutes list shows #196 mentioned on 4/25, 5/2 and 5/9 cwebber2 17:24:49 aaronpk: Last week we agreed to incorporate this HTTP 410 issue 17:25:08 aaronpk: Julian wanted MAY instead of SHOULD. 17:25:24 aaronpk: New WG 17:25:28 tantek: yeah 17:25:59 sandro: contingent on clarification 17:26:14 sandro: although with MAY it's hard to imagine it being a problem 17:26:57 tantek: I agree, the MAY makes it even less likely to raise concerns. It's pointing direction for implementation. Is it possible to test this? 17:27:24 aaronpk: I do plan on test, waiting for text to be in 17:27:45 tantek: if it's widely implemented, than in a 1.1 we could upgrade it to a SHOULD 17:28:27 aaronpk: In that case I'll go ahead with a new CR 17:29:00 tantek: I think this would be normal WG post-REC maintenance 17:30:34 sandro: I'll still check with Ralph, don't want to get this wrong 17:30:49 aaronpk: I checked on github's impl 17:30:58 .. turns out they don't implement discovery 17:31:14 .. their topic URLs don't return anything when you touch them 17:31:23 .. and their subscription request requires Access-Token 17:31:35 .. so it's not really PubSubHubbub 17:31:39 .. they do send fat pings 17:31:49 .. but it's undefined if they match URL, since URLs don't work 17:31:55 .. not a lot of good news 17:32:14 .. I'm asking someone at github to look into it 17:32:24 .. but not optimistic because of their general need for authentication 17:32:36 topic: Post Type Discovery 17:32:49 tantek: Nothing new 17:33:01 .. hopefully soon 17:33:24 topic: Any other documents? 17:33:34 Zakim: who is on the call? 17:33:37 eprodrom: We approved pub of social web protocols 17:33:49 I have been working on updates to JF2 17:33:55 but that will be a bit before done 17:34:02 sandro: rhiaro is at conf this week 17:34:17 ajordan, comma not colon 17:34:34 topic: Social Incubator CG 17:34:40 cwebber2: Tomorrow! Show Up! 17:34:47 sandro: :/ 17:35:03 eprodrom: Nice. Short meetings are good. 17:35:11 +1 to that 17:35:30 https://www.w3.org/wiki/SocialCG/2017-05-31 17:35:39 sandro: help add to CG agenda and get the word out 17:35:39 q+ 17:35:50 ack ajordan 17:35:58 hehe 17:36:00 ack ajordan 17:36:21 cwebber2: might want to announce on the CG page 17:36:25 eprodrom, adjourned, see you tomorrow and next week! 17:36:28 ajordan, yes probably 17:36:35 trackbot, end meeting 17:36:35 Zakim, list attendees 17:36:35 As of this point the attendees have been eprodrom, sandro, ajordan, cwebber, ben_thatmustbeme, aaronpk, tantek 17:36:35 sandro++ 17:36:35 sandro has 39 karma in this channel (46 overall) 17:36:38 sandro++ for minuting 17:36:38 sandro has 40 karma in this channel (47 overall) 17:36:39 eprodrom++ 17:36:39 eprodrom has 46 karma in this channel (47 overall) 17:36:39 eprodrom++ 17:36:39 slow down! 17:36:41 sandro++ 17:36:43 RRSAgent, please draft minutes 17:36:43 I have made the request to generate http://www.w3.org/2017/05/30-social-minutes.html trackbot 17:36:44 RRSAgent, bye 17:36:44 I see no action items