From W3C Wiki
Jump to: navigation, search
<cwebber2> ========== MEETING LOGGING STARTS ==========
<aaronpk> scribenick: aaronpk
<aaronpk> cwebber2: for those who are new, the scribe transcribes what is being spoken into the IRC log
* dnegreira (~v0id@public.cloak) has joined
<cwebber2> present+
<dnegreira> present+
<aaronpk> ... make sure you type present+ into IRC as well
<aaronpk> present+
* eprodrom (~eprodrom@public.cloak) has joined
<eprodrom> Hey all
<cwebber2> hey eprodrom, we were just getting started
<eprodrom> My mumble app keeps crashing so I'm joining from computer
<cwebber2> present+
<cwebber2> present+ emacsen
<aaronpk> cwebber2: let's do a round of introductions
<cwebber2> scribenick: cwebber2
<cwebber2> cwebber2: let's do introductions
<cwebber2> aaronpk: I'm Aaron Parecki, I've worked on websub, micropub, indieauth
<cwebber2> aaronpk: you can follow me from mastodon
<cwebber2> scribenick: aaronpk
<trwnh> present+
<aaronpk> cwebber2: i'm cochair of this group along with aaron, i worked on activitypub in the group. currently working on something called spritely
<aaronpk> ... which is a set of demonstrations and writeups to show how we can advance the social web
<aaronpk> ... my personal website is
<aaronpk> dnegreira: i work for canonical but i'm here representing myself. i have some interests in activitypub and decentralized networks, i saw this meeting happening and was curious to see what was going on here
<aaronpk> ... to see if i can contribute in the future as well
<aaronpk> emacsen: I'm serge, i'm not representing anyone, not even myself. i am currently writing an activitypub implementation that is going to be used as a tutorial of the process of creating an activitypub implementation so i thought it might be useful to lurk and see what people are saying
<eprodrom> present+
<eprodrom> Sorry, can't connect to mumble for some reason
* cwebber2 eprodrom ok I'll read out what you say on irc
* cwebber2 and we'll scribe
<aaronpk> trwnh: my name is abdulla trwnh (sp). i am a casual observer interested in what's going on here
<aaronpk> cwebber2: first item on the agenda is the announcement about spritely and samsung stack zero grant i got
<eprodrom> I'm Evan Prodromou, I am the co-editor of Activity Streams 2.0, founder of, helped in making OStatus and ActivityPub. I work for the Wikimedia Foundation but not representing them in this meeting.
<eprodrom> !!!!!!!!!!!!!!!!
<aaronpk> cwebber2: (reads eprodrom's intro)
<aaronpk> cwebber2: so what spritely is, the fediverse can do some things but not others.
<aaronpk> ... some things it can't do is some direct and private exchanges and some richer interactions
<aaronpk> ... if a node goes down, all of its content goes with it, and there's no real way to verify the content was there
* crazychicken (~crazychicken001@public.cloak) has joined
<aaronpk> ... the point of spritely is to take a lot of ideas from surrounding communities and, in order to keep it from vaporware, releasing it as a bunc hof separate standalone demos
<aaronpk> ... i just released one demo called gollum, to show off how you can distribute messages instead of by a live HTTP link, by distributing an encrypted and content addressed way where only the recipients can see the message but it can still be passed around a p2p network.
<aaronpk> ... to show that even if a node that created the message goes offline it can still be preserved
<aaronpk> ... i should be done with the documentation this week
<aaronpk> ... i am going to try to create a decentralized MUD on top of these technologies
<eprodrom> !!!!
<aaronpk> ... that's the description of spritely. i have two years of funding, not quite enough full time so i will be doing some contracting on the side too
<trwnh> present+
<trwnh> q+
<cwebber2> ack trwnh
<aaronpk> trwnh: my question is around content addressing. i know a lot of implementations don't do that. how much do you think it's possible to do that in existing implementations without fully extending activitypub
<aaronpk> cwebber2: current impls don't do that. one of the discussions we had was whether to require the https URI scheme. one of the reasons i pushed back against it is we might want to explore some other territories where we can retrieve things over schemes other than HTTPS.
<aaronpk> ... a very simple explanation is imagine a post was delivered to you with an address that is ipfs://
<aaronpk> ... if i submitted to your inbox with just @id and the ipfs URI you could retrieve that object and it would be able to stick around
<aaronpk> ... let's imagine we took an existing implementation like mastodon, basically they'd have to be able to recognize not just https but also how to retrieve objects referred to by other protocols
<aaronpk> trwnh: that makes sense. one thing i've noticed is they don't really make a distinction between location and identity
<eprodrom> q+
<aaronpk> ... so in some ways they conflate the two, they take the location as the identity
<aaronpk> ... in some ways the location is unique in an https URI
<aaronpk> cwebber2: right this is an origin style approach. i agree the applications are being hardcoded to specific behavior around origins and that may turn out to be a problem
<aaronpk> ... what i can say for now is i think i have further demonstrations of why we want to reduce the origin as identity in the future
<cwebber2> ack eprodrom 
<eprodrom> So, I'm concerned that doing a lot to talk about next generation AP technology hurts adoption of AP right now
<eprodrom> Like, your description of this technology is about what AP can't or doesn't do
* cwebber2 eprodrom, say "done" when done so I know when to reply :)
<eprodrom> How are you going to keep the momentum going, when you're focusing on problems with the protocol?
<eprodrom> done!
<aaronpk> cwebber2: i think this is a legitimate concern
<aaronpk> ... one reason i'm not too worried at the moment is i think we hvae a lot more momentum than antipicated at the moment
<aaronpk> ... i think the last time it was captured we had 40 implementations that have mostly been trying to message between each other.
<aaronpk> ... that doesn't mean we can't accidentally screw it up
<aaronpk> ... right now with me pushing these out as demos is i'm not pushing things out as production ready that should be adopted
<aaronpk> ... i'm trying to push things out that are compatible with AP as written, but using some of the spaces that are more open to allow this
<aaronpk> ... then trying to engage discussion to what degree do we want to pick these up and run with it
<aaronpk> ... but i understand the concern that AP is doing well right now and maybe this will fragment or confuse things
<aaronpk> ... and i guess that's part of why i think the demo approach will help us be able to think about and evaluate things
<aaronpk> .
* cwebber2 and done :)
<cwebber2> eprodrom, does that answer your question to a degree of satisfaction?
<eprodrom> That's great, thank you!
<cwebber2> TOPIC: Open PRs on ActivityStreams 2.0, getting slight aged..
<eprodrom> So many
<aaronpk> cwebber2: this one is a pretty simple PR. it adds a namemap property to the list of possible properties under object and link
<aaronpk> ... this seems pretty easy for me because link already has name so i don't see why it wouldn't have namemap
<aaronpk> ... and reordering the properties seems like a simple change
<aaronpk> ... i'm very interested in whether evan feels okayh with this PR
<eprodrom> I think it sounds fine, and it's backwards-compatible
<cwebber2> eprodrom, great!  Can you merge?
<eprodrom> We'd need to put some formatting around it to indicate that it's new
<eprodrom> Yes, will do
<cwebber2> ok great!
<eprodrom> Wait
<aaronpk> cwebber2: pulling in the security namespace into the activitypub context
<eprodrom> Did we come up with a structure for doing that?
<cwebber2> waiting!
<eprodrom> Maybe "<new>" or something?
<cwebber2> eprodrom, I don't know of one...
<cwebber2> eprodrom, I wonder what other groups do
<cwebber2> eprodrom, at least there should be a change log
<cwebber2> eprodrom, I can ask best practices from some other groups?
<eprodrom> I think that makes sense. Changelog is probably the place to do it
<eprodrom> I don't think it would go in ERRATA since I don't think it's technically an error in the text.
<cwebber2> ack
<cwebber2> move onto next issue then?
<eprodrom> Y
<cwebber2> back to
<aaronpk> cwebber2: the challenge is we can add the namespace with the shortened form
<eprodrom> I'm happy to rework this so it has the ID params also
<eprodrom> We haven't had a response from puckipedia though that this satisfies their objection
<aaronpk> ... the original discussion was that we'll add that and it'll make it easy to add terms. the concern puckipedia raised last time is that doesn't capture the type information so we probably want to deal with that, otherwise it could lead to disjointness between the JSON-only and JSON-LD people
<cwebber2> eprodrom, sounds great re: adding those, and I'll ping puck 
<eprodrom> Great thank you
<eprodrom> OK, I'll have a new PR up, maybe we can complete it before next meeting, if there are no objections here
<cwebber2> eprodrom, sounds good to me
<aaronpk> cwebber2: this seems like just fixing indentation so no reason not to pull this in
<eprodrom> pulled
<aaronpk> cwebber2: there seems to be some confusion here
<aaronpk> ... i'm not quite sure what bengo is thinking is happening here. he is thinking these refer to URIs but the ID and type are just aliases for @id and @type
<aaronpk> ... so let's defer this and talk on the issue
<eprodrom> agree
<eprodrom> Those aliases weird me out anyway
<aaronpk> cwebber2: they also weird me out because it requires more work from people not using JSON-LD because it requires people look for two different things
<eprodrom> Y
<aaronpk> cwebber2: i don't see any reason why we wouldn't pull this in except if we wanted to demonstrate that if you dont supply a type then it defaults to object, but it doesn't seem like these two examples were explicitly trying to show that off
<cwebber2> eprodrom, willing to merge then?
<eprodrom> No
<eprodrom> Definitely not, I haven't looked at the examples yet
<eprodrom> I will review and merge if it makes sense
<cwebber2> ok great eprodrom 
<aaronpk> cwebber2: for those who joined new, i apologize that you joined an issue closing meeting and also one where a key member isn't on the phone. but this is an important part, making sure the issues don't stagnate.
<aaronpk> ... so that brings us to the end of the ActivityStreams PRs
<eprodrom> Whee
<aaronpk> ... so if there are issues people would like to talk about we can do those right now or we can decide to end early
<aaronpk> ... going once
<eprodrom> I need to go, thanks all
<aaronpk> ... going twice
* eprodrom has quit ("")
<aaronpk> ... alright we'll call it early. thanks everyone for coming
<aaronpk> ... see you all next time
<aaronpk> ========================= END ===========================