#cwebber2This document was published by the Social Web Working Group as an Editor's Draft. If you wish to make comments regarding this document, please send them to public-socialweb@w3.org (subscribe, archives). All comments are welcome.
#rhiaroeprodrom: For the f2f minutes it sounds like based on irc discussion that they haven't been cleaned up yet and tantek suggested that we postpone til next week
#rhiaro... One thing from that is it seems to be written assuuming the thing being reivewed is written as part of the browser, so some of the questions were challenging in that context
#rhiaro... The other micropub update is that I've been making progress on the test suite
#rhiaro... So if you do have a micropub implementation please feel free to take a look at that
#rhiaro... The other thing point out is that it stores the test results itself so creating the implementation report summary will be easier becasue allt he data will be in that website already
#rhiaroeprodrom: that's excellent, what a good idea
#rhiarotantek: the thing about the security and privacy questionnaire mostly sounding like it's been written from a browser perspective is accurate
#rhiaro... that was the driving force behind writing it up
#rhiaro... getting editors aware of security and privacy implications implementing w3c specs in the browser
#rhiaro... but we shoould be interpreting those questions liberally
#rhiaro... and think about the intent, what are they getting at in terms of vulnerabilities
#rhiaro... so even if it seems like it's browser specific, broaden the scope of that in your mind and consider what is the equivalent from the server perspective as well
#rhiaro... concerns about cookies, or implementations being stored on the browser, eg. for private browsing mode
#rhiaro... the equivalent for a server would be the server maintaning user data or stats or cookies or logs which are actually important to call out
#rhiaro... in some juristictions there are rules about that
#rhiaro... eg. europe, the ability to be forgotten by the server
#rhiaro... anything that sounds browser specific, think about what it measn for the server to have to do the equivalent
#rhiaro... I'll take a look at those answers and in places where some feedback will help with the privacy and security questionnaire I'll also push some of thsoe changes to the questions upstream and update the questionnaire itself
#rhiaro... It'll help to have examples in our specs where we're doing that
#rhiarocan anyone else hear the constant giggling from the MIT end of this call?
#rhiaro... a couple of extra things before the webmentino processing, then it hands off to regular webmention processing
#rhiaro... excited about this, and we already have implementations started
#rhiaro... three combinations of sending and receiving right now
#rhiaro... happy to be able to say that there will be an answer to how webmention works with private content
#rhiaro... once it has more implementations we'll add it to the list of extensions on the spec
#rhiaroeprodrom: So I've made a post, you've sent me a webmention and I'll show the response... is the intention that the response would not be shown on my site?
#rhiaroaaronpk: that's typically how webmentions are used, but similar to how the webmention spec doesn't actually say you have to show a comment, it leaves that out, and the goal of this spec is getting the verification to work
#rhiaro... a separate issue is what people do with that
#rhiaro... my intent is not to specify how or when peopel should show comments
#rhiaro... that will depend on why the post is private and what audience it's for
#rhiaro... I expect now that implementations would not show them as comments except maye for the owner of the site
#rhiaro... but I want to leave that open for more intelligent display of received comments
#rhiaro... the whole goal o fthis spec was to get the verification to work with authenticated content
#rhiaroeprodrom: specifying the intention early might be good to avoid mistakes
#rhiaro... if I were to send you a webmention form my site and my intention is that it would have the same access control as I have on my site
#rhiaro... if I haven't made it public to the whole world, you wouldn't make it public to the whole world either. If you did do that it would be contrary to my intention
#rhiaro... What scenario would there be where I have it private on my site but you can make it public on yours?
#rhiaroaaronpk: I would expect it to have the same access control as the source
#rhiaro... I don't want to get into ACL stuff with this, but I would epxect that anyone in the group who could see the original could see the comment on the other site as well
#rhiaroeprodrom: it seems like being more conservative in this case might be better, but it's obviously up to you how people use it
#rhiarocwebber2: There have been a number of changes to AP and when we spoke at the f2f we talked about publishing a new WD
#rhiaro... There's a new ED with a changelog of all the changes
#rhiaro... Probably the biggest change is adding the soure field stuff as discussed at the f2f, and adding that and the binary data mechanism as at risk
#rhiaro... my outstanding question regarding voting for CR next week is I did see a bunch of the i18n folks filing issues, do you expect to have responses to those by next week?
#rhiaro... I've sent out stuff for wide review and I've been starting to get feedback, and going to make a mediagoblin blog post to day and asking our donors for additional review
#rhiaro... we've already got a good amount, not all on the wiki page yet
#rhiaro... will be working on that today, and collapsing tha tpage into the CR page on the wiki
#rhiaro... I have been getting feedback, the majority was people concerned about the cryptographic integrity of the document
#rhiaro... so this might be partly because of the people who are paying most attention to AP are in the federated social web space and are concerned about decentralisation from that kind of perspective
#rhiaro... there were a couple of peopel from diaspora who had weighed in before, that were about how diaspora has done sigantures and asking that we do the same
#rhiaro... I don't think signatures are going to make it in, but I've left text on how that might be done
#rhiaro... Cleared it up so the method of verification is left open
#rhiaro... That was surprising so far, but they seem very interested in that
#rhiaro... And some other feedback I'll be getting to over the week
#tantekq+ to ask if signatures could be done as an extension? and does this relate to private webmentions at all? should it?
#rhiarotantek: I tried to follow some of those conversatiosn about signatures, I think you're doing the right hting Chris, but is that something we could write up or add later as an extension?
#rhiaro... That if servers decided to adopt that extension they'd have some way of discovering that they are talking to someone who supports signatures?
#rhiaro... And potentially satisfy the commenter concerns in that way?
#rhiaro... Part 2 of this question is from hearing aaron's discussion about private webmention, is there / shoulld there be relation?
#rhiaro... We've all elft this space open in our specs
#rhiaro... to leave verification somewhat ambiguous with some proposed methods for doing so
#rhiaro... the most basic being checking the source content. But having left it open we can define that as an extension and make sure it's compatible going into the future
#rhiaro... So yes I'm interested in collaborating with aaron and anyone who is interested
#rhiaro... and whether or not it applies to the private messaging stuff
#annbassq+ to say something about next steps (when this topic is done)
#rhiaro... it definitely applies there, and as a means of verification, another place where it was brought up is that some of you might remmeber that amy and I put a mechanism for forwarding messages into the AP spec so you wouldn't have the problem that pumpio currently has
#rhiaro... where if you send a message to someone' sfollowers and someone replies and people up the chain don't see it
#rhiaro... it's an interesting point, they really rely on that
#rhiaro... there are multiple reasons to want that, but we don't need to solve that in the time of this group, we can work on it going forward
#rhiarotantek: we are talking about the winding down of the wg, but after the f2f we did agree to start a CG and this is a perfect candidate to be discussed
#rhiaro... and worked on in the context of that CG
#rhiaro... we figured out a bunch of things, and we're taking them to CR, and anything else is a bit more experimental and that's the perfect use of a CG is to take this ideas and start to incubate them there
#rhiaro... without a particular timeline or deadline
#rhiaroannbass: We agreed at the f2f to start a CG to continue the follow on
#julienMaybe PubSubHubbub? (not that I have nything special to say though...)
#rhiaro... I've been chatting with akuckartz who is cochair of the federated socweb CG (with evan) and andreas questions if we should close that or repurpose that
#rhiarotantek: I think as far as we discussed at thef2f, part of the intent of creating the social web incuabor group was to... we discussed closing down a number of CGs and we'd include their work as part of the new gropu... for example the PuSH CG ... so we can declare that CG succeeded in incubating... part of the point was to provide a continuity of like here is a group that's been active (the WG) and the future of that is to incubate thingse beyond what we've
#rhiaro... and I feel like we've built 'brand recognition' with the good work the WG has done
#rhiaro... and to keep that and indicate that there's continuity here
#Zakimsees cwebber, tantek, annbass on the speaker queue
#rhiaro... so unless andreas has any objectsion, I think that's a good reason to start the new CG and also it'll be a good announcement that we're starting a new group with the following scope
#Zakimsees cwebber, tantek, annbass, akuckartz on the speaker queue
#rhiaro... what we've done before, plus the other CGs
#rhiaro... I think it woulld be better to bring those under one umbrella, make a new brand we can announce and get people excited again, rather tahn attempting reuse of an existing one
#Zakimsees cwebber, tantek, annbass on the speaker queue
#rhiaroakuckartz: I think we should discuss this by mail
#rhiaro... I think the fact that there are more than 120 members of the fedsocweb CG
#rhiaro... Almost all of them were becoming members over a long period of time because they're itnerested in decentralised social web, and I think this should be a factor in deciding the future of how to build a new CG
#tanteknote: everyone in all past CGs should absolutely be invited to join the new SWICG
#rhiaro... Many of the people who are conerned about the social web, I don't think .. if the active members from the WG join then the CG will become active again
AdamB joined the channel
#rhiaro... Regarding the name, I don't care very much about that, federated or not, but the aim is to have a decentralised social web and that should be reflected, even if it's just social
#rhiaro... I think everybody knows the CG will not have the target of creating silos
#rhiaroannbass: seems like we're talking about similar things and we want to capture the members of this group, and the closing IG, and the existing CGS
#rhiaro... we all share an interest in the existing standards, I agree with tantek's point that we want to capitalise on the identity we've built through this group
#ZakimAs of this point the attendees have been rhiaro, on, irc, but, not, call, (spotty, wifi), sandro, aaronpk, tantek, annbass, ben_thatmustbeme, cwebber, csarven, julien, AdamB,