#rhiaroHey folks, we're voting on a new AP CR today to ship the last month's editorial changes. There's a colour coded diff courtesy of sandro here: https://www.w3.org/People/Sandro/diff/activitypub/20170907-20171030.html If you have time to familiarise yourself with the changes before today's meeting, that would be awesome.
#csarvensandro: Instead of <span class="delete"> and <span class="insert">, why not <ins>/<del> (with optional @datetime)? Is that some ReSpec thing out of the box?
#puckipediaI know AS2 vocab does Like and Dislike :P
#jaywinkI'm kind of scared about starting to impelement AP. I honestly don't understand most of what is discussed here lol
#jaywinkshould have time hopefully dec-jan to start tho. hopefully without having to read about json-ld :P
#puckipediayou should be able to get by without :P
#puckipediaI would still advice you to run the JSON-LD compaction algorithm on any incoming messages, so you know that 'object' means 'object'
#rhiaropuckipedia: I don't understand your questiona bout the context
#puckipediarhiaro: likes/shares are not defined in the AS2 context, so they get expanded into "_:likes": [{"@value": "https://www.w3.org/ns/activitystreams"}]
#csarvenrhiaro I'll try to be present for the meeting, but in case I can't make it, please accept my preemptive +1 on advancing the AP spec (with reasonable non-normative changes that the WG agrees with - aka, going with the status quo here)
#puckipediarhiaro: okay, if I extract the values from all <code> tags in the editor draft, and remove all those in the @context, I get... likes and shares
#rhiarocwebber2, it's admirable that you check irc before you're even awake properly. It's okay, we can wait until you've had breakfast :)
#cwebber2rhiaro: oh, likes and shares don't need to go there but "shared" should have, but isn't, in that section
#cwebber2"liked" and "shared" are what the actor liked/shared as opposed to "likes"/"shares" which are a collection of likes and shares where the object was the subject
#Loqi[jaywink] #203 Linked Data Signatures + public key URI
#rhiaro... One is not really affecting things in the spec
#rhiaro... Just so everyone knows, this has already been handled, I left it open because we had agreed I'd make specific changes to the wiki page in the CG, so I left it open to remind myself
#rhiaro... amy and I spent a substantial amount of time. We talked about it a few weeks ago
#rhiaro... We resolved that we would clarify that there's not specific mapping of one user to one actor in the spec and wouldn't do anything further
#rhiaro... I thougtht hat was going to be it, but the commenter was not satisfied
#rhiaro... there's been much further conversation about needing to explain very carefully this concept of 'account' and we spent a lot of itme trying to figure out what they meant
#rhiaro... even within the last couple of changes amy and I got in a clear exlpanation that's non-normative that explains how accounts are actors, and can be humans or bots etc. I hoep that satisfies them but I'm not sure
#rhiaro... This has gone on for only 50 messages and in circles for a while
#rhiaro... We did have a resolution that was incorporated
#rhiaro... I'd like to get some group.. if you haven't read it.. well... I think we've done the very best we can to try to capture everything this person has said without adding vocab. Even the commentor agrees on not adding vocab
#rhiaro... I'd like the group to approve we close this even if the commentor specifies they're not satisfied, because I don't thinkw e can do better at this point
#rhiarotantek: the first question I would ask (I haven't read the issue since the additional messages) is there any way to distill what if any new information was added to the issue since we did a group resolution?
#rhiarotantek: I understand the points before, but I'm trying to understand if there's new information subsequently
#rhiarocwebber2: it switched from talking about users to talkinga bout accounts
#rhiaro... there was a lot more clarificationa bout why they thought this was really important
#rhiaro... I feel like a lot of it went to discusisng about how accounts in the system are really important to have the domain modelling of, and they also feel that this in some way not specifying is missing
#rhiarorhiaro: Agree with chris. A lot of the comments are rephrasing the same information for clarity. A lot belongs in the CG, and the commentor agreed on some of that too
#rhiarotantek: the reason I ask a question like that is at some point if we're not getting new information we can resolve it in the group and we can note that if it appears the commentor is not satisfied
#rhiaro... it should be okay if we've done our due diligence
#rhiaro... that being said, my understanding is we don't have anything about account management in any of our specs as far as I know, si that correct?
#rhiaro... by account management I mean creating an account, setting your background image, setting up email, etc. We don't model any of that do we?
#rhiarocwebber2: we don't, aside from the most basic detail like your name
#rhiarotantek: we have name and image, but that's it. That's abou tthe actor not about the account, I would argue
#rhiaro... the way that I would try to resolve this in a productive fashion is saying account management is important and we don't have it in the current spec, it would be a great extension
#rhiaro... that might be what satisfies the commentor
#rhiarorhiaro: we already said in the spec that this stuff is important and should be discussed as an extension in the CG
#rhiarocwebber2: we could resolve that we've done what we can with this and move oveflow to the CG and ask the commentor if they're satisfied and mark it one way or the other
#tantekjust as additional info for that issue, note the Account Management issues (partially) documented for Twitter that are likely worth modeling https://indieweb.org/Twitter#Features
#rhiarocwebber2: So the signatures one is not one that touches the spec, and 260, 266 is the only change we'd make since the diff in terms of issuing a new CR
#rhiaro... I'd like to propose we publish a new CR with changes from 266
#cwebber2PROPOSED: Issue new CR of ActivityPub incorporating change proposed in issue #266
#puckipediacwebber2: I mean, I could define Kroeg as 'serverless', it has no concept of servers :P
#cwebber2"serverless" here I think refers to the term used to deploy an AWS "serverless" application... which of course has servers, you're just abstracted away from them somewhat
#puckipediahow about ... to filter a collection that contains type Create/Announce: {"filter:contains": { "type": ["Create", "Announce"] }, "filter:excludes": { "actor": "https://example.com/user" } }}
#cwebber2it def looks like a cool api direction if possible
#puckipediaI would probably put these on the OrderedCollection together with a "filter:basedOn": "otherId", then filter those filter: results from the returned object
#puckipediaanyways, I already have arbitrary filtered collections, I do audience checks in the DB
#puckipediabut yeah, it'll be somewhat unfeasible for some
#cwebber2when's the next SocialCG meeting? we're planning a face-to-face meeting at TPAC on Monday but not many people from here will be there for it probably
#cwebber2given TPAC it may be hard to schedule the usual wednesday call