#social 2015-05-05

2015-05-05 UTC
rhiaro_, rhiaro__, akuckartz and Arnaud joined the channel
#
sandro
trackbot, start meeting
#
trackbot
is preparing a teleconference.
RRSAgent joined the channel
#
trackbot
RRSAgent, make logs public
#
RRSAgent
I have made the request, trackbot
Zakim joined the channel
#
trackbot
Zakim, this will be SOCL
#
Zakim
I do not see a conference matching that name scheduled within the next hour, trackbot
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 05 May 2015
#
sandro
zakim, room for 10 for 600 minutes?
#
Zakim
sorry, sandro; could not schedule an adhoc conference; passcode overlap; if you do not have a fixed code you may try again
tantek joined the channel
#
sandro
zakim, move 26631 here
#
Zakim
I don't understand 'move 26631 here', sandro
#
sandro
zakim, move conference 26631 here
#
Zakim
I don't understand 'move conference 26631 here', sandro
#
sandro
zakim, help
#
Zakim
Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help.
#
Zakim
Some of the commands I know are:
#
Zakim
xxx is yyy - establish yyy as the name of unknown party xxx
#
Zakim
if yyy is 'me' or 'I', your nick is substituted
#
Zakim
xxx may be yyy - establish yyy as possibly the name of unknown party xxx
#
Zakim
I am xxx - establish your nick as the name of unknown party xxx
#
Zakim
xxx holds yyy [, zzz ...] - establish xxx as a group name and yyy, etc. as participants within that group
#
Zakim
xxx also holds yyy - add yyy to the list of participants in group xxx
#
Zakim
who's here? - lists the participants on the phone
#
Zakim
who's muted? - lists the participants who are muted
#
Zakim
mute xxx - mutes party xxx (like pressing 61#)
#
Zakim
unmute xxx - reverses the effect of "mute" and of 61#
#
Zakim
is xxx here? - reports whether a party named like xxx is present
#
Zakim
list conferences - reports the active conferences
#
Zakim
this is xxx - associates this channel with conference xxx
#
Zakim
excuse us - disconnects from the irc channel
#
Zakim
I last learned something new on $Date: 2013-03-03 19:18:47 $
parklize joined the channel
#
sandro
zakim, move conf1 to here
#
Zakim
sandro, I see Team_(socwg)07:29Z in the schedule but not yet started. Perhaps you mean "this will be conf1".
#
sandro
zakim, this will be conf1
#
Zakim
ok, sandro; I see Team_(socwg)07:29Z scheduled to start 2 minutes ago
#
sandro
zakim, this will be Team_(socwg)
#
Zakim
ok, sandro; I see Team_(socwg)07:29Z scheduled to start 3 minutes ago
#
cwebber2
morning, ish
#
Arnaud
trackbot, start meeting
#
trackbot
is preparing a teleconference.
#
trackbot
RRSAgent, make logs public
#
RRSAgent
I have made the request, trackbot
#
trackbot
Zakim, this will be SOCL
#
Zakim
I do not see a conference matching that name scheduled within the next hour, trackbot
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 05 May 2015
#
cwebber2
the "ish" is that it's 2:30am here, I'm barely awake
#
sandro
zakim, this will be Team_(socwg)
#
Zakim
ok, sandro; I see Team_(socwg)07:29Z scheduled to start 3 minutes ago
claudio joined the channel
#
Arnaud
zakim, who's on the phone?
#
Zakim
Team_(socwg)07:29Z has not yet started, Arnaud
#
Zakim
On IRC I see claudio, parklize, tantek, Zakim, RRSAgent, Arnaud, akuckartz, KevinMarks, shepazu, cwebber2, kaepora, deiu, elf-pavlik, Loqi, wilkie, melvster1, oshepherd, rhiaro,
#
Zakim
... aaronpk, kylewm, Tsyesika, mattl, ElijahLynn, JakeHart, bret, bigbluehat, ben_thatmustbeme, dwhly, trackbot, sandro, wseltzer
#
sandro
cwebber2, are you calling into Zakim? The conference code is 26631 today
bblfish joined the channel
#
Arnaud
cwebber, are you calling in?
#
tantek
good morning #social web WG! again, lurking today, in another meeting all day.
#
sandro
When the INRIA conference system answers the phone (in French) can you enter the conference code 23695487# ?
#
sandro
Zakim, call INRIA-bridge
#
Zakim
ok, sandro; the call is being made
#
Zakim
Team_(socwg)07:29Z has now started
#
Zakim
+INRIA
#
sandro
zakim, drop inria
#
Zakim
INRIA is being disconnected
#
Zakim
Team_(socwg)07:29Z has ended
#
Zakim
Attendees were INRIA
#
Zakim
Team_(socwg)07:29Z has now started
#
sandro
Zakim, call INRIA-bridge
#
Zakim
ok, sandro; the call is being made
#
Zakim
+[IPcaller]
#
Zakim
+INRIA
#
Zakim
-[IPcaller]
#
Arnaud
bridges are connected
#
aaronpk
scribenick: aaronpk
#
cwebber2
Arnaud: I am
#
cwebber2
give me a minute
#
aaronpk
Arnaud: plan for today is to go through two more APIs, activitypump and SoLiD
rhiaro_ joined the channel
#
cwebber2
hey Arnaud it says
#
cwebber2
"the conference is restricted at this time"
#
aaronpk
Tsyesika: user posts a note
#
aaronpk
posting a note to the outbox, you submit a Post activity with an object of a Note, sent to "followers"
melvser1 joined the channel
#
aaronpk
the server returns the entire activity with the note back, and it's added the author and publish date, and the ID of the activity and the object
#
aaronpk
Sandro: do you need the @type collection on the "to" object? Yes
#
cwebber2
ok, I can't dial in since the conference is restricted, so I'll just follow via text
#
sandro
cwebber2, what conference code did you use?
#
cwebber2
sandro: SOCL
#
aaronpk
Tsyesika: the API requires you to specify the type, we could see about removing the requirement
#
sandro
ah, sorry, but it's 26631 today
#
Zakim
+??P0
#
aaronpk
...to "to" is specifying the audience, not adding something to the collection, different from it being the target
#
cwebber2
Zakim, ??P0 is me
#
Zakim
+cwebber2; got it
#
aaronpk
...the server would lok at everyone you sent it to (the followers), and send it out to the inbox of everyone in the followers collection
#
sandro
cwebber2, can you hear Jessica?
#
cwebber2
yeah, it's a bit faint but I can follow
AnnB joined the channel
#
sandro
yeah, she's mostly facing the screen, which is facing away from you
#
aaronpk
... there are two URLs involved here, the user's outbox "feed" and the "followers"
#
cwebber2
sandro: no worries, it's sufficient
#
aaronpk
Q: is this like access control?
akuckartz_ joined the channel
#
aaronpk
Tsyesika: kind of, it's audience targeting but if the account is private then it acts as access control
#
aaronpk
Arnaud: can you tell us about the backend of distributing to the followers?
#
aaronpk
Tsyesika: it iterates through all the followers asynchronously and sends the full activity object to the inbox of everyone
#
aaronpk
Arnaud: so there are two resources that got created, one for the note itself, and one for the acitvity
#
aaronpk
Tsyesika: for updating a note, you specify the same note object but there's a new activity ID
#
cwebber2
it's like email and collections are like email lists
#
aaronpk
sandro: if the following collection changes tomorrow, who has access to the previous notes?
#
aaronpk
Tsyesika: if I were to write the spec now, it would be available to the people who were in the collection at the time it was posted
#
aaronpk
sandro: so I could update the note and send the update to a different set of people?
#
aaronpk
Tsyesika: i don't think this is specified either
#
aaronpk
elf-pavlik: i'll make an issue for clarifying the ACL
#
aaronpk
Tsyesika: deletion, creating a deletion activity specifying the ID of the note
the_frey joined the channel
#
aaronpk
... a shell of the note remains at the original URL, which includes the deleted date. i'm going to open an issue to remove the publish/update dates from the deleted note
shepazu_ joined the channel
#
aaronpk
... the delete activity becomes activity 3
#
aaronpk
next story: following a person
#
bblfish
what's the URL
#
sandro
(To be more specific, the ACL issue is: how do the acls of a Note related to the recipient lists of the various activities which create/update that note)
#
cwebber2
fyi it's totally cutting in and out so if someone addresss me I won't hear it
#
wseltzer
cwebber2 should we try moving the phone?
#
cwebber2
wseltzer: might help
#
cwebber2
we're entering into a user story I wrote up last night without being able to coordinate with Tsyesika
#
cwebber2
and some of this behavior is different than the pump api
#
wseltzer
cwebber2, any better?
#
cwebber2
a bit I think
#
aaronpk
Arnaud: the first step was the act of following, the second was the distribution of adding an activity?
#
aaronpk
Tsyesika: Delano posts a "follow" activity to his server with an object of Beth
#
cwebber2
explicit side-effect in the spec
#
aaronpk
elf-pavlik: what side effects does this have? it's a delivery mechanism and also changing the collection
#
aaronpk
Tsyesika: it's an explicit effect
#
aaronpk
... this is acitivtypump specific
claudio joined the channel
#
Zakim
sees cwebber on the speaker queue
#
aaronpk
... the server needs to know the "inbox" endpoint for beth, so it can go discover the endpoints
#
Arnaud
ack cwebber
#
Zakim
sees no one on the speaker queue
#
aaronpk
cwebber2: btw some of this has changed from the pump API to activitypump at the request of the group, including the jsonld embedded in the HTML
#
aaronpk
... one of the options we discussde was whether we should embed jsonld into the html, but there are other options, we could embed microformats or rdfa into the document
#
aaronpk
... so we have not actually made decisions on this
#
aaronpk
... were previously using webfinger but the group decided not tu ose webfinger
#
aaronpk
Tsyesika: so this is still an open issue for doing the URL discovery
#
aaronpk
... so now you can make a post to their inbox
AnnB joined the channel
#
aaronpk
aaronpk: can you clarify the "public" id in the "to"
#
aaronpk
Tsyesika: this is a special URL that means the public collection
#
cwebber2
well, and
#
cwebber2
the target stuff is still in the editor's draft has to: cc: bcc:
#
cwebber2
it hasn't dropped that yet
#
cwebber2
for activitystreams 2
#
cwebber2
but I think we're willing to move with the group
#
cwebber2
it doesn't seem like it's gelled yet, even in the document
#
aaronpk
Tsyesika: pump.io uses primary and secondary audiences extensively, so i'm skeptical of getting rid of them
#
aaronpk
elf-pavlik: what's the difference with using "to" and specifying a secondary audience, vs just using target
#
aaronpk
Tsyesika: having a "to" of the public URL is essentially saying it's not to anyone, it's to everyone
#
cwebber2
elf-pavlik: it's pubsubhubbub style
#
cwebber2
it's not polling
#
cwebber2
it's push
#
cwebber2
you *can* pull
#
aaronpk
elf-pavlik: so why use the "to: inbox" why not just "target: my outbox"
#
aaronpk
Tsyesika: mainly because this is how all audience targeting works to avoid a special case for this
#
cwebber2
elf-pavlik, public collections are a "special collection", there could be a different convention to have the stream
#
cwebber2
but the convention is currently deliver to collections or users
#
aaronpk
bblfish: so the problem is in this case, the "id" is not derefencable so the code needs to special-case this all the time
#
aaronpk
Tsyesika: that's true
#
aaronpk
...okay now this is delano looking at his inbox, he sees the post made by beth of the image, and presumably more activities below
#
aaronpk
... unfollowing someone, they make another acitivty to their outbox, delano unfollowing beth
#
aaronpk
.. the object is the person, send to beth and cc the public URL
#
cwebber2
wseltzer: btw the call quality is much better now
#
aaronpk
Tsyesika: there is a suggestion for using the "undo" activity with the object of the activity you want to undo
#
aaronpk
... so in this case the user is removed from the followers collection
#
aaronpk
bblfish: in some ways there's a similarity between micropub, which is that this is also not restful
#
aaronpk
Tsyesika: we do specify an alternative way of doing this, you do a PUT to any object
#
aaronpk
... and has a side effect of generating the update activity
#
cwebber2
we had PUT and DELETE and removed it on feedback
timbl joined the channel
#
aaronpk
... in some reasearch evan did, most people were posting activities
#
aaronpk
... but we do make allowances for that in the specification
#
cwebber2
evan looking into it was also partly prompted by tantek requesting possibly dropping it down to GET/POST only
#
wseltzer
cwebber2, good to hear!
#
aaronpk
... 1. finding more content from an author
eprodrom joined the channel
#
cwebber2
activitypump is the socialwg iteration of the pump api ;)
#
cwebber2
hey eprodrom !
#
eprodrom
indeed
#
aaronpk
... looking at the inbox. this is where activitypump diverges from pump.io
#
aaronpk
... pumpio has a specific comment type, so when you're posting a reply you're posting a comment, which is like a note
hhalpin joined the channel
#
aaronpk
... but in activitypump we don't have a comment type, you just post any object, and add an inReplyTo
#
eprodrom
What
#
eprodrom
That's not true
#
tantek
interesting about no explicit comment type!
#
Arnaud
zakim, who's on the phone?
#
Zakim
On the phone I see INRIA, cwebber2
#
eprodrom
Arnaud: I thought we were starting at 9:30 this morning again
#
rhiaro_
eprodrom: can you clarify what's not true?
#
hhalpin
evanpro - the Zakim code is: 26631
#
Arnaud
we did
#
eprodrom
pump.io API doesn't require a specific type
#
eprodrom
hhalpin: thanks
#
eprodrom
But OK
bblfish joined the channel
#
Arnaud
9:30 was 1h ago
#
eprodrom
Ah great
#
eprodrom
My bad
#
aaronpk
Tsyesika: I apologize to evan if I made a mistake
#
hhalpin
ok, regardless ActivityPump does have quite a few differences - evanpro, you may want to list them.
#
hhalpin
In particular, re dependencies on the rest of the "Ostatus" stack
#
eprodrom
Really?
#
AnnB
Tseysika invites eprodrom to clarify
#
eprodrom
Which, about the comment type?
#
hhalpin
and clarify at some point what you think is crucial to keep and what dependencies you could live without. For example, didn't Google stop producing webfinger?
#
aaronpk
Tsyesika: you can if you wish to a GET on the user's outbox to see the activities they've done which is what's in this example
#
cwebber2
eprodrom: what are you objecting to?
#
cwebber2
that's where you should comment :)
#
eprodrom
Will do
#
AnnB
dang time zones!
#
aaronpk
... those are the user stories we got done last night, hopefully that gives you an idea
#
cwebber2
Tsyesika++
#
Loqi
Tsyesika has 9 karma
#
aaronpk
Arnaud: are there any more questions?
#
aaronpk
... it seems that access control is a big difference
#
Zakim
+eprodrom
#
elf-pavlik
Arnaud: looks like IndieWeb doesn't have ACL - looking at ActivityPump approach
#
elf-pavlik
aaronpk: we experiment with with it and it may work similar to ActivityPump
#
elf-pavlik
aaronpk: sending private not has some experiments but we still work on it
#
elf-pavlik
elf-pavlik: public content seems focus so far in IndieWe
#
cwebber2
elf-pavlik: it's not using pubsubhubbub
#
cwebber2
it's push-style
hhalpin_ joined the channel
#
hhalpin_
q+
#
Zakim
sees hhalpin_ on the speaker queue
#
aaronpk
cwebber2: pubsubhubbub is push-style, not sure what you mean
#
aaronpk
(that was me saying that, not cwebber2 oops)
#
cwebber2
aaronpk, right, I meant that it's push-style *like* pubsubhubbub, but it isn't *using* pubsubhubbib, sorry
#
cwebber2
aaronpk, that was the clarification I meant
#
aaronpk
(cool thanks)
#
aaronpk
bblfish: can you describe posting a photo
#
aaronpk
Tsyesika: you submit the file with the image content type, you get back the image ID
#
aaronpk
...then you can submit an activity with the photo object
#
eprodrom
q+
#
Zakim
sees hhalpin_, eprodrom on the speaker queue
#
aaronpk
...i'm not thrilled about having several requests, I like how indieweb did it where you submit just one request with all the metadata you want
#
aaronpk
... we don't have any provisions right now for specifying a title when uploading the photo right now, so you have to do it in multiple requests
#
Zakim
sees hhalpin_, eprodrom on the speaker queue
#
Arnaud
ack hhalpin_
#
Zakim
sees eprodrom on the speaker queue
#
elf-pavlik
q+ re: sidefects
#
Zakim
sees eprodrom, elf-pavlik on the speaker queue
#
Zakim
sees eprodrom, elf-pavlik on the speaker queue
#
aaronpk
hhalpin_: quick note on the ACL point, I thought we had some stories about access control, but maybe not ones that we all agreed on had it
#
aaronpk
... so it would be great to get it working, but if we can't even get public working then we shouldn't do access control
#
aaronpk
... So in terms of activiitypump, it's nice that it's the one that's closest that maps to AS2.0
#
aaronpk
... if you're looking to converge with the indieweb aapproach, what is your take on the form encoding
#
aaronpk
Tsyesika: there's lots of nested stuff, but they get around it by posting stuff individualyand referencing it by ID
#
aaronpk
... that'd work, but i'm not huge on making lots of requests
#
aaronpk
... i'm not necessarily against form encoding, but JSON has its merits, and especially JSONLD given its extensibility
#
eprodrom
I have the answer, call on me
#
Arnaud
ack eprodrom
#
Zakim
sees elf-pavlik on the speaker queue
#
Zakim
sees elf-pavlik on the speaker queue
#
aaronpk
eprodrom: it's entirely possible, we had a mechanism in pump.io to include the image in the json encoded upload
#
Zakim
sees elf-pavlik, bblfish on the speaker queue
#
aaronpk
... it's less popular because you have to do some encoding in the JSON upload, so people like the double post more often
#
hhalpin_
I'm trying to map the "big" differences and see where we can get consensus on the larger whole.
#
aaronpk
... i'd also point out that the double-post mechanism comes from the atompub protocol
#
Zakim
sees elf-pavlik, bblfish, aaronpk on the speaker queue
#
aaronpk
eprodrom: there is a mechanism in pump.io that didn't make it into activitypump, to encode a binary object in JSON, so if it's needed we can pull it over
#
aaronpk
... the other option is the double post mechanism
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss sidefects
#
Zakim
sees bblfish, aaronpk on the speaker queue
#
cwebber2
elf-pavlik: it could be viewed in an RDF type graph as well that's probably true
#
cwebber2
what happens if you follow, unfollow, follow?
#
aaronpk
elf-pavlik: posting the as:follow activity has the side effect of adding the :follows edge
#
hhalpin_
Arnaud, you may want to mention the IBM testing effort for ActivityStreams about now
#
eprodrom
elf-pavlik: is the point that we'd have to test the behaviour?
#
aaronpk
...you could make an automated test
#
eprodrom
q?
#
Zakim
sees bblfish, aaronpk on the speaker queue
#
aaronpk
Tsyesika: when you submit a folow activity, twot hings happne. the activity is federated to the audience, and the user is added to the followers collection
#
aaronpk
... so in the future, when you post to the followers collection as the audience, it will also federate to the new person
#
hhalpin_
What is difficult about testing the side-effects (i.e. input->outputs)?
#
aaronpk
eprodrom: i think elf's point is that we don't have all those side effects listed out under the follow activity
#
aaronpk
... we should probably do that for each of these activities
#
hhalpin_
+1 be clearer about the input/outputs but bugs will be worked out in test-suite
#
eprodrom
"The Follow activity is used to subscribe to the activities of another user. Once the user has followed a user, activities shared with the Follows of that user SHOULD be added to the actors's inbox."
#
Arnaud
ack bblfish
#
Zakim
sees aaronpk on the speaker queue
#
aaronpk
bblfish: LDP also doesn't know how to do multiple files in one go
#
cwebber2
multiple files is an interesting motivation for the file endpoint
#
cwebber2
I hadn't realized that bit
#
aaronpk
... couldn't activithypump also use multipart uploads?
#
aaronpk
Arnaud: currently LDP1.0 spec doesn't talk abotu how to optimize this kind of operation, you have to deal with every resource independelty
#
aaronpk
.. there have been discussions about how to optimize the traffic
#
aaronpk
... there was some ealier draft that allowed it, there were questions about the details, so we took it out, now it's on the wishlist
#
Zakim
-eprodrom
#
aaronpk
... we just discussed the priority items for LDP, it was selected to allow that for the read, but not for the write
#
aaronpk
... it's not clear that the next version will allow to post multiple things inthe same operation
#
aaronpk
timbl: we could take input from here
#
Loqi
timbl has 3 karma
#
aaronpk
Arnaud: people are welcome to express their opinion here whether that's a priority
#
Zakim
+eprodrom
#
Arnaud
ack aaronpk
#
Zakim
sees no one on the speaker queue
#
rhiaro_
elf-pavlik I'll scribe
#
elf-pavlik
aaronpk: i want to talk about Harrys question about convergence of APIs
#
rhiaro_
aaronpk: I wanted to talk about quesiton of converging apis
#
Zakim
-eprodrom
#
rhiaro_
... Bigger difference than form encoding
#
bblfish
yes @sandro but there is also the list of 6 items that are being proposed for LDP next charter. that is more important
#
rhiaro_
... In activitypump you're always creating an activity that references an object, but in micropub you only create an object and no explicity activity
#
Zakim
+ +1.514.525.aaaa
#
rhiaro_
... trying to make those match up is more than dealing with nested objects
#
cwebber2
aaronpk, I think you are right on that analysis
#
Zakim
- +1.514.525.aaaa
#
rhiaro_
... it would take something like making micropub create activities vs objects, or having the activitypump api create the activities as a side effect of the object, rather than explicitly creating activities
#
sandro
bblfish, sure, it's all up to there ACTUALLY being a sufficient community to do this.
#
rhiaro_
harry: do developers find it easier to work with activities or objects directly?
#
rhiaro_
aaronpk: from what I've seen creating objects directly has been extremely straightfoward
#
rhiaro_
... but i haven't talked to a lot of people who are creating activitystreams posts
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
Zakim
sees eprodrom on the speaker queue
#
rhiaro_
Tsyesika: a matter of personal preference
#
rhiaro_
... activities are subject verb object type things
#
rhiaro_
... like Tsyesika posts Image
#
Zakim
+eprodrom
#
bblfish
yes, indeed but there should be a list of approved stories, so that those who are do not see their story in the wishlist, can at least drum up support :-) Ie. we need a diff
#
elf-pavlik
q+ re: shortly lon side effects in MicroPub, ActivityPump and LDP
#
Zakim
sees eprodrom, elf-pavlik on the speaker queue
#
rhiaro_
... activities very much how yo'd construct a sentence
timbl joined the channel
#
rhiaro_
... It's not too difficult for developers to work with activities. Just personal preference, one isn't easier or harder
#
eprodrom
Hey, the conference bridge is a mess
#
eprodrom
Am I the only one who can't hear anything, cwebber2 ?
#
bblfish
yes, indeed but there should be a list of approved LDP next desires, so that those who are do not see their desire in the LDP next, can at least drum up support :-) Ie. we need a diff
#
cwebber2
eprodrom: it's been the hard the whole time, believe it or not it's better than it was ;\
#
rhiaro_
Arnaud: aaron's point is that the significat difference between the two approaches is activities are implied and maybe reconstructed if you need to, whereas here they're explicitly stated and created as independant resources
#
Zakim
sees eprodrom, elf-pavlik on the speaker queue
#
eprodrom
Oh
#
Arnaud
ack eprodrom
#
Zakim
sees elf-pavlik on the speaker queue
#
eprodrom
Hi
#
eprodrom
Developers overwhelmingly prefer the activity style
#
elf-pavlik
eprodrom, we can't hear you
#
elf-pavlik
Zakim, who's on the call?
#
Zakim
sees on the phone: INRIA, cwebber2, eprodrom
#
eprodrom
I know, because your phone is all messed up
#
cwebber2
eprodrom: they can hear fine though
#
cwebber2
we just can't hear them
#
eprodrom
We had about an OOM difference between object-style and activity-stle
#
kaepora
(Sorry I'm late: I'd like to repeat my offer to have a "crypto Q&A session" today so I can help as the invited observer who works in crypto)
#
aaronpk
eprodrom: with pump.io we have an order of magnitude difference between people doing operations on activityies vs creating objects directly
#
akuckartz
kaepora++
#
Loqi
kaepora has 1 karma
#
eprodrom
I can't hear, have to wait for the scribe
#
cwebber2
eprodrom, the question was:
#
eprodrom
Is there a way to fix the phone there?
#
sandro
we can try hanging up and dialing again, I guess
#
Arnaud
we didn't know it was broken!
#
sandro
you're not hearing anything?
#
bblfish
we need a cofee break to fix it. What is the problem you are experienceing @eprodrom ?
#
cwebber2
eprodrom, could you clarify, was it that you had an experience with an overwhelming number of developers having preference
#
aaronpk
sandro: i think you were saying you tried both approaches and people preferred one?
#
cwebber2
between activities and objects
#
cwebber2
let eprodrom respond before we do that dacne
#
eprodrom
Yes, from pump.io logs
#
AnnB
you guys can't hear anything?
#
AnnB
we didn't know
#
Arnaud
none of you can hear us?
#
eprodrom
I can barely hear
#
AnnB
hmm
#
eprodrom
BETTER
#
eprodrom
YES
#
sandro
cwebber2, it was working earlier, right? did it stop at some point?
#
cwebber2
yes much better
#
cwebber2
sandro: it has been bad the whole time
#
cwebber2
sandro: but it was even worse earlier
#
aaronpk
we didn't change anything, we're just going to have to speak loudly
#
hhalpin_
we could always switch to talky.io
#
cwebber2
I agree it's not a connection
#
cwebber2
now it's much clearer
#
sandro
it's just a long room, so some people aren't near the speakerphone.
#
cwebber2
anyway, maybe eprodrom should be able to reply to that point before we do any connect/disconnect dance?
#
Zakim
sees elf-pavlik, cwebber on the speaker queue
#
eprodrom
q+
#
Zakim
sees elf-pavlik, cwebber, eprodrom on the speaker queue
#
Zakim
sees elf-pavlik, eprodrom on the speaker queue
#
rhiaro_
eprodrom: did you mean people use posting of activities more than PUT and DELETE on objects?
#
cwebber2
eprodrom: your turn to speak
#
cwebber2
are you muted?
#
eprodrom
Yes
#
eprodrom
One sec
#
Arnaud
eprodrom, can you please expaned a bit on what you meant
#
eprodrom
Let's just go to break, I'm sorry
pfefferle joined the channel
#
sandro
is there something you want us to do during the break?
#
aaronpk
eprodrom: yeah we did a big log scan based on a question from tantek. we had about 10x more people using activities endpoints posting update and delete activities ranther than PUT and DELETE on objects
#
rhiaro_
eprodrom: that was via Tsyesika btw
#
Arnaud
ack eprodrom
#
Zakim
sees elf-pavlik on the speaker queue
#
aaronpk
eprodrom: i'd like to talk about differences between activitypump and pump.io api
#
aaronpk
... there's a notify method, pump.io uses a regular webhooks mechanism, the other is activitypump requires https IDs for objects and pump.io allows any ID for objects
#
aaronpk
... the requiement for https IDs came in from activitypump
#
aaronpk
... i'm not crazy about it
#
aaronpk
Tsyesika: there's an issue open about both things, most of those are things left from how oshepherd wanted it, and I just didn't change it
#
hhalpin_
so maybe dropping those HTTP IDs might be possible.
#
aaronpk
... i'm more than open to having less stringent requirement for IDs, I don't think requiring TLS on URIs is necessary
#
hhalpin_
that would probably make people happier re convergence
#
hhalpin_
q+
#
Zakim
sees elf-pavlik, hhalpin_ on the speaker queue
#
rhiaro_
people using activities endpoint over PUT on objects could be a preference for endpoints over restful, not necessarily activities over objects (cc Tsyesika, eprodrom, cwebber2)
#
aaronpk
... for the most part we're open to change
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss shortly lon side effects in MicroPub, ActivityPump and LDP
#
Zakim
sees hhalpin_ on the speaker queue
#
aaronpk
elf-pavlik: activitypump seems heavy on side effects, LDP seems light on side effects
#
aaronpk
...the user posts a file is a great story to demonstrate side effects
#
aaronpk
... if we all compare this story we can talk more about the side effects
#
aaronpk
Arnaud: i thinkwe can defer that discussion to later
#
hhalpin_
q?
#
Zakim
sees hhalpin_ on the speaker queue
#
aaronpk
... the plan is next to talk about the similar stories with SoLID, the rest of the day is about talking about how they compare
#
hhalpin_
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
Arnaud
ack hhalpin_
#
Zakim
sees no one on the speaker queue
#
aaronpk
hhalpin_: we are at inria, the world top center for TLS and web security stuff...
#
aaronpk
... i'm going to talk with the researchers here, if people wanted to do a brief security session, maybe people would be interested
#
KevinMarks
hm, the dev pref for activities seen on pump could be because those are theire esamples
#
cwebber2
totally dropping out
#
elf-pavlik
+1 TLS session
#
cwebber2
the call, I mean :)
#
KevinMarks
PUT rather than POST?
#
hhalpin_
should we do a crypto or TLS session?
#
hhalpin_
I'll ask Karthik what his schedule is, but Nadim could also do it.
#
aaronpk
Arnaud: let's take a break for now, 10-15 minutes then look at SoLiD
#
KevinMarks
PUT is a pain to do; POST is a form, hence micropub
#
AnnB
bye, cwebber2 ... if you're going
#
cwebber2
AnnB: oh I'm not leaving
#
eprodrom
Tsyesika: I just found out that SUBSCRIBE/NOTIFY is an existing model in WebDAV
#
cwebber2
I meant, the call was dropping in and out of my ability to hear :)
#
AnnB
ah yes .. they're rebooting phone I think
#
eprodrom
Tsyesika: also, great job!
#
cwebber2
yes indeed
#
Tsyesika
eprodrom: thanks! sorry about the few mistakes i made >.<
#
AnnB
yes, Tsyesika++
#
cwebber2
Tsyesika, kick ass work :)
#
cwebber2
Tsyesika++
#
Loqi
Tsyesika has 10 karma
#
eprodrom
Tsyesika: yes, sorry about my outburst
#
eprodrom
With pump.io, the "comment" type isn't required for a response
#
Tsyesika
thanks for clarifying
#
eprodrom
Any in-reply-to response will work
#
AnnB
pretty mild, if that was an outburst!
#
cwebber2
anyway, I knew Tsyesika was the right person to present on the subject
#
eprodrom
However, I think the Web UI will barf if it sees something besides a comment there
#
eprodrom
Yes, fantastic
#
cwebber2
Tsyesika: I think you did a clearer job of presenting on the spec than I would have!
#
eprodrom
Did you ever hear back from Owen Shephard?
#
cwebber2
ok, now that we're at a bredak
#
cwebber2
I can finally get coffee
#
cwebber2
finallyyyyyyy
#
oshepherd
eprodrom: *sticks nose in*
#
AnnB
go for it!
#
eprodrom
HEY
#
cwebber2
ohai oshepherd :)
#
eprodrom
Also, misspelled
#
eprodrom
Your last name
#
eprodrom
Hooray that you are here oshepherd
#
oshepherd
I have been suuuuper busy
#
sandro
anyone on the phone
#
oshepherd
I commented a couple of weeks back on verb vs object orientation... My conclusion was that the only difference here between indieweb and ActivityStreams *in practice* was the "post"/"share" verbs which IMO are very contentless (and I'd actually prefer ActivityStreams without them, because in practice they're - specifically the post verb - a huge source of problems in pump.io
#
oshepherd
Specifically the problem is that you really want the audience attached to the object, but it ends up attached to the post
tantek joined the channel
#
oshepherd
Anyway, on the subject of mandatory TLS: I'll note that the both Google, Mozilla and I believe the W3C itself have announced an intent to deprecate HTTP (non-S)
#
eprodrom
Understood
#
eprodrom
I like a SHOULD but I'm less crazy about a MUST
#
eprodrom
I also like Webfinger
#
eprodrom
But I understand that the requirement for dereferenceable URIs makes that more complex
#
oshepherd
I haven't had a chance to catch up with Tsyesika's changes, but I did keep Webfinger *just* for the use case of translating user@domain identities
#
eprodrom
(We have to drag in the Webfinger spec)
#
eprodrom
Oh, I think it's out now
#
Zakim
-eprodrom
#
eprodrom
elf-pavlik: I find it funny that you talk about the update to the social graph as a "side effect"
#
eprodrom
It seems like the primary intent of posting a "follow" activity
#
oshepherd
Theres a whole lot of social platforms out there today using such identities - StatusNet, PumpIO, Diaspora, more traditional things like XMPP, even email. I don't think we can say "Sorry, you have to throw away all your user IDs" to them
#
eprodrom
I see your point
#
eprodrom
But I think there's something to be said for consistency too
#
eprodrom
(I prefer keeping the Webfinger ID, btw)
#
oshepherd
But I very much kept WebFinger use minimal - its' just "take an acct URI and translate it into the URI of an ActivityStreams profile document" - and if your IDs aren't in acct: form, you don't need to implement a server
#
eprodrom
All of which is to say
#
eprodrom
oshepherd++
#
Loqi
oshepherd has 3 karma
#
eprodrom
Tsyesika += 1,000,000
#
eprodrom
Actually I guess in Python that'd be
#
eprodrom
Tsyesika = Tsyesika + 1000000
#
oshepherd
Python has +=
#
eprodrom
Oh
#
eprodrom
Great!
#
oshepherd
Doesn't have ++ though, unless my brain has gone fuzzy
#
eprodrom
I usually assume that if a particular syntax element is convenient Python prudishly disallows it
#
eprodrom
B-)
#
oshepherd
I spend most of my time coding in SystemVerilog these days which is the mother of not-at-all convinient
Gabriel_Lachmann joined the channel
#
oshepherd
(No, SystemVerilog, nobody wanted their function's member variables to default static. But that's enough ranting about SystemVerilog :-))
#
eprodrom
Wow
#
eprodrom
OK, I will pipe down then
#
eprodrom
Tsyesika, it looks like AS2.0 doesn't even have a "comment" type
#
eprodrom
Which is probably good
#
eprodrom
I've never been a big fan
#
Tsyesika
eprodrom: yeah we use "Note" type as an example of what i'd use a "comment" in pump.io for
#
oshepherd
It's basically just a "note"
#
rhiaro_
scribenick: rhiaro
#
aaronpk
scribenick: rhiaro_
#
rhiaro_
Arnaud: we have all afternoon, if we don't get through before lunch we can go on after
#
rhiaro_
... can people on the phone hear?
#
cwebber2
I can hear
bblfish and akuckartz joined the channel
#
Tsyesika
oshepherd: i did want you to look at #15 and #19 on https://github.com/w3c-social/activitypump/issues
#
Tsyesika
oshepherd: not now but sometime
#
Zakim
+eprodrom
#
rhiaro_
deiu: will start with most basic example, create edit and delete a note
#
rhiaro_
... then henry's going to go over two more complex examples, profile editing and access control stuff
#
rhiaro_
... So SoLiD uses LDP to create new resources and manage resources
#
rhiaro_
... This makes it really easy for people who are used to a restful way of doing things
#
rhiaro_
... compared to previous examples, we're not using an endpoint to post new data, but creating data inside a container that is used to store similar types of resources
#
rhiaro_
... in this case, a notes container
#
oshepherd
Tsyesika: Using the NOTIFY element is supremely elegant. It's also quite likely to be a supreme pain in the ass, so I'd say go ahead and replace it with POST.
#
rhiaro_
... So we can see here our examples use curl
#
rhiaro_
... just to give you an impression of how simple they are
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
aaronpk
q+ to ask about "slug"
#
Zakim
sees eprodrom, aaronpk on the speaker queue
#
rhiaro_
... What we're doing is sending a post request with slug header, and data containing actual note. Uses activitystreams terms to describe note
#
rhiaro_
... [and is turtle]
#
rhiaro_
... could be json-ld
#
oshepherd
Tsyesika, as for HTTPS, maybe table this one for later. By the time any spec becomes a REC, I expect Lets Encrypt should make TLS certs trivially available
#
eprodrom
Could you speak up, please, deiu ?
#
rhiaro_
... use AS2.0 vocab
#
rhiaro_
sandro: we haven't implmeented anything that uses that
#
rhiaro_
deiu: we don't have an app that consumes AS2.0 data
#
rhiaro_
... the point is to demonstrate how you create and modify data
#
rhiaro_
timbl: you can do it with a client without the server knowing anything
#
rhiaro_
deiu: What the server returns is a Location header which has the full URI of the new resource
#
rhiaro_
... Second step is to correct/complete the note that was sent before
#
rhiaro_
... Client needs to update existing resource with the new data
#
rhiaro_
... SoLiD has two ways of doing this
#
rhiaro_
... can do a PUT to replace whole resource
#
rhiaro_
... uses URI of new resource, that you get back in the Location header
#
Tsyesika
oshepherd: might be good to write that on the issue just so evan can respond, i am not against lowering the requirements but i'm also not really bothered by it either but it seems evan is
#
rhiaro_
... Second way of doing is to send an HTTP PATCH with a SPARQL UPDATE
#
eprodrom
Yes
#
eprodrom
I am
#
rhiaro_
... in which you modify only the bit of information you want to change
#
AnnB
phone people ... are you still having trouble hearing?
#
eprodrom
Yes, it's just fading in and out
#
rhiaro_
... We should probably add PATCH but it's not relevant to this group
#
eprodrom
I think the speaker needs to be louder or closer to the phone
#
aaronpk
he's as close as he can get
#
rhiaro_
sandro: PATCH is subject to conneg. The one here is implemented, but there's a w3c rec for a different patch format
#
eprodrom
OK, thanks
#
rhiaro_
deiu: we do support json patches
#
rhiaro_
... if you have json-ld file you could use that
#
rhiaro_
... final step is user decides to delete note
#
rhiaro_
... HTTP operation on the resource itself (DELETE)
#
Zakim
sees eprodrom, aaronpk on the speaker queue
#
Arnaud
ack eprodrom
#
Zakim
sees aaronpk on the speaker queue
#
elf-pavlik
q+ re: request for Social WG oriented view on SoLid
#
Zakim
sees aaronpk, elf-pavlik on the speaker queue
#
rhiaro_
eprodrom: social software often when you're posting a note, you would send it somewhere, like the inbox of followers or mentions inbox of person mentioned
#
rhiaro_
... I understand this wouldn't be possible?
#
rhiaro_
... So side effect wouldn't happen server side, has to happen client side
#
rhiaro_
deiu: yes, everything happens in the client. Client is charged to send notification to someone's inbox
#
rhiaro_
... or you could have additional app-specific service which listens to changes on containers
#
rhiaro_
... then based on changes on containers like new resource created, could trigger app-specific processes
#
rhiaro_
melvster: triggers websocket
#
rhiaro_
eprodrom: that's interesting
#
elf-pavlik
ACTION: pelf create comparison of side effects approach in MicroPub, ActivityPump and SoLiD
#
trackbot
is creating a new ACTION.
#
RRSAgent
records action 1
#
trackbot
Created ACTION-61 - Create comparison of side effects approach in micropub, activitypump and solid [on Pavlik elf - due 2015-05-12].
#
rhiaro_
... twitter members have millions or tens of millions of follows, would not be scaleable to have client distribute note to millinos of inboxes
#
Zakim
sees aaronpk, elf-pavlik, bblfish on the speaker queue
#
rhiaro_
... starts becoming difficult for client
#
rhiaro_
... and if two different clients do it differently you don't have a very consisten social experience
#
rhiaro_
... so if there is a way to have a consistant side effect that provides these sorts of features in ldp that would be interesting
#
melvser1
q+
#
Zakim
sees aaronpk, elf-pavlik, bblfish, melvser on the speaker queue
#
rhiaro_
... access control too
#
rhiaro_
deiu: we have access control
#
rhiaro_
... SoLiD does implement websockets
#
rhiaro_
... has a websocket interface for all it's resources
#
rhiaro_
... you could have a service which listens on a websocket which has subscribed to that container, which can process all the data that gets into the container
#
cwebber2
huh, that's interesting
#
rhiaro_
timbl: which works for hundreds of thousands of people
#
rhiaro_
eprodrom: if you come check yoru inbox in the morning and want to see all the stuff that happened since yesterday, has to be some kind of application process, or you can leave a websocket open all night
#
rhiaro_
... so websocket interesting for online updates, but not distirbution
#
rhiaro_
deiu: distribution happens by a service, like a pubsub service
#
rhiaro_
... that listens to data and upates all its subscribers
#
rhiaro_
Arnaud: more background on ldp
#
elf-pavlik
ACTION: pelf document possible danger of malicious apps when moving more responsibilities to clients
#
trackbot
is creating a new ACTION.
#
RRSAgent
records action 2
#
trackbot
Created ACTION-62 - Document possible danger of malicious apps when moving more responsibilities to clients [on Pavlik elf - due 2015-05-12].
#
rhiaro_
... there are different use cases. LDP spec defines generic protocol to create and update and find resources
#
rhiaro_
... but there are different types of servers that can implement LDP
#
rhiaro_
... there is what we refer to as (??) applications
#
rhiaro_
... no specific application semantic associated
#
melvser1
q-
#
Zakim
sees aaronpk, elf-pavlik, bblfish on the speaker queue
#
rhiaro_
... generic datastore
#
rhiaro_
... you send bits, they store, you ask and they return
#
rhiaro_
... never any side effects
#
rhiaro_
... Other peopel use LDP with very application specific servers
#
rhiaro_
... for example, IBM uses LDP in the context of application lifecycle management
#
rhiaro_
... LDP is a thin layer put on the top of legacy software
#
rhiaro_
... in this case when you create a resource using LDP you create something with very specific semantics, and has application specific side effects
#
rhiaro_
... possible to imagine in this case youc ould hasl have an application specifi cserver, with side effects like distribution and notifications and things like that
#
Arnaud
ack aaronpk
#
Zakim
aaronpk, you wanted to ask about "slug"
#
Zakim
sees elf-pavlik, bblfish on the speaker queue
#
rhiaro_
aaronpk: about slug - is that meant to be a unique slug per note, or a namespace where multiple things go?
#
eprodrom
rhiaro_: thanks for scribing so well
#
rhiaro_
deiu: a hint on how you want URI to end up looking
#
rhiaro_
... was name, not namepsace
#
rhiaro_
... suggested name
#
rhiaro_
... server could ignore it
#
rhiaro_
Arnaud: that's not specific to LDP, there's an RFC on slug
#
rhiaro_
aaronpk: Ok. Other thing - you do or do not have implementations consuming the data?
#
rhiaro_
deiu: I meant about activity streams vocab
#
rhiaro_
... we don't have an implementation that consumes AS
#
rhiaro_
... things created so far don't use AS
#
rhiaro_
sandro: CIMBA uses SIOC
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss request for Social WG oriented view on SoLid
#
Zakim
sees bblfish on the speaker queue
#
elf-pavlik
action-61
#
trackbot
is looking up action-61.
#
trackbot
action-61 -- Pavlik elf to Create comparison of side effects approach in micropub, activitypump and solid -- due 2015-05-12 -- OPEN
#
rhiaro_
elf-pavlik: for the side-effects I created action-61
#
rhiaro_
... I don't think it's enough to just have this in minutes
#
rhiaro_
... we should document on wiki
#
rhiaro_
... Also I'm going to request on SoLiD repo that we can have a social web perspect
#
rhiaro_
... ive
#
rhiaro_
... eg. using json-ld first instead of turtle, etc
#
rhiaro_
... to make it easier for group
#
rhiaro_
... whoever wants to work on it with me, can help
#
sandro
q+ to say I'd like webmention to be part of vanilla LDP
#
Zakim
sees bblfish, sandro on the speaker queue
#
rhiaro_
timbl: do you think making it a live switchabe document, switching example format between json-ld and turtle is good? Or document rewritten?
#
rhiaro_
elf-pavlik: I think some things like with sparql updates, some peopel won't even want to go there
#
eprodrom
elf-pavlik: That's true
#
rhiaro_
deiu: sparql and ldp patch or whatever else have been added as alternatives
#
rhiaro_
... in addition to LDP http requests
#
eprodrom
My eyes just skip over those options
#
rhiaro_
... we should work together
#
Arnaud
ack bblfish
#
Zakim
sees sandro on the speaker queue
#
rhiaro_
elf-pavlik: make it clear we don't HAVE to use these
#
elf-pavlik
11:36 eprodrom My eyes just skip over those options
#
AnnB
what do you mean, eprodrom, that your "eyes skip over those options"?
#
rhiaro_
bblfish: it woudl be extremely useful for LDP or this group, to have some way for any resource to be able to say I want to subscribe to this resource so you can say you want to see any changes on a document. Could be really generic
#
claudio
q+
#
Zakim
sees sandro, claudio on the speaker queue
#
rhiaro_
... would work like activitystreams, could poitn to another collection somewhere else
#
eprodrom
When there's a section of SoLiD like, "Or, you could do a SPARQL query like this..."
#
rhiaro_
... the resource itself on the server could post notification changes
#
eprodrom
AnnB: ^^^^
#
rhiaro_
... we could solve the problem mentione don the phone
#
aaronpk
eprodrom: AnnB: same with me
#
rhiaro_
Arnaud: there are discussions about this in LDPNext about being able to keep track of changes to resources and be notfied
#
rhiaro_
... you can have an optimal way of knowing what has changed
#
AnnB
does that mean it's not useful to you, or it's not actually functioninng, or ...??
#
rhiaro_
... instead of having to fetch the whole resource and figure it out
#
rhiaro_
... you can use patch format to tell you what has changed. Possible in future of LDP
#
Arnaud
ack sandro
#
Zakim
sandro, you wanted to say I'd like webmention to be part of vanilla LDP
#
Zakim
sees claudio on the speaker queue
#
rhiaro_
AnnB some people are allergic to rdf and sparql :)
#
eprodrom
AnnB: It's not useful to me, and mentioning it in the spec is less helpful
#
rhiaro_
sandro: what would solve that is if webmention were standardise and LDP incorporate that
#
eprodrom
q+
#
Zakim
sees claudio, eprodrom on the speaker queue
#
rhiaro_
... assumign you can have massive webmention servers. Offloads from client and puts in normal server infrastructure
#
Arnaud
ack claudio
#
Zakim
sees eprodrom on the speaker queue
#
KevinMarks
PUT and PATCH are retro von Neumann worldviews
#
rhiaro_
claudio: from my commercial point of view, most of the use cases are around personas rather than topics
#
KevinMarks
POST is more general
#
Zakim
+ben_thatmustbeme
#
rhiaro_
... but we have uses cases where it's important to people to stream content, to interact over topics instead of among each other
#
ben_thatmustbeme
Zakim, mute me
#
Zakim
ben_thatmustbeme should now be muted
#
AnnB
so eprodrom, is that specific to rdf and sparql, or all of the linked data stuff?
#
rhiaro_
... If we have a streaming event like a movie, we are really interested in seeing what people are thinking about a topic
#
eprodrom
AnnB: it's actually more editorial about the document
#
AnnB
aha, thanks
#
rhiaro_
... we are forseeing technologies for adapting streaming content to people's mood etc. So critical to happen realtime. I wonder if these technical solutions would cover it
#
eprodrom
There's one clear and simple way to get a task done, then a few other options that are less clear and less simple
#
KevinMarks
movie's aren't streaming
#
rhiaro_
... As far as I understand most silos are consumer oriented. In twitter you can provide a topic and see how people react to that
#
rhiaro_
... We are using webRTC, there's a lot to do, to provide personalised video streams
#
rhiaro_
... so we need to knwo what people are thinking
#
rhiaro_
sandro: hashtags?
#
AnnB
altho I still don't truly understand the nuance of your comment
#
KevinMarks
2-way is streaming; movies are downloads
#
rhiaro_
claudio: yes but we dont' want to rely on twitter
#
rhiaro_
... intresting example with virtual product placement, or virtual notification of live streaming events
#
rhiaro_
... We are not sure we can model it with most of these decentralised solutions
#
eprodrom
claudio: there are two options
#
Zakim
sees eprodrom, cwebber on the speaker queue
#
KevinMarks
hashtags are not bound to twitter
#
ben_thatmustbeme
eprodrom, is audio in and out with you as well or is it just me?
#
AnnB
fyi, Claudio is from Telecom Italia
#
KevinMarks
they span multiple models
#
rhiaro_
sandro: out of scope for this group
#
eprodrom
ben_thatmustbeme: for me too
#
rhiaro_
Arnaud: do we have user stories that get close to this?
#
cwebber2
ben_thatmustbeme: yeah the call quality is not good
#
rhiaro_
bblfish: we have a bug database that is content oriented
#
rhiaro_
... or one for a product
#
rhiaro_
... interaction on an object not on a [person] community comes around the object
#
ben_thatmustbeme
eprodrom, cwebber2 seems to be when speaking too softly
#
rhiaro_
sandro: hashtags are harder, they don't have identifiers
timbl joined the channel
#
rhiaro_
claudio: we are looking at things in Telecom Italia, in talks with netflix, they're using product placement for funding content
#
rhiaro_
... this could be done on the fly
#
rhiaro_
... adaptive advertisement
#
rhiaro_
... customise content basedon what people are saying in realtime
#
rhiaro_
... this is feasible
#
aaronpk
yeah we really need external mics for the phone because the people on the ends of the table are super hard to hear
#
ben_thatmustbeme
cwebber2, eprodrom, again, don't use ':' or you are speaking for me. I thought you had to be scribe for that to happen, but sandro indicated otherwise
#
eprodrom
ben_thatmustbeme, sorry
#
rhiaro_
... we rely on twitter for now because we don't have an open decentralised solution for this
#
rhiaro_
... I understand may be out of socpe
#
aaronpk
wait really? I thought that only applied to the scribe. uhoh.
#
rhiaro_
... topics could be in the future
#
Zakim
sees eprodrom, cwebber on the speaker queue
#
cwebber2
ben_thatmustbeme, sorry, it's my client default to use :
#
cwebber2
so I have to correct it constantly
#
Zakim
-eprodrom
#
ben_thatmustbeme
aaronpk, we'll find out for sure soon
#
aaronpk
yeah it's every IRC client default to use that
#
rhiaro_
my client uses : too, I thought it was IRC standard
#
rhiaro_
sandro: we had a hashtags user stories, was -1 because it's too hard
#
cwebber2
I figured the scribenick made it clear
#
AnnB
(I called his attention to your comment, KevinMarks, about streaming vs download)
#
rhiaro_
elf-pavlik: could observe if something is otu of scope and check if something might block it in the future and flag it
#
cwebber2
but I guess not
#
rhiaro_
... and we can do our best to take that into account
#
rhiaro_
claudio: I wonder if takign it into accoutn could make it easier if we decide we want to handle it
#
cwebber2
I guess it doesn't, at least, when someone takes over for scribing
#
rhiaro_
... I understand standardising hashtags is not easy
#
Zakim
+eprodrom
#
rhiaro_
... or impossible
#
rhiaro_
... but could be valuable
eprodrom_ joined the channel
#
eprodrom_
q?
#
Zakim
sees eprodrom, cwebber on the speaker queue
#
eprodrom_
Aha
#
AnnB
no worries
#
rhiaro_
bblfish: a company taht did a bookmarking service, you could bookmark things and when you typed a word they would do a text analysis, then find dpbedia concepts and URIs that were related to concepts in the page
#
rhiaro_
... it looks to the user like a hashtag, but behind is the semantics of dpbedia and URIs
#
ben_thatmustbeme
aaronpk, rhiaro_, well i suppose it does make things easier for the scribe
#
rhiaro_
^^ bbc does that to help journalists tag news articles
#
rhiaro_
... helps users avoid clashes
#
eprodrom_
Are we still talking about the media monitoring?
#
rhiaro_
timbl: there are some structured hashtags, some are totally random
#
rhiaro_
... it would be fun though
#
eprodrom_
Could we maybe get back to the social API agenda?
#
KevinMarks
autocomplete is fine, estatign the tag the user assigned isn't
#
eprodrom_
Arnaud, are we on-topic?
#
rhiaro_
elf-pavlik: could have hashtag.cc like prefix.cc
#
eprodrom_
I'd like to talk about SoLiD
#
Arnaud
ack eprodrom
#
Zakim
sees cwebber on the speaker queue
#
rhiaro_
ALERT everyone's wifi passcodes are expiring
#
rhiaro_
stay tuned
#
rhiaro_
eprodrom: can we go back to talking about SoLiD
#
rhiaro_
... concerned that notifications like webmention might be useful, but in other ones there's a more complex effect in executing a social action
#
rhiaro_
... eg a follow action would update the actor's following list
#
rhiaro_
... and distribute follow action to serveral inboxes
#
rhiaro_
... so I'm not sure this is just about notification
#
rhiaro_
... there's a lot of updates that could happen
#
rhiaro_
... again, it's all entirely possible to do these using polling
#
rhiaro_
... you could poll every list of every social graph then add reverse pointers
#
rhiaro_
... but much easier to get collection of people
akuckartz joined the channel
#
rhiaro_
... if we use SoLiD we're goign to have to put a lot of burden on the client which is unfair to the client and likely to generate a lot of errors
#
rhiaro_
... or we're going to have to limit ourselves to very simple social interactions
#
Zakim
sees cwebber on the speaker queue
#
Arnaud
ack cwebber
#
Zakim
sees no one on the speaker queue
#
rhiaro_
bblfish: we have more examples
#
timbl
One could use (coincidentally) a distributed hash table for coordonating people interested in hashtags. The problem is a bit like the NNTP newsgroup distribution problem, as newsgroup names and hashtags are bothe basicallt arbitrary short strings.
#
elf-pavlik
action-61
#
trackbot
is looking up action-61.
#
trackbot
action-61 -- Pavlik elf to Create comparison of side effects approach in micropub, activitypump and solid -- due 2015-05-12 -- OPEN
#
elf-pavlik
eprodrom_ let's work on documenting it together?
#
rhiaro_
cwebber2: I'm curious what happens in terms of how much link rot impacts this system, especially if you end up having commuincation with someone else and their whole site goes down? How does that affect yoru local record of your interaction with them? And also resolving information about that?
#
rhiaro_
... curious about what ends up happening when somebody else's server goes down
#
eprodrom_
timbl, you could also have one or more aggregation servers
#
rhiaro_
deiu: how is this specific to solid? will affect any decentralised service?
AnnB_ joined the channel
#
KevinMarks
hashtags converge because language converges
#
rhiaro_
cwebber2: if my mail server goes down you can't send me email. You still have access to all the email you have from me
#
rhiaro_
... and contact metadata
#
Zakim
sees no one on the speaker queue
#
rhiaro_
... I'm not making a comment, this is a real question
#
sandro
As Evan said: -1. I think search is probably difficult to do for this API. Maybe a separate API? --Evan Prodromou (talk) 16:02, 18 February 2015 (UTC)
#
elf-pavlik
q+ re: capturing ACTIONs
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro_
sandro: we don't address that yet, the answer is to use caching proxies or archiving services where I access your site through something that keeps a copie
#
rhiaro_
... we need that for performance reasons too
#
KevinMarks
to put it another way, hashtags works precisely because they don't have namespaces; thus forcing convergence
#
rhiaro_
deiu: in a decentralised system, there are two ways to shuffle information around
#
rhiaro_
... you base it on poll or push
#
rhiaro_
... either you push notifications to people directly to their own servers
#
rhiaro_
... or you wait for them to poll your feed/outbox of notifications and everyone gets theirs when they want
#
rhiaro_
bblfish: interesting compatibility with AS2
#
rhiaro_
... you could have feed of activities which you fill in whenever an action happens on the LDP server
#
rhiaro_
... if a client misses a poll request they can go back to the feed and find all the changes
#
rhiaro_
... this might be where this is going
#
rhiaro_
timbl: you can convert between the two
#
cwebber2
thx sandro, deiu
#
rhiaro_
... when you know the state of some resource you can accumulate the differences
#
deiu
no problem :)
#
rhiaro_
... if you have a series of update messages you can generate the results
#
rhiaro_
Arnaud: eprodrom, isn't that true for all other solutions too?
#
rhiaro_
... if aaron's website is down I can't access any content?
#
cwebber2
I think you mean me, not eprodrom_ :)
#
rhiaro_
... same with pumpio and activitypump
#
rhiaro_
... Valid question, but why make it sound like it's specific to SoLiD?
#
rhiaro_
... sorry I meant cwebber2
#
rhiaro_
cwebber2: curious because I imagine (??) sparql something ..
hhalpin joined the channel
#
rhiaro_
... you end up storing copies of communication
#
hhalpin
waves!
#
rhiaro_
... not sure if you do sparql queries across multiple sites
#
rhiaro_
... I just don't have experience with this type of infrastructure
#
ben_thatmustbeme
Arnaud, in microformats its assumed that data is copied and stored, not constantly pulled
#
rhiaro_
... I think there are issues when a node goes down and someone can't access
#
Zakim
sees elf-pavlik, deiu on the speaker queue
#
eprodrom_
q+
#
Zakim
sees elf-pavlik, deiu, eprodrom_ on the speaker queue
#
hhalpin
An invited observer, Francesca Musiani, who is studying decentralized networking and internet governance as a sociologist at CNRS, has just joined us.
#
rhiaro_
... anyway, not tryign to challenge this, just to see if this is something that SoLiD has
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss capturing ACTIONs
#
Zakim
sees deiu, eprodrom_ on the speaker queue
#
hhalpin
q?
#
Zakim
sees deiu, eprodrom_ on the speaker queue
#
rhiaro_
elf-pavlik: quick comment. I see need that we capture more actions and put thing son wiki page as we explore things
#
rhiaro_
... every meeting every week we stumble on the same things from different directions
#
rhiaro_
... every time there is a problem make an action or put it on the wiki
#
rhiaro_
... it gets lost in the minutes
#
rhiaro_
... indiewebcamp has a good approach, we can take inspiration from that
#
Arnaud
ack deiu
#
Zakim
sees eprodrom_ on the speaker queue
#
rhiaro_
... to build up common understanding of each implementation
#
rhiaro_
deiu: can we make it an open issue? [caching] and think about it later? It affects every proposal
#
rhiaro_
elf-pavlik: someone take action to document issue
#
rhiaro_
sandro: or just raise issue
#
eprodrom_
q?
#
Zakim
sees eprodrom_ on the speaker queue
#
rhiaro_
deiu: please raise issue
#
Arnaud
ack eprodrom_
#
Zakim
sees no one on the speaker queue
#
rhiaro_
eprodrom: I think the reason chris brought it up is that SoLiD is putting a lot of the burden onto the client to make sure that the state of the world is maintained
#
Zakim
sees deiu on the speaker queue
#
rhiaro_
... I know you're trying to concentrate on simple examples
#
sandro
issue: do we need the overall system to be robust even when nodes fail?
#
trackbot
is creating a new ISSUE.
#
trackbot
Created ISSUE-39 - Do we need the overall system to be robust even when nodes fail?. Please complete additional details at <http://www.w3.org/Social/track/issues/39/edit>.
melvster joined the channel
#
rhiaro_
... but I'm more interested in ones that have more complex interactions like follow
#
elf-pavlik
q+ re: running same logic on client and server (more general clear documentation of concerns / responsibilities )
#
Zakim
sees deiu, elf-pavlik on the speaker queue
#
rhiaro_
... would generate a follow activity in my outbox, generate multiple follow activities in multiple inboxes, update my follows list and woudl update someone else's folllowers list
#
rhiaro_
... if any one of those fails, then the state of the world is out of sync
#
rhiaro_
... in pump.io each server is responsible for processing those actions Only one message is transmitted between servers
#
rhiaro_
... if evan on one server follows arnaud on another server the only notification that goes from one to the other is the activity noteification
#
rhiaro_
... the server doesn't try to write to arnaud's collection from even's server
#
Zakim
sees deiu, elf-pavlik on the speaker queue
#
rhiaro_
... that means just re-sending an activity is much easier
#
rhiaro_
... server's responsibility, so much easier and more reliable
#
rhiaro_
... can do retries
#
rhiaro_
... not up the client
#
rhiaro_
Arnaud: solid have more walkthroughs
#
Arnaud
ack deiu
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro_
deiu: SoLiD started as a general platform not social, but we are intereseted in managing notifications
#
sandro
q+ to answer eprodrom_ re consistency
#
Zakim
sees elf-pavlik, sandro on the speaker queue
#
rhiaro_
... We want any app to have a way to notify apps and other servers about changes
#
Zakim
sees elf-pavlik, sandro on the speaker queue
#
Zakim
sees elf-pavlik, sandro, bblfish on the speaker queue
#
rhiaro_
... So AS2 could help us do that
#
rhiaro_
... which means we would have to implement some of this logic in the server
#
eprodrom_
That's great
#
rhiaro_
sandro: different answer
#
Arnaud
ack sandro
#
Zakim
sandro, you wanted to answer eprodrom_ re consistency
#
Zakim
sees elf-pavlik, bblfish on the speaker queue
#
rhiaro_
... about 20 minutes ago henry mentioned idea of generic website
#
cwebber2
so move the side effect / notification stuff off to activitystreams, and the actual store of things on RDF / linked data?
#
rhiaro_
... we haven't implmemented this yet, this is speculative
#
cwebber2
is that what you mean deiu ?
#
rhiaro_
... If I follow someone we change the link to say I follow them, then there's data propagation that doesn't care about the semantics of what happened. All changes are all just data changes
#
rhiaro_
... haven't standardised that yet, but lots of ways to do it
#
rhiaro_
timbl: could be something like thermometer has just taken new temperature reading
#
rhiaro_
sandro: we want this to work for long tail of multi user appications, social is just 1%
#
rhiaro_
... doesn't necessarily mean anything to anyone in this group, but this is the background about why we're designing like this
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss running same logic on client and server (more general clear documentation of concerns / responsibilities )
#
Zakim
sees bblfish on the speaker queue
#
AnnB
q=
#
Zakim
AnnB, if you meant to query the queue, please say 'q?'; if you meant to replace the queue, please say 'queue= ...'
#
AnnB
Q+
#
Zakim
sees bblfish, AnnB on the speaker queue
#
rhiaro_
elf-pavlik: to give our collaboration more structure. We can't say easier/harder/worse/better - it's subjective. We should document possibilities and constraints so everyone knows the options
#
Zakim
sees bblfish, AnnB on the speaker queue
#
rhiaro_
... We need clear way to talk about rendering, content editing, notifications, we need clear vocabulary for this
#
rhiaro_
... Because responsibilities can be handled elsewhere
#
Arnaud
ack AnnB
#
Zakim
sees bblfish on the speaker queue
#
rhiaro_
... Don't make constraints based only on personal use cases, but document these constraints
#
rhiaro_
AnnB: enterprise interest is more about workflow management
#
rhiaro_
... than social
#
rhiaro_
... seems that the linked data stuff which reflects more data changes, like some travel approval comes through or some supply chain change
#
rhiaro_
... in Boeing we transfer every ten minutes as much data as in the library of congress
#
hhalpin
q+
#
Zakim
sees bblfish, hhalpin on the speaker queue
#
rhiaro_
... so the general data stuff is important to me/Boeing
#
hhalpin
?
#
rhiaro_
sandro: the other proposals can handle data flowing as well
#
hhalpin
Are we done with SoLID stories?
#
eprodrom_
hhalpin: I think I keep interrupting
#
hhalpin
Or can we move comparing SoLID to ActivityPump?
#
Arnaud
ack bblfish
#
Zakim
sees hhalpin on the speaker queue
#
rhiaro_
hhalpin: no we just started
#
eprodrom_
Maybe we should let deiu finish
#
hhalpin
q- hhalpin
#
Zakim
sees no one on the speaker queue
#
rhiaro_
bblfish: there's no distinction between client and server. servers can speak to servers to make these updates too, could be in the background
#
rhiaro_
... then we rely on REST for getting and caching resources
#
rhiaro_
... all the infrastructure of the web is there for us
#
rhiaro_
... no duplication of data because all data is at the URI that names it
#
rhiaro_
... so what's missing is for updates to be sent when the content changes before the cache expirey date
#
rhiaro_
... to say please refresh cache. At architectural level that's what missing
#
elf-pavlik
cache includes browser cache, social backend cache etc.
#
AnnB
to expand my point, we are interested in the "social" components, as well as the workflow management -- and we see relationship between the two
#
rhiaro_
Arnaud: break for lunch, continue with user stories after lunch
#
rhiaro_
hhalpin: some AC people have to leave at like 3?
#
rhiaro_
sandro: at 5, when the meeting is over
#
rhiaro_
AnnB: we're going straight from here
#
rhiaro_
probably doesn't need to scribe this
#
eprodrom_
rhiaro_: actually the schedule stuff is very helpful
#
eprodrom_
For those of us on the phone
#
eprodrom_
Since it's mostly inaudible
#
rhiaro_
eprodrom_: nothing new, just that people don't need to leave early after all
#
eprodrom_
rhiaro_: thanks
#
eprodrom_
So breaking for lunch now?
#
rhiaro_
hhalpin: who wants a TLS session after SoLiD
#
rhiaro_
epodrom_: yes I think so
#
Zakim
sees no one on the speaker queue
#
eprodrom_
Thank you
#
eprodrom_
Sorry to be so needy :)
#
rhiaro_
hhalpin: if people want to fit that in, we're in INRIA so we could have a TLS session
#
rhiaro_
... but it's out of scope for group
#
rhiaro_
AnnB: let's not get distracted
#
rhiaro_
Arnaud: we should go through our agenda
#
rhiaro_
... two more stories for SoLiD
#
rhiaro_
... general discussion
#
rhiaro_
... comparison
#
rhiaro_
... once we've seen three different proposals, see what the differences are
#
rhiaro_
... then there are demos
#
rhiaro_
melvster has short demos, for more generic use cases. deiu has a specific demo
#
rhiaro_
AnnB: TLS thing feels too much distraction
#
rhiaro_
... Didn't know it came up
#
rhiaro_
Arnaud: proposal is that once we're done with agenda, those interested can have security discussion with INRIA
#
elf-pavlik
+1 TLS after AC participants leave
#
cwebber2
hey also
#
rhiaro_
... *now* breaking for lunch
#
cwebber2
rhiaro++ for great scribing :)
#
Loqi
rhiaro has 74 karma
#
aaronpk
rhiaro++
#
eprodrom_
Thanks for scribing rhiaro_
#
Loqi
rhiaro has 75 karma
#
eprodrom_
rhiaro++
#
Loqi
rhiaro has 76 karma
#
cwebber2
rhiaro is a karma accumulator
#
rhiaro_
Lunch 1 hour
#
rhiaro_
back at quarter past
#
Zakim
-ben_thatmustbeme
#
Zakim
-eprodrom
#
rhiaro
For anyone not physically present, we haven't made it back from lunch yet
#
cwebber2
rhiaro: ok thx
tantek joined the channel
#
eprodrom_
rhiaro: thanks
#
eprodrom_
I like that phrasing
#
eprodrom_
It makes it sound like we're visitors from the spirit realm
#
Zakim
+ben_thatmustbeme
#
ben_thatmustbeme
Zkim, mute me
#
ben_thatmustbeme
Zakim, mute me
#
Zakim
ben_thatmustbeme should now be muted
#
eprodrom
Are we live again?
#
ben_thatmustbeme
i hear nothing
#
ben_thatmustbeme
i just jumped on to see
#
tantek
greetings - administrivia request: I'd like to cancel next week's telcon (and suggest adopting a culture of skipping the week after a f2f)
#
ben_thatmustbeme
eprodrom, there is talking again
#
tantek
Arnaud, eprodrom, hhalpin ^^^
#
Arnaud
tantek: what's the rationale for that?
#
rhiaro_
People are just drifting back in
#
rhiaro_
most people not back yet
#
tantek
Arnaud: it's a request, and typical in many WGs. Allows for more time for post-f2f async follow-ups (which there tend to be more of) before the next telcon.
#
Zakim
-cwebber2
#
cwebber2
I didn't hear anything, but I am redialing
#
cwebber2
could have been my connection
#
tantek
Also good to acknowledge that sometimes a f2f can be tiring and giving people a week to "recover" is good too.
#
Arnaud
I'm open to it but not in favor of making it a rule
#
tantek
I don't think it's a rule in any WG - more of a custom.
#
tantek
So I'm proposing it as a one-off for next week
#
tantek
then we can get feedback from WG members about were they ok with it, appreciated it, or would have preferred having a telcon.
#
Zakim
+??P0
#
Arnaud
"adopting a culture of skipping the week after a f2f" sounded like making it a rule/policy
#
cwebber2
Zakim, ??P0 is me
#
Zakim
+cwebber2; got it
#
cwebber2
I can hear again
#
tantek
Arnaud: the *and* was intended as a two part proposal
#
ben_thatmustbeme
cwebber2, did you lean on the keypad. :P
#
tantek
I wanted to provide my longerterm intentions
#
cwebber2
ben_thatmustbeme: no?
#
ben_thatmustbeme
cwebber2 haha, :P
#
ben_thatmustbeme
cwebber2, I also just force myself to use /me so its not minuted at all
#
Zakim
+eprodrom
#
cwebber2
(setq erc-pcomplete-nick-postfix ",")
#
cwebber2
there we go
#
eprodrom
Cool
#
eprodrom
It's almost worse to hear the telecon at this point
#
eprodrom
IMTS the audio
#
eprodrom
Mostly getting rough impressions
#
sandro
hm? How's the audio? There are multiple conversations in the room as we haven't started yet.
#
eprodrom
Ah, right
#
eprodrom
sandro, it's pretty bad right now
#
eprodrom
That's great
#
eprodrom
I'm sorry to be so demanding about the phone
#
tantek
I am still in a separate meeting and cannot call in.
#
eprodrom
It's a lot easier when someone is scribing
#
Arnaud
fyi: we had lunch at a restaurant nearby that was pretty crowded and it took longer to get served than we would have liked
#
Arnaud
people are still slowing coming back
#
cwebber2
eprodrom, someone needs to scribe the ambient smalltalk! ;)
#
eprodrom
No problem whatsoever
#
Arnaud
s/slowing/slowly/
#
tantek
Arnaud: PROPOSAL: Skip next week's telcon as being the week after a f2f.
#
Arnaud
personally I think we still have issues on AS we could talk about on the telecon
#
tantek
we will continue to do so, and I think they could wait til the next telcon
#
cwebber2
I'm not against the telecon :) I just wouldn't mind the break!
#
ben_thatmustbeme
thinks france has 18 hour days... an hour for lunch is an hour and a half, 8 hours of sleep is 9 and a half ;P
#
tantek
cwebber2: agreed. We could use the break after a f2f.
#
sandro
scribe: sandro
#
sandro
scribenick: sandro
#
ben_thatmustbeme
Before we start do we want to bring up tantek's proposal?
#
sandro
which is, in a few words?
#
Arnaud
I'd rather wait to see where we end up
#
tantek
sandro, PROPOSAL: Skip next week's telcon as being the week after a f2f.
#
tantek
Arnaud, is that a -1 or a 0?
#
Arnaud
this is: later :)
#
sandro
tantek, I suggest we use it as an informal recap of the F2F, esp for people who didnt attend
#
ben_thatmustbeme
tantek, i think thats a postpone vote
#
cwebber2
informal recap could be ok
#
eprodrom
Sorry to say, we're behind on our deliverables and I don't think it makes sense to take a week off
#
Zakim
sees no one on the speaker queue
#
tantek
I don't think that's a good use of sync time - recaps belong in summaries on a URL.
#
sandro
topic: solid walkthrough: profile management
#
Arnaud
I'm with evan
#
sandro
tantek, in my experience, these recaps are mostly discussion
#
tantek
eprodrom, we're only "behind" because the dates set were unreasonable and without explicit methodology as to *how* they were going to be met.
#
tantek
so such "we're behind" justification is a bit hollow
#
elf-pavlik
we *all* try following deiu demo now!
#
sandro
deiu: I'm showing my profile, using an app, which gathers the data from multiple sources, some of which are public and some are restricted-access.
#
eprodrom
tantek, but that's what people who run late always say
#
tantek
eprodrom: that's a tautology and false
#
tantek
I stated from the beginning that the proposed schedules were unrealistic and should be dropped.
#
eprodrom
Fair enough
#
sandro
deiu: I'm adding a phone number, and the apps asks which place I want to put it -- with different associated access control
#
tantek
I don't think such top-down schedules are a good way to run or motivate a working group
#
melvster
slaps KevinMarks around a bit with a large fishbot
AnnB joined the channel
#
tantek
melvster huh?
#
sandro
deiu: See how in the PUBLIC version of my profile, my phone numbers don't appear
#
cwebber2
melvster, are you running mIRC on windows95? ;)
#
sandro
deiu: that is, when I'm not logged in
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
melvster
misclick
#
kaepora
No, you can't use a#b to scroll to a location in a JSON! I just checked! :P
#
sandro
deiu: the app pulls in the profile elements from different places
#
cwebber2
I do wish I could watch this presentation... I suppose such things are the risks you take when you attend remotely tho :)
#
elf-pavlik
kaepora++
#
Loqi
kaepora has 2 karma
#
eprodrom
cwebber2, you get what you pay for
#
sandro
deiu: (shows network trace, where some profiles give a 403 because he's not allowed access to those, with this identity)
#
Zakim
sees eprodrom on the speaker queue
#
Arnaud
ack eprodrom
#
Zakim
sees no one on the speaker queue
#
sandro
deiu: (as intended)
#
sandro
eprodrom: The user-profile --- you use schema.org, foaf, vcard, ... why didn't you use AS2.0?
#
sandro
deiu: This app is older than AS 2.0
#
aaronpk
I don't know if this is going to work, but it might... https://talky.io/socialwg
#
tantek
not older than vcard nor hCard :P
#
sandro
eprodrom: API surface? The client needs to pull a bunch of different data from different URLs
#
sandro
deiu: Yes
#
sandro
eprodrom: To document this API for a client developer, I'd need to document all these URLs?
#
sandro
deiu: No, it's just following links.
#
AnnB
aaronpk, I thought they said yesterday that the port (?) we need for talky is blocked at the INRIA firewall
#
aaronpk
I'm on a VPN
#
sandro
deiu: The API is just doing GETs on URLs of the resources of interest, following links. HATEOAS
hhalpin joined the channel
#
sandro
tantek, it uses vcard
#
AnnB
aha
#
hhalpin
the rdf vcard vocabulary, which I think is compatbile with hcard
#
AnnB
I get to a splash screen, and no further
#
eprodrom
vcard++
#
Loqi
vcard has 1 karma
#
sandro
timbl: Code can following multiple links, like the older version of the vocab and the newer version. So one could convert to AS2.0 gradually, with supporting the old vocabs, too.
pfefferle joined the channel
#
sandro
deiu: To build on that example, using tabulator
#
Zakim
-eprodrom
#
ben_thatmustbeme
but i can hear
#
elf-pavlik
Zakim, who's on the call?
#
Zakim
sees on the phone: INRIA, ben_thatmustbeme (muted), cwebber2
#
sandro
eprodrom, you calling back?
#
eprodrom
Sorry, I'm off the phone, trying to work out talky.io stuff
#
cwebber2
eprodrom's still on talky at least ;)
#
eprodrom
It's actually much better than the phone bridge
#
cwebber2
yeah it's not bad
#
AnnB
cool beans
#
Zakim
+??P2
#
elf-pavlik
kaepora: can you please share link to resource saying that you can't do fragment URIs in JSON? a#b ?
#
sandro
deiu: I'm using tabulator as a generic skin to render the RDF data in my profile as HTML so it can display in the browser
#
aaronpk
whoever is the other black screen on talky, can you mute your video? it will free up bandwidth
#
elf-pavlik
q+ re: note on 'server' and 'client' side rendering e.g. JSON-LD -> RDFa https://github.com/w3c-social/social-arch/issues/1
#
Zakim
sees elf-pavlik on the speaker queue
#
sandro
deiu: I can add additional data to my profile, using a vocabulary I make up, for "hometown"
#
eprodrom
aaronpk: I just disabled video for that reason
#
Zakim
-ben_thatmustbeme
#
sandro
deiu: I just defined a new property, "hometown"
#
sandro
deiu: Now tabulator lets me set values for it
#
sandro
deiu: So *without programming* I was able to define a new profile property, and then apps allowed users to add it.
#
ben_thatmustbeme
wow, talky is way better than phone
#
eprodrom
ben_thatmustbeme surprisingly so
#
AnnB
that's great to learn
#
AnnB
those who were remote at the last TPAC said same thing
#
sandro
elf-pavlik: something about templates
#
AnnB
really surprising, since the audio is just coming through the webcam
#
ben_thatmustbeme
eprodrom, may be more to do with microphone quality than anything
#
sandro
deiu: Lea Verou of CSS WG is doing a PhD (at MIT) on html page templates from data
#
ben_thatmustbeme
also can compress the audio first, whereas phone doesn't
#
Zakim
-cwebber2
#
eprodrom
ben_thatmustbeme it felt like there was some kind of bursting going on
#
ben_thatmustbeme
eprodrom, yeah, the audio does sound more... muddled, its definitely not as clear but it doesn't cut in and out
#
aaronpk
yeah sorry the mic is pointed the opposite direction of the people so you can see the screen
#
sandro
tim: there are levels of customizablity, default form, styled form, js-controlled form, etc
#
Zakim
sees no one on the speaker queue
#
Arnaud
ack elf-pavlik
#
Zakim
sees no one on the speaker queue
#
cwebber2
sorry I seem to be having connection issues on my LAN
#
elf-pavlik
Zakim, who's on the call?
#
Zakim
sees on the phone: INRIA, ??P2
#
ben_thatmustbeme
cwebber2, is that you?
bblfish joined the channel
#
elf-pavlik
who's on the phone?
#
elf-pavlik
deiu: can you please link to more info on what you say happening at MIT in this gh-issue? https://github.com/w3c-social/social-arch/issues/1
#
kaepora
elf-pavlik: I just created a big JSON fle and tried it locally
#
deiu
I'm not sure I have links for it
#
kaepora
elf-pavlik: I am sure you can replicate the results on your browser :-)
#
eprodrom
Who is scribing?
#
ben_thatmustbeme
i believe sandro was supposed to be scribe
#
Zakim
sees no one on the speaker queue
#
sandro
topic: Henry does Solid walkthrough on Private SHaring
#
sandro
bblfish: Using webid-tls for access control, in this example
cwebber2` joined the channel
#
ben_thatmustbeme
ouch, when audio hiccups on talky it gets quite interesting though
#
sandro
bblfish: So assume Ian has a WebID (a URI that identifies as him)
#
sandro
bblfish: I GET Ian's "card"
#
sandro
bblfish: link "acl" (not registed with IANA)
cwebber2 joined the channel
#
sandro
.. goes through various headers, eg for CORS
#
elf-pavlik
issue including topic of rel="acl" registration https://github.com/linkeddata/SoLiD/issues/10
#
trackbot
doesn't understand that ISSUE command.
#
sandro
.. in this example I used turtle instead of JSON-LD, just because it was a little easier for me
#
cwebber2
what's the talky url again?
#
sandro
.. shows Ian's certificate
#
cwebber2
thx ben_thatmustbeme
#
sandro
.. using cert.pem for curl demo (browser does this automatically)
#
tantek
elf-pavlik: don't make an issue of rel=acl registration - just go add it to the rel registry yourself per http://microformats.org/wiki/existing-rel-values
#
sandro
s/ik:/ik,/
#
elf-pavlik
tantek: i see not problem with you having your interpretation on that, but please note that other people interpret it differently
#
sandro
bblfish: Link header to acl resource
#
sandro
.. we GET it
#
cwebber2
we GET it, man!
#
sandro
s/tek:/tek,/
#
tantek
elf-pavlik: not an interpretation - just a suggestion to you to help you take a productive step forward
#
sandro
ha ha ha
#
tantek
s/k:/k,
#
sandro
s/lik:/lik,/
#
elf-pavlik
tantek we had discussion with timbl over lunch also about that and hopefully W3C can engage in resolving that issue, also in a way which provides full URI for registered link relations
#
sandro
bblfish: do a PATCH to add the new bit of access control
#
sandro
.. so the client software just allowed jane access
#
ben_thatmustbeme
cwebber, is your video/audio muted. it seems like its trying to load a black screen from here
#
sandro
.. send notice to Jane
#
elf-pavlik
which for me can result in blessing microformats.org , as long as we can all agree no resolution for that
#
Zakim
+??P4
#
ben_thatmustbeme
cwebber2 nevermind ;P
#
cwebber2
Zakim, ??P4 is me
#
Zakim
+cwebber2; got it
#
cwebber2
ben_thatmustbeme: intentionally muted
#
elf-pavlik
we including IETF / IANA folks
#
cwebber2
I got 3 hours of sleep between prepping user story details and waking up for this
#
tantek
elf-pavlik W3C and WHATWG have already done so - in that limited capacity, so there is no further blessing that is being done.
#
cwebber2
I don't want to appear on webcam ;p
#
sandro
.. do a GET on her profile
#
cwebber2
but i'm on SIP now anyway
#
ben_thatmustbeme
yes, i know, but it looked like the camera was just covered, not muted in talky
#
aaronpk
sorry my computer seems to be having network issues, everything is really slow
#
sandro
.. In the example, I show a proposed extension to GET, to include a query, being discussed in HTTP WG
#
eprodrom
Thanks aaronpk
#
Zakim
+ben_thatmustbeme
#
ben_thatmustbeme
Zakim, mute me
#
Zakim
ben_thatmustbeme should now be muted
#
ben_thatmustbeme
yeah, i was losing talky sadly
#
AnnB
aaronpk, should I try hosting talky?
#
aaronpk
AnnB: not sure it'll make a difference
#
sandro
sandro: This is off topic --- we don't need queries to make this user story work
#
AnnB
k
#
sandro
bblfish: okay
#
aaronpk
wishes that whole thing was minuted
#
sandro
bblfish: We get back a "ping" endpoint
#
AnnB
which bit are you missing, aaronpk?
#
sandro
bblfish: and you POST to that endpoint. *or* or use webmention
#
eprodrom
I think it's jumping the gun to say this is definitely WebMention
#
AnnB
more than what sandro is scribing?
#
aaronpk
AnnB nevermind
#
sandro
bblfish: I haven't yet looked at how webmention works
#
elf-pavlik
tantek so *maybe* we just need URIs for link relations in microformats.org namespace
#
sandro
bblfish: the resource you POST to with ping should have ACLs such that you can post (append) but not read, except maybe you can edit the things you created.
tommorris_ joined the channel
#
sandro
elf-pavlik or a w3.org ns
#
elf-pavlik
+1 w3.org namespace what timbl proposed
#
tantek
elf-pavlik we have URLs for many link relations in microformats.org "space" already at things like http://microformats.org/wiki/rel-me etc. and many more linked from the existing-rel-values page
#
tantek
and that's where they're maintained with a community maintaining them
#
sandro
bblfish: shows diagram, explaining bits.....
#
aaronpk
diagram has some typos apparently
#
elf-pavlik
tantek @prefix rel: http://microformats.org/wiki/rel- might work ...
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
tantek
I'm against putting things in a space that's not actively community maintained (in my experience, W3C namespace URIs are not community maintained at all, and often end up out of date)
#
tantek
elf-pavlik interesting. I had never considered that.
#
Arnaud
ack eprodrom
#
Zakim
sees no one on the speaker queue
#
elf-pavlik
can *community* setup content negotiation or at least embed <scrip> tags for text/turtle and application/ld+json if we find need for it?
hhalpin_ joined the channel
#
ben_thatmustbeme
tantek, elf-pavlik that is a pretty interesting idea. I could certainly see that making sense
#
elf-pavlik
tantek i hope you, timbl, mnot and others can disucss it!
#
sandro
eprodrom: I like this flow, it's a lot like activity pump, except the client is responsible for making that ping (where in AP it'd be the server). With fanout issues, it's probably better handled by server.
#
elf-pavlik
q+ re: running bots on server which do client logic ...
#
Zakim
sees elf-pavlik on the speaker queue
#
hhalpin_
+1 just fixing a URI namespace for microformats
#
sandro
bblfish: Yeah, it could be the server, or some non-client-agent. Although if we want a dumb server, we need and intelligent client.
#
sandro
eprodrom: LDP as stupid as possible? (stupid is good here. not business intelligence.)
#
deiu
LDP doesn't do much by design
#
Zakim
sees elf-pavlik on the speaker queue
#
hhalpin_
At this point I would keep the URIs at microformats.org rather than w3.org
#
hhalpin_
q+
#
Zakim
sees elf-pavlik, hhalpin_ on the speaker queue
#
eprodrom
LDP + social stuff
#
sandro
sandro: as simple as possible, but no simpler
#
deiu
exaxctly
#
deiu
s/exaxctly/exactly
#
sandro
timbl: as long as the added features are application-independent
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss running bots on server which do client logic ...
#
Zakim
sees hhalpin_ on the speaker queue
#
sandro
elf-pavlik: different elements have different responsibilityies... Could have a daemon which does stuff.
#
deiu
elf-pavlik++ (similar to Apache modules)
#
Loqi
elf-pavlik has 24 karma
#
sandro
sandro: it's still black and white to me --- certain things are the responsibility of the client or not.
#
sandro
Arnaud: solid (right now) puts a lot of responsibility on the client
#
Zakim
sees hhalpin_, deiu on the speaker queue
#
Arnaud
ack hhalpin_
#
Zakim
sees deiu on the speaker queue
#
eprodrom
Aha!
#
sandro
hhalpin: the LDP model is interesting, similar to unhosted in some ways, dependent on access control and auth, maybe
#
deiu
disagrees
#
eprodrom
Interesting
#
ben_thatmustbeme
deiu /me lines are not minuted, if you want that on the record, don't use /me
#
sandro
hhalpin: If you had a server, please store any file, it's a problem
#
deiu
I disagree with hhalpin_
#
akuckartz
hhalpin mentioned https://unhosted.org/ and briefly compared it to LDP
#
deiu
I didn't want to polute the logs
#
sandro
sandro: that's exactly the same with ActivityPump and MicroPub. You still need some identity and auth mechanism.
#
ben_thatmustbeme
deiu, understandable, but i feel like disagreement, is important to capture
#
sandro
hhalpin: I think we should talk about TLS later today
#
deiu
you're right
#
sandro
sandro: I think they could each use each other's auth system
#
sandro
aaronpk: I think the access control is really similar, and orthogonal to this spec
#
Arnaud
ack deiu
#
Zakim
sees no one on the speaker queue
#
sandro
Arnaud: any more about solid per se, before we get to overall similarities and differences
#
sandro
deiu: SoLiD is relatively new
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
AnnB
are melvster's demos related? (that we have not yet seen)
#
deiu
AnnB, maybe we can do those demos in the demo session
#
eprodrom
q-
#
Zakim
sees no one on the speaker queue
#
sandro
sandro: The LDP parts of SoLiD are stable and have lots of implementations, the other bits are very much subject to change and improvement
#
sandro
topic: Comparison of Proposals
#
sandro
Arnaud: maybe self-criticism
#
sandro
akuckartz: Maybe instead -- say what's good about the others
#
deiu
for the minutes..."What a great idea"
#
ben_thatmustbeme
if we can get everyone authenticating to each other, that would be a really big step forward
#
deiu
ben_thatmustbeme, we can do that in a different WG though
#
deiu
as it doesn't only apply to Social
#
rhiaro_
sandro: want me to take over minuting?
#
sandro
that'd be great
#
rhiaro_
scribenick: rhiaro_
#
ben_thatmustbeme
deiu, true, I don't mean for the WG to deal with that, the socialwg is specifically avoiding choosing auth mechanism. but if we can get working those developing in the group i think will find it quite useful
#
rhiaro_
aaronpk: micropub is only for writing. Complete picture includes webmention, PuSH and microformats
#
deiu
ben_thatmustbeme, I agree
#
rhiaro_
... We have lots working reasonably well, where there are holes are getting into propagating information about state changes of objects deep in the tree of comment threads or eg. likes on comments
#
rhiaro_
... we haven't built that stuff yet
#
eprodrom
aaronpk I think also access to the social graph (who follows Aaron? Who does Aaron follow?)
#
rhiaro_
... which is why I'm not sure about it
#
rhiaro_
... we want to figure out a better solution for that
#
eprodrom
And CRUD on profiles
#
elf-pavlik
eprodrom: we do *self* criticism :)
#
rhiaro_
... the way AS handles that is entirely reasonable, with activities essentially being a changelog of everything that happens
#
rhiaro_
... you can sync systems using changelog
#
eprodrom
elf-pavlik thanks very much
#
rhiaro_
... the way I figured this out was going through the story and seeing the edge cases. Seeing at a point in the story there isn't a solid answer
#
rhiaro_
... whereas just glancing at the story when we were voting it looked like we could do all of it
#
rhiaro_
... So that was the big one.
#
ben_thatmustbeme
eprodrom, thats a matter of publishing that information as a xfn page really. I plan to start doing that soon... following is easy, followers not so easy unless following notifies
#
eprodrom
ben_thatmustbeme yes
#
rhiaro_
... The whole formencoding and namespacing of command params with mp- in micropub works for all use cases I've encountered, but I can see where ther eare limitations, we just haven't hit them in practice yet
#
rhiaro_
... maybe it's better to find a solution where we don't have those limitations in the first place
#
deiu
thinks rhiaro_ needs more karma for her minutes
#
rhiaro_
Arnaud: any reactions?
#
deiu
rhiaro_++
#
Loqi
rhiaro_ has 77 karma
#
eprodrom
elf-pavlik am I allowed to respond now?
#
ben_thatmustbeme
aaronpk, i would say i started to hit at least annoyances with it for tagging people in locations in a photo
#
rhiaro_
deiu: karma to rhiaro without _ please ;)
#
deiu
rhiaro++
#
Loqi
rhiaro has 78 karma
#
elf-pavlik
eprodrom, ActivityPump time now so your turn -- Tsyesika speaks ATM
#
rhiaro_
Tsyesika: one thing micropub talked about is ability to get source, eg. markdown rather than html
#
ben_thatmustbeme
rhiaro_, loqi knows to ignore _ at the end of a name
#
eprodrom
elf-pavlik ah, maybe my sarcasm wasn't clear enough
#
rhiaro_
... I'd love to introduce ability to get that source
#
aaronpk
ben_thatmustbeme: locations of person tags wasn't part of the story so I didn't include an example, but yes that's true
#
eprodrom
elf-pavlik I don't like being told to shut up
#
elf-pavlik
eprodrom on IRC things don't go through that well + me not very english ;)
#
rhiaro_
... So ActivityPump doesn't have that
#
eprodrom
Undersood
#
eprodrom
s/Undersood/Understood/
#
rhiaro_
... Other thing is no ability to have multiple file uploads
#
rhiaro_
... And multiple steps to upload one file
#
rhiaro_
... [plus metadata]
#
elf-pavlik
Zakim, who's on the phone?
#
Zakim
sees on the phone: INRIA, ??P2, cwebber2, ben_thatmustbeme (muted)
#
rhiaro_
... One of the biggest problems I have as a developer for activitypump is that audience targeting is always on the activity rather than the object
#
rhiaro_
... but in reality when you're checking someone's ability to access an object when they dereference it, you really need the audience targeting on the object
#
rhiaro_
... it's more useful on the object than the activity. Youc an get around it with some caching, but it's not great
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
rhiaro_
... has been pointed out that there is duplication regarding post and share activities with objects, but not sure how to get around that without fundamentally changing activitystreams - which I'm not against, but might bring other problems
#
rhiaro_
... Plus discoverability hasn't been cemented yet
#
cwebber2
I think having a "source" field on notes and etc would be really nice
#
rhiaro_
various people: helping ann with whiteboard
#
cwebber2
would make editing my posts a lot easier when using pump clients that use markdown
#
rhiaro_
Arnaud: anyone?
#
Arnaud
ack eprodrom
#
Zakim
sees no one on the speaker queue
#
rhiaro_
eprodrom: as part of ActivityPump spec (Jessica did a great job), I would point out that in the federation aspect it calls for using the NOTIFY verb
#
rhiaro_
... I'd really rather see that as a webhook style description mechanism
#
bblfish
Is there an HTTP NOTIFY verb?
#
Zakim
sees cwebber on the speaker queue
#
rhiaro_
... Second, it has a number of activity types that are called out for how they change the state of the world
#
rhiaro_
... There should be some finer detail on what exactly happens when you unfollow, when there's a like, etc
#
rhiaro_
... Finally, to go back through and review the user stories and make sure the examples that we have (supported by pumpio)
#
rhiaro_
Arnaud: more interested in big gaps that need filling
#
rhiaro_
... every technology can have open issues, but right nown we're more interested in bigger story
#
Arnaud
ack cwebber2
#
Zakim
sees cwebber on the speaker queue
#
sandro
bblfish, only if you squint
#
Arnaud
ack cwebber
#
Zakim
sees no one on the speaker queue
#
rhiaro_
cwebber2: I agree with evan and jessica
#
rhiaro_
... One thing I admire about micropub is having a wide variety of implementations
#
eprodrom
That's the only reference I can find
#
eprodrom
oshepherd probably has more info
#
rhiaro_
... we have a good variety of implementations of clients, but for servers there are only pump.io and mediagoblin, mediagoblin only implements half the pump spec
#
rhiaro_
... with activitypump I'd like to see a spec that people *can* implement on the server side
#
eprodrom
cwebber2++
#
Loqi
cwebber2 has 29 karma
#
Zakim
sees no one on the speaker queue
#
eprodrom
q-
#
Zakim
sees no one on the speaker queue
#
rhiaro_
Tsyesika: to follow on, at lunch we [rhiaro, aaronpk, arnaud] talked about how the indieweb community have split their specs up, and it feels easier to implement
#
rhiaro_
aaronpk: it lets you make incremental progress
#
rhiaro_
Tsyesika: with activitypump it's like you're either compliant with the spec or not, adn it's a lot of work to get that done
#
rhiaro_
... someone coming along wanting to make their site activitypump compliant would have a much harder time than getting started with indieweb
#
rhiaro_
... I don't have it on my personal site
#
rhiaro_
hhalpin: can you explain why?
#
eprodrom
I don't think it's a "personal site" kind of API
#
eprodrom
It's a "social network engine" API
#
rhiaro_
Tsyesika: it's one big spec and it can takek time to implement it all, and it's changing a lot. It's a big investment to do it all at once, then change it
#
aaronpk
eprodrom, you're saying my personal website can't participate in a social network?
#
rhiaro_
arnaud: something fundamental that makes it impossible to do it this way in activitypump?
#
rhiaro_
Tsyesika: no, we can break it down
#
ben_thatmustbeme
it has to be able to, a personal site is a network of 1
#
rhiaro_
... also NOTIFY is probably going to be dropped
#
eprodrom
aaronpk, nope
#
rhiaro_
bblfish: don't want to hear sandro speak, don't need to push him to be negative about SoLiD. It means more if I'm negative, as a big defender
#
cwebber2
eprodrom, well, I think maybe with sufficient library'ification of activitypump
#
rhiaro_
... Implementing is very important, that's where indieweb community is great
#
cwebber2
we can hit a lot more of the "easy to implement" side of things
#
eprodrom
cwebber2, right
#
rhiaro_
... SoLiD have to learn to create communities too
#
Tsyesika
eprodrom: i agree it's more oreiented to social network software and being a platform and such but also i think it's useful to be able to implement parts of the spec
#
eprodrom
Tsyesika, sure, but I'd have a hard time dividing it into pieces
#
rhiaro_
... Also AS and pump work is interesting, seems like there can be a mapping to solid
#
cwebber2
activitypump is not quite SSL in difficulty to implement, but similarly, having some good libraries like that can make things much nicer
#
eprodrom
Also, I think the kind of person who'd be implementing would be doing it for e.g. Diaspora
#
aaronpk
cwebber2, but you also have to make it really easy for other people to create libraries because you're not gonna want ot write libraries in every language
#
cwebber2
aaronpk, I agree
#
deiu
q+ to bash SoLiD a bit
#
Zakim
sees deiu on the speaker queue
#
Tsyesika
eprodrom: i agree, it'd be tricky, i'm not sure how i'd do it to be honest but it's something i like from the indieweb and it's maybe a good idea to look into if here is anything we could do
#
Tsyesika
but yes we want this to work for the diasporas, facebooks, etc. of the world
#
cwebber2
aaronpk, I think that the activitypump spec is quite implementable as a library, but it also requires that we put more code into it
#
rhiaro_
... LDP is harder to implement
#
rhiaro_
... Once the server is done, it's done for everybody
#
cwebber2
aaronpk, another thing is until MediaGoblin implemented the pump api, nobody else had done that work. I think we should see if we can share our experieences to make it clearer to implement
#
rhiaro_
... on the client side there's lots of JS and rdf libraries needed
#
rhiaro_
... it's more theoretical infrastructure
#
aaronpk
cwebber2, eprodrom, Tsyesika, I would be interested to see what activitypump would look like broken out into small implementable steps, like what if someone could just create their inbox but wait to implement an outbox
#
sandro
is dying to hear Tim take a turn at this. :-)
#
cwebber2
I'm interested in seeing what that would look like!
#
Tsyesika
i'm not sure how it'd look but i think it'd be good to look into
#
cwebber2
aaronpk ^^
#
rhiaro_
... Could do work on notifications that people want in social communities
#
eprodrom
Yeah, so, there are ~5 endpoints defined in the activity pump doc
#
eprodrom
Maybe more if you count CRUD on user profiles and created objects
#
eprodrom
That feels pretty minimal
#
rhiaro_
... To give more responsibility to the server
#
rhiaro_
... Let server act as a client
#
cwebber2
eprodrom, also I'd say that a lot of the work Tsyesika is spending time on is changing the database to support migrations
#
Arnaud
ack deiu
#
Zakim
deiu, you wanted to bash SoLiD a bit
#
cwebber2
and I'm not sure how you can get around that complication
#
Zakim
sees no one on the speaker queue
#
aaronpk
eprodrom, i would feel better about that if it has been demonstrated that it's pretty mininal
#
cwebber2
to support federation
#
Tsyesika
cwebber2: sure which isn't nesseserly anything to do with specs tho
#
Tsyesika
it's just legancy infrastructure
#
cwebber2
however!
#
rhiaro_
deiu: SoLiD by definition is very generic
#
cwebber2
we *can* make it easier
#
eprodrom
Migrating from one server to another?
#
cwebber2
by sharing information on how we got there
#
eprodrom
That's such a hard problem
#
cwebber2
eprodrom, no, not that
#
rhiaro_
... it has a different view of what social means to indieweb and activitypump
#
rhiaro_
... especially in terms of notifications
#
cwebber2
eprodrom, migrations as in "sql schema migrations"
#
Tsyesika
eprodrom: moving a database from a design not intended for federation
#
eprodrom
Right
#
cwebber2
upgrading the table structure
#
Tsyesika
to a database which is
#
rhiaro_
... it's less focused on this definition of social, it's a bit difficult to implement the same user stories
#
rhiaro_
... This translates in a lot of clientside javascript
#
rhiaro_
... as opposed to indieweb where a lot of logic happens in the server
#
rhiaro_
... pages clients see are less heavy
#
rhiaro_
... for SoLiD there are bandwidth requirements you have to meet in the client
#
rhiaro_
... there's also this high-percieved learning curve
#
rhiaro_
... develoeprs are used to implementing apis, whereas we have a different way of managing data
#
Tsyesika
eprodrom: i'm going to try and find some to implement a spec complient version of activitypump and i'll see what the pain points are
#
rhiaro_
... I think that's the biggest difference
#
rhiaro_
... I think it's a perceived learning curve, it's not that big a deal
#
cwebber2
eprodrom, anyway, I think some documents showing how to plan your database from day 1 (the easiest route!) or how to upgrade an existing system will help other developers with adoption
#
eprodrom
Tsyesika maybe we could work on it together
#
eprodrom
Tsyesika I want to try a new Go project
#
rhiaro_
arnaud: this touches the point about whether you post the activity and the server creates the post or vice versa
#
eprodrom
Or if you have another language you'd like to try
#
rhiaro_
... an activity or object centric view of the world
#
cwebber2
eprodrom, let's write it in guile ;)
#
rhiaro_
deiu: we have a data view of the world
#
Tsyesika
just to clarify i said you can use CRUD on existing objects nt to create new objects
#
rhiaro_
arnaud: more generic
#
eprodrom
cwebber2 cool here
#
cwebber2
would actually like that but knows that probably not many others will be as into it?
#
rhiaro_
deiu: on the plus side, if tomorrow there's going to be a completely different working group with different use cases, we might be able to help them as well
#
rhiaro_
arnaud: it's more flexible in that respect
#
Tsyesika
eprodrom: sure i don't have any Go experiance
#
eprodrom
Tsyesika me either
#
cwebber2
eprodrom, Tsyesika is also learning scheme
#
eprodrom
Oh, cool
#
rhiaro_
bblfish: I think we've got a set of communities that represent a learning curve that come to a full blow generalisable version of SoLiD (?)
#
eprodrom
We could do it in Scheme
#
cwebber2
now we can make a truly ivory tower version of federation ;)
#
Tsyesika
i've played with it on the side :)
#
rhiaro_
... we're all doign prety much the same thing
#
Tsyesika
"learning" is maybe too stronger word
#
deiu
eprodrom, one of our Solid servers is written in Go
#
rhiaro_
... requirements seem to be on one end of the spectrum, minimal technology, to the other side with maximal generality
#
eprodrom
deiu, cool
#
rhiaro_
... we can all learn from each other
#
cwebber2
I think this has bee a good exercise, sandro !
#
Zakim
sees akuckartz on the speaker queue
#
rhiaro_
AnnB: tim or sandro? or melster?
#
deiu
eprodrom, I wonder if you could fork it to add the pump API
#
rhiaro_
s/melster/melvster
#
eprodrom
deiu, it would be an interesting exercise
#
Zakim
sees akuckartz on the speaker queue
#
rhiaro_
melvster: I was a semantic web skeptic
#
rhiaro_
... perceived learning curve as andrei mentioned
#
rhiaro_
... spent a year looking at it, adn by the end realised I could have learned it in less time, it's conceptually quite simple
#
rhiaro_
AnnB: Negative comment on solid?
#
aaronpk
Tsyesika, cwebber2, how about building an activitypump api and launch on your own websites? :)
#
elf-pavlik
q+ re: to propose discussion about evolution of the whole system, extensible design and backward/forward compatibility
#
Zakim
sees akuckartz, re: on the speaker queue
#
rhiaro_
melvster: compared to indieweb for example or ostatus, activitypump ecosystems, it's not as far advanced in terms of community
#
Zakim
sees akuckartz on the speaker queue
#
rhiaro_
... it's not as far advanced in terms of developers or users
#
rhiaro_
it's early
#
elf-pavlik
q+ to propose discussion about evolution of the whole system, extensible design and backward/forward compatibility
#
Zakim
sees akuckartz, elf-pavlik on the speaker queue
#
eprodrom
aaronpk, that's really a great idea
#
cwebber2
aaronpk, yes I'd like to do that
#
eprodrom
But I'd like to have a proof-of-concept first
#
Tsyesika
i fully intend to use whatever i make on my website
#
rhiaro_
... It's hard to document, hard to get across that it's simpler than the percieved learning curve
#
Arnaud
ack akuckartz
#
Zakim
sees elf-pavlik on the speaker queue
#
cwebber2
eprodrom, something I've thought of
#
cwebber2
Tsyesika, also
#
cwebber2
maybe making something like a "Disqus" for activitypump
#
cwebber2
I got interested in this when I realized the endpoints can point off-server
#
eprodrom
heh
#
cwebber2
so static publishing people can have a federation panel still
#
eprodrom
Yeah that's pretty cool
#
rhiaro_
akuckartz: you have to get in and understand what linked data is about. I'm pretty sure ibm, boeing, would be abel to do that. People who don't have those resources - is it possible to modify or restrict the proposal for SoLiD so that the implementation curve is reduced?
#
rhiaro_
... with the purpose of making it easy for others
#
eprodrom
Why?
#
deiu
q+ to suggest we rename SoLiD
#
Zakim
sees elf-pavlik, deiu on the speaker queue
#
eprodrom
I mean, why would I have to do that?
#
hhalpin_
q+
#
Zakim
sees elf-pavlik, deiu, hhalpin_ on the speaker queue
#
rhiaro_
... who never dealt with semantic web, to adopt spec
#
ben_thatmustbeme
cwebber2, eprodrom, thats exactly what tantek was talking about last F2F with the desire to always support static sites
#
eprodrom
If I understand JSON-LD, why do I have to do my Semantic Web meditation training
#
eprodrom
?
#
cwebber2
ben_thatmustbeme, yes, it took me a while to understand what that meant
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to propose discussion about evolution of the whole system, extensible design and backward/forward compatibility
#
Zakim
sees deiu, hhalpin_ on the speaker queue
#
sandro
imho, you don't eprodrom
#
eprodrom
q+
#
Zakim
sees deiu, hhalpin_, eprodrom on the speaker queue
#
cwebber2
ben_thatmustbeme, but when I got it I got kind of excited about how to do it with activitypump
#
eprodrom
sandro, I don't think so either
#
cwebber2
hence my post about it to the list
#
rhiaro_
elf-pavlik: I'd like to propose discussion about evolution of APIs, especially breaking changes
#
rhiaro_
... power of web by showing opening an old webpage in a modern browser
#
deiu
q+ tim
#
Zakim
sees deiu, hhalpin_, eprodrom, tim on the speaker queue
timbl and melvster_ joined the channel
#
rhiaro_
... could analyse apis this way, how they could be broken by certain design choices
#
rhiaro_
... how to avoid this in future
#
eprodrom
q-
#
Zakim
sees deiu, hhalpin_, tim on the speaker queue
#
Arnaud
ack deiu
#
Zakim
deiu, you wanted to suggest we rename SoLiD
#
Zakim
sees hhalpin_, tim on the speaker queue
#
rhiaro_
deiu: maybe SoLiD was not the right name for this spec
#
rhiaro_
... We should remove the parts of the spec that aren't relevant to the workign group from the spec
#
rhiaro_
... we started writing the spec with a state of mind in which we wanted to document the whole thing that we were doing
#
rhiaro_
... that's too much at this point, for this group
#
Arnaud
ack hhalpin_
#
Zakim
sees tim on the speaker queue
#
rhiaro_
hhalpin: when we were writing the charter we knew we were going to have something liek this problem
#
rhiaro_
deiu++
#
Loqi
deiu has 5 karma
#
rhiaro_
... most of the world using json based apis
#
rhiaro_
... this could change next year, I find it unlikely
#
rhiaro_
... the microformat html based approach has advantages, but we didnt' write this in the charter because most people want to ship around json not html
#
rhiaro_
... and we want to be open to enterprise use cases
#
rhiaro_
... we thought we'd have more enterprise membership to the group
#
rhiaro_
... but that's changed, we have a much more open sourced, hacker based community
#
rhiaro_
... on that basis, I could see revisiting json as charter requirement
#
tantek
and the microformats based approach has a canonical JSON representation - which is why I was ok with charter mentioning "JSON"
#
rhiaro_
... in terms of rdf communities, the amount of people using json and html vs json-ld is smaller
#
rhiaro_
... using RDF is powerful for people who want it
#
rhiaro_
... I'd be concerned if we did an rdf *only* spec
#
rhiaro_
... json-ld was trying to fix that
#
rhiaro_
... I wasn't thinking about html microformats case when writing the charter
#
rhiaro_
... microformats2 does have json version, we could massage something there
#
rhiaro_
... I'm hoping json-ld plus parsing html could bridge these communities
#
rhiaro_
... the goal of any decentralised social web should be to bridge, we don't want three decentralised silos
#
Zakim
sees tim on the speaker queue
#
rhiaro_
... ideally we don't want three different standards, we want one standard that allows the different networks and different communities to do what they want with rich communication
#
rhiaro_
... I'm hoping URI extensibility will help with this
#
sandro
q+ to suggest the contexts can bridge to microformats and form-encoding
#
Zakim
sees tim, sandro on the speaker queue
#
rhiaro_
... Charter isn't written in stone, but when I was writing it this is what I was seeing
#
eprodrom
_1
#
eprodrom
+1 I mean
#
rhiaro_
... there are a number of high level things that are the same
#
Arnaud
ack tim
#
Zakim
sees sandro on the speaker queue
#
eprodrom
q+
#
Zakim
sees sandro, eprodrom on the speaker queue
#
rhiaro_
timbl: Feeling of deja vu
#
rhiaro_
... back in the xml days... json is the new xml
#
rhiaro_
... the xml and rdf communities were born at about the same time
#
eprodrom
Poor rhiaro_
#
rhiaro_
... everyoen was commiteed to xml, and rdf should be as xml like as possible
#
rhiaro_
... that was a massive mistake
#
elf-pavlik
rhiaro++
#
Loqi
rhiaro has 79 karma
#
rhiaro_
... rdf is simpler than xml
#
rhiaro_
... by trying to make an xml syntax it was horrible
#
rhiaro_
... should have used turtle originally
#
eprodrom
Actually timbl is being pretty slow-paced right now
#
rhiaro_
... a few companies have had similar experience
#
rhiaro_
... a guy said he wasted three years looking at rdf through xml glasses
#
rhiaro_
... so json is just a shoe-in for xml
#
rhiaro_
... incentive because it's used in javascript
#
rhiaro_
... you can't address things within a json document
#
rhiaro_
... something about blank nodes
#
hhalpin_
q- hhalpin
#
Zakim
sees sandro, eprodrom on the speaker queue
#
rhiaro_
... json is interesting, and helping people get from one to the other is interesting, but potentially counterproductive, I'm torn
#
rhiaro_
... try A/B
#
rhiaro_
... take one set of developers and give them a json world, and another set who forget json and think about core rdf model
#
rhiaro_
... think about that, send turtle across the wire
#
rhiaro_
... and you'll find yourself empowered because yoru life is simpler
#
rhiaro_
... can merge data streams by concatenating files
#
rhiaro_
... you can build any application on LDP without the store having to know anything about it
#
rhiaro_
... they are different philosophies
#
rhiaro_
... we're desinging new stuff
#
rhiaro_
... the number of people using json at the moment is in some ways totally irrelevant
#
rhiaro_
... there is ane xcited turtle community
#
hhalpin_
q+
#
Zakim
sees sandro, eprodrom, hhalpin_ on the speaker queue
#
rhiaro_
... we should provide something that does not require json
#
rhiaro_
... and allow turtle directly
#
rhiaro_
arnaud: I can see there are differences that could be easily accommodated between different approaches, and combined
#
rhiaro_
... like content negotiation, format of data can be accommodated
#
rhiaro_
... solutions that support several different formats
#
rhiaro_
... some differences are harder to accommodate
#
rhiaro_
... some that use a single entry points, some more restful
#
rhiaro_
... this is harder, you go one way or the other
#
tommorris_
notes that he has seen people using XSLT to transform RDF/XML and despaired.
#
rhiaro_
... aaron and jessica acknowleged some of the other stuff can be used to learn from
#
rhiaro_
... there are poitns of convergance we can identify
#
sandro
was required once to write XSLT to turn OWL/XML into OWL
#
Arnaud
ack sandro
#
Zakim
sandro, you wanted to suggest the contexts can bridge to microformats and form-encoding
#
Zakim
sees eprodrom, hhalpin_ on the speaker queue
#
rhiaro_
tommorris_: some of my students do that for coursework :D
#
rhiaro_
of their own inclination
#
Zakim
sees eprodrom, hhalpin_, melvster_ on the speaker queue
#
rhiaro_
sandro: I think having an implicit (or explicit) json-ld context, basically we can get form encoding and microformats to be json-ld
#
rhiaro_
... they're really close
#
hhalpin_
My hope is that JSON-LD could basically, with some auto-conversion on server or client side, could be the lingua franca.
#
rhiaro_
... then we're down to vocabulary mapping question
#
rhiaro_
... they're different vocabularies
#
hhalpin_
Vocabulary mapping can be worked out, they are not super-different
#
rhiaro_
... hoping one community could switch
#
rhiaro_
... no idea what politics of that are
#
hhalpin_
There seems general consensus around a HTTP REST model.
#
ben_thatmustbeme
getting those vocabulary difference documented would be a good step on that
#
rhiaro_
... Big thing about static sites being different wrt being restulf
#
rhiaro_
... but you could say a static site is like restful funnelled through one endpoint
#
rhiaro_
... if you don't do that, you can go through individual URIs
#
rhiaro_
... discover of that could be painful, but may be worth while
#
rhiaro_
... Also, seems like ActivityStreams is sending across changes in an application specific way
#
rhiaro_
... in the end SoLiD don't have a way to do this
#
rhiaro_
... but we've talked about it having an application non-specific ways to send changes
#
rhiaro_
... like a diff stream
#
rhiaro_
... don't care what kind of data, just want changes to any kind of data
#
rhiaro_
... my inclination is towards the generic one
#
rhiaro_
... curious, people who work on ActivityStreams can they consider giving up on terms like Like
#
ben_thatmustbeme
wonders if we have a list of people actually using ActivityStreams now
#
eprodrom
??
#
rhiaro_
... why do you want to explicitly like something rather than just say you changed some data
#
eprodrom
ben_thatmustbeme, yes all of us
#
eprodrom
Since we're publishing it as a spec
#
Arnaud
ack eprodrom
#
Zakim
sees hhalpin_, melvster_ on the speaker queue
#
rhiaro_
arnaud: more powerful, but harder to get there
#
deiu
eprodrom, I'll take a stab at AS for our apps
#
ben_thatmustbeme
eprodrom, you mean all pump.io group? indieweb has not yet really found AS2.0 to be useful, as the different philosophy of everything is a post. but I'm thinking it makes a lot more sense in the notifications sense
#
rhiaro_
eprodrom: addressing harry's point. If you look at these three systems, if you take something like solid and remove webid requirement, add specific containers that are related to each user (folllowing, followers, favourites, ..) and you require some server side behaviour, you've got activitypump
#
rhiaro_
... if you favour activitystreams as main vocab and favour json-ld serialization
#
rhiaro_
... they are very close
#
rhiaro_
... the outlier is micropub
#
rhiaro_
... micropub is going to survive regardless
#
rhiaro_
... but we could do something like activitypump informed by SoLiD design
#
rhiaro_
... and suggest micropub as a social api for (??)
#
ben_thatmustbeme
eprodrom, didn't mean to interrupt you, was just finishing my thought.
#
rhiaro_
... we canc ome out with two specs
#
rhiaro_
arnaud: I think evan jumped the gun
#
hhalpin_
q?
#
Zakim
sees hhalpin_, melvster_ on the speaker queue
#
rhiaro_
eprodrom: I'd rather not describe our group as three different camps
#
elf-pavlik
q+ to propose convergence driven by queries on the (social) datasets
#
Zakim
sees hhalpin_, melvster_, elf-pavlik on the speaker queue
#
rhiaro_
... in competition
#
Zakim
sees hhalpin_, melvster_, elf-pavlik on the speaker queue
#
rhiaro_
... we have to ship something
#
rhiaro_
... I'm not sure a competitive framework it he one we should be working
#
Tsyesika
I'm not so sure micropub is all that fundermentally different, after talking to aaronpk more these two days and looking at amy's work it looks like there could be some resolve a lot of our "differences"
#
rhiaro_
doesn't think anyone is really thinking competitively lany more
#
sandro
Right -- we all have pretty much the SAME GOAL
#
rhiaro_
... whatever group decides, I'll hold my nose and get it done, but won't necessarily like it
#
Arnaud
ack hhalpin
#
Zakim
sees melvster_, elf-pavlik on the speaker queue
#
ben_thatmustbeme
Tsyesika, i'm very interested to hear your thoughts on that.
#
rhiaro_
hhalpin: we weren't hoping on staying competitive
#
rhiaro_
... that was to force peopel to compare each other to find commanalities and differences
#
rhiaro_
... we're at the point where we can solve some of them
#
rhiaro_
... we're clearly seeing some convergance
#
rhiaro_
... hoping json-ld can be converted into mf or turtle
#
ben_thatmustbeme
theoretically if we did switch micropub to json instead of form encoded, likely as some other version of MP, how much would that change usability by the other communities?
#
rhiaro_
... the devil is in the detail of vocabulary alignments, link headers etc
#
eprodrom
???
#
rhiaro_
... In terms of what evan said about indieweb, worth noting that indiewb has the most grassroots developer adoption
#
eprodrom
hhalpin_: can you justify that?
#
sandro
s/_:/_,/
#
rhiaro_
... One of the critques when we started this group is that w3c has tendancy to be overly complicated and drive away developers
AnnB joined the channel
#
eprodrom
We have hundreds of thousands of users on pump.io
#
rhiaro_
... So how can we simplify what everyone is doing
#
Arnaud
ack melvster_
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro_
melvster: we had this group a few years ago run by RMS called GNU consensus
#
eprodrom
I count well less that 100 using indieweb
#
rhiaro_
... idea was to get social web componants to talk to each other
#
eprodrom
ben_thatmustbeme in response, no, I mean the social web wg
#
rhiaro_
... tried to condense to 'hello world' use case, but it failed because no social web groups would talk to any others
#
rhiaro_
... now we've seen we've all solved similar use cases
#
rhiaro_
... can we get all groups to focus on a minimal use case to talk to each other
#
sandro
eprodrom, be what about number of implementations? I think that's IWC's claim.
#
rhiaro_
hhaplin: we already have use cases
#
rhiaro_
melvster: for test suite
#
rhiaro_
aaronpk: that was the goal of creating SWAT0
#
eprodrom
sandro, yes, and if we go by whether a spec has odd or even number of characters in it, I think SoLiD wins there
#
rhiaro_
hhaplin: ideal situation we have api and common data format and we use that for common use cases
#
rhiaro_
melvster: can we test it?
#
rhiaro_
hhalpin: yes we will
#
rhiaro_
arnaud: part of the process is creating a test suite and showing interop
#
rhiaro_
melvster: by the next f2f?
#
eprodrom
sandro, although I think we might have more pump.io clients than there are implementations of the indieweb stuff
#
rhiaro_
bblfish: we should implement these stories
#
eprodrom
Really?
#
rhiaro_
hhalpin: goal of standardisation workgroup is to produce a standard, not to have a nice time and learn from each other
#
rhiaro_
... if we produce a standard we fail, or produce a standard with low adoption or contradictory standards, also fail
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to propose convergence driven by queries on the (social) datasets
#
rhiaro_
arnaud: we're nowhere near there yet
#
Zakim
sees no one on the speaker queue
#
rhiaro_
elf-pavlik: we haven't moved much on querying or accessing data
#
rhiaro_
... evan mentioned with indieweb you can't get social graph and relationships
#
rhiaro_
... from the resulting data, we can derive requirements of api
#
rhiaro_
... with linked data, by following your nose you do it in the same way
#
bret
Is there a Zakim or tally room?
#
rhiaro_
... could be some interesting ways of approach resulting dataset
#
hhalpin
It can work, we have seen this with WebCrypto where we got every browser implementing the same crypto API despite underlying differences (NextGen Crypto API, NSS, ec.)
#
rhiaro_
... then find some common ground
#
rhiaro_
arnaud: break until the hour
#
Zakim
-INRIA
#
ben_thatmustbeme
eprodrom, huh? perhaps i should rephrase, how many have actually implemented and are publishing an AS2.0 stream
#
eprodrom
ben_thatmustbeme, to what point?
#
cwebber2
ben_thatmustbeme, the spec isn't even out yet
#
eprodrom
That it doesn't matter because it's not implemented?
#
eprodrom
We're publishing it. It's our job to ship it.
#
Arnaud
zakim, who's on the phone?
#
Zakim
On the phone I see ??P2, cwebber2, ben_thatmustbeme (muted)
bblfish joined the channel
#
hhalpin_
I sould assume we will be implement AS2.0
#
eprodrom
It's ridiculous that we'd turn up our nose at the spec that we are producing and saying it's not good enough because it's not implemented.
#
hhalpin_
if we don't, we should not ship it as a spec
#
eprodrom
Or we should fix it
#
hhalpin_
However, it's still quite early
#
ben_thatmustbeme
eprodrom, indieweb philosophy is to work out an implementation that works, then spec around it. I'm not suggesting that. I'm saying implment it too
#
hhalpin_
I think we will have a problem if in a year from now there aren't AS2.0 implementations
#
eprodrom
ben_thatmustbeme, right, I understand that.
#
ben_thatmustbeme
before the spec is done, because you will never have a spec finished unless you start implementing
#
eprodrom
ben_thatmustbeme, I totally agree
#
hhalpin_
Re the indieweb approach, I tend to agree
#
eprodrom
On the other hand, I don't like to implement things multiple times
#
ben_thatmustbeme
i was just trying to see who is publishing as2.0 streams NOW, as they can better make statements about where it is and isn't useful
#
eprodrom
I especially don't like to put my users through a lot of incompatibility pain
#
eprodrom
"Sorry, I implemented an intermediate version of the spec, now all your feeds are broken."
#
ben_thatmustbeme
eprodrom, doesn't mean it has to be on a large system, but you still need some sort of system to test it
#
eprodrom
ben_thatmustbeme, I agree
#
ben_thatmustbeme
direct question, do you have a published intermediate version of an AS2.0 stream? that I can right now try to consume
#
eprodrom
No I do not
#
eprodrom
But there are test versions in the test repo
#
eprodrom
Which might be good for you to start with
#
ben_thatmustbeme
okay, so If i start playing with implementations, I'm not looking at anything else. So I may end up with a lot of suggestions for changes on the MF2 version of it
#
eprodrom
sandro, blunt question
#
eprodrom
Is SoLiD just CrossCloud rebranded?
#
eprodrom
The name slipped earlier
#
eprodrom
I don't think that's a bad thing but I'm kind of confused by the whole 'keep it general for all kinds of apps' thing
#
eprodrom
I reallllly think CrossCloud is a great idea
#
Zakim
+[IPcaller]
#
ben_thatmustbeme
general question that i asked and i didn't see any response... if I wrote a MP client that posted with json data instead of form encoded, would that be more interesting to compatibility building? what would still be lacking? argue points better or worse, etc
#
Arnaud
zakim, call inria-bridge
#
Zakim
ok, Arnaud; the call is being made
#
Zakim
+Inria
#
eprodrom
Neat
#
eprodrom
I'm OK
#
eprodrom
Just a lot of beeps
#
Zakim
-[IPcaller]
#
Arnaud
we had to reconnect the bridges
#
Arnaud
we're on a break
#
akuckartz
ben_thatmustbeme: We are still having a break.
#
eprodrom
Yes
#
Arnaud
thanks
#
eprodrom
Thank you
#
Tsyesika
eprodrom: i'll try and get these issues worked through and then we should work on a basic implementation
#
Tsyesika
makes no sense with all those open issues
bblfish joined the channel
#
Zakim
sees no one on the speaker queue
#
cwebber2
I'm interested in collaborating on a basic implementation, and am flexible on what language
#
cwebber2
as long as not php ;)
#
Tsyesika
i'm flexable on language too
#
Tsyesika
but it looks like the issues on it atm will cause a big chnge
#
Tsyesika
*change
#
Tsyesika
if eprodrom wants to try out go it's all good for me
#
rhiaro_
did we get a scribe yet?
#
eprodrom
Tsyesika: let's see how the conversation goes today
#
bblfish
Topic: next meetnig
#
bblfish
Arnaud: advantages of continuing next week is that we should keep the momentum
#
eprodrom
Agreed
#
rhiaro_
scribenick: bblfish
#
eprodrom
Nice handwriting
#
bblfish
Arnaud: we could have a debriefing meeting next week
#
bblfish
Arnaud: anyone objects to not canceling next meeting?
#
bblfish
Resolve: Continue next week
#
bblfish
RESOLUTION: Continue next week
#
akuckartz
aaronpk++
#
Loqi
aaronpk has 796 karma
#
aaronpk
q+ to talk about authentication in the APIs
#
Zakim
sees aaronpk on the speaker queue
#
bret
Thanks for the whiteboard photo
#
bblfish
Arnaud: severaly way we could imagine resolving the differences. We should discuss the strategy
#
Zakim
sees aaronpk, bblfish on the speaker queue
#
bblfish
Arnaud: we could just continue resolving issues
#
elf-pavlik
q+ to propose continue with showing implementation of User Stories
#
Zakim
sees aaronpk, bblfish, elf-pavlik on the speaker queue
#
bblfish
Arnaud: or we could just bite the bullet and go from there.
AnnB joined the channel
#
Arnaud
ack aaronpk
#
Zakim
aaronpk, you wanted to talk about authentication in the APIs
#
Zakim
sees bblfish, elf-pavlik on the speaker queue
#
eprodrom
q+
#
Zakim
sees bblfish, elf-pavlik, eprodrom on the speaker queue
#
bblfish
aaronpk: differences between our API and jessica, we could arrive at a compromise and explore that possibility. WE need to look at this more. We now can see how things are similar and different
#
bblfish
aaronpk: also we could make a point about authentication: it appears that all three APIs use verifiers with tokens, we could leave the way to get the token out of the API, and leave that for the next API.
hhalpin joined the channel
#
hhalpin
q+
#
Zakim
sees bblfish, elf-pavlik, eprodrom, hhalpin on the speaker queue
#
deiu
rhiaro++
#
Loqi
rhiaro has 80 karma
#
deiu
pssst, rhiaro needs more karma
#
bblfish
aaronpk: I was surprised to see a lot of convergence
#
rhiaro_
commonground++
#
Loqi
commonground has 1 karma
#
Arnaud
ack bblfish
#
Zakim
sees elf-pavlik, eprodrom, hhalpin on the speaker queue
#
AnnB
that's the reason to have F2F meetings!
#
rhiaro_
note, sandro just indicate he sees common ground between SoLiD and micropub
#
rhiaro_
so that's the full triangle :D
#
elf-pavlik
bblfish: to common ground seams to be notion of container and posting to containers
#
AnnB
people work stuff out more easily when actually in person ... not to mention with pizza, sushi, wine, beer ...
#
AnnB
triangles are the strongest foundation
#
elf-pavlik
bblfish: also some use POST everything
#
elf-pavlik
... maybe some mapping would allow finding common ground
#
akuckartz
convergence++
#
Loqi
convergence has 1 karma
#
elf-pavlik
... i see common understanding that thanks to JSON-LD we can think in RDF level and still people can use it as plain JSON
#
elf-pavlik
... one can consider AS2.0 as cristalization of RDF (rel to article bblfish wrote year ago)
#
elf-pavlik
bblfish: we should automatically find a way to produce it on LDP servers
#
cwebber2
full_triangle++
#
Loqi
full_triangle has 1 karma
#
elf-pavlik
... i can with my tools in very generic way and at the same time people who don't want to use those tools (yet) they can still interoperate
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to propose continue with showing implementation of User Stories
#
Zakim
sees eprodrom, hhalpin on the speaker queue
#
Arnaud
ack eprodrom
#
Zakim
sees hhalpin on the speaker queue
#
bblfish
elf-pavlik: we should write implementations of the top uses cases and get feedback by doing that.
#
aaronpk
evanpro: i feel like we're stretching the amount of time we're getting out of this community to begin with, the idea that we'd write multiple implmenenations for hte contiually iterating different standards, and spend time evallutaing them and figuring it out...
#
aaronpk
evanpro: i'd rather put that time towards a single standard
#
AnnB
+1'
#
aaronpk
... rather than splitting that time among multiple standards
#
aaronpk
... i'm not sure this convergence is going to get easier
#
elf-pavlik
bblfish scribe?
#
aaronpk
... i feel like we've already put off this decision once, we need to start coming down to what the social apis are going to be if expect to ship it by the end of the year
#
aaronpk
... i'm sure that our friends here on w3c staff are optimistic about having our charter renewed
#
deiu
Isn't that a bit premature?
#
aaronpk
... i'm not sure i have the mental capacity to continue doing this if we never actually come out with results
#
bblfish
evanpro: we need to bite the bullet fast, or else the charter can be completed
#
sandro
Don't we have 20 months left?
#
aaronpk
... my feeling is there is some urgancy, we probably need to make some tough decisions
#
bblfish
s/can/cannot/
#
aaronpk
Arnaud: we are not expiring at the end of this year, at the end of 2016
#
eprodrom
Thanks for the correction
#
aaronpk
... i agree we don't want to waste time, but it's also not as critical as you just described
#
eprodrom
Yes, 2016
#
aaronpk
... to have a recommendation by the end of next year, we better have a solid proposal by the end of this year
#
aaronpk
... there's still a lot of work
#
deiu
Solid is such a troll name :)
#
aaronpk
.... i agree by the end of this year we'd beter have a good idea of what this looks like
#
Zakim
sees hhalpin on the speaker queue
#
Zakim
sees hhalpin on the speaker queue
#
Arnaud
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
sandro
yeah, I keep laughing at it
#
elf-pavlik
q+ to mention that current drafts already start or even address federation
#
Zakim
sees elf-pavlik on the speaker queue
#
aaronpk
hhalpin: next steps: from each of the three communities, we should choose an author from each comunity
#
aaronpk
... to help filter to an editor a draft editor
#
aaronpk
... or two editors, who is neutral, not in any of the camps
#
aaronpk
... to try to push a converged document out
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to mention that current drafts already start or even address federation
#
bblfish
@hhalpin wants to operationalise what evan said. Next step: from the three communities we should choose an author from each community one or two draft editors, to push a draft document out to see if we can get consensus
#
Zakim
sees no one on the speaker queue
#
aaronpk
elf-pavlik: it seems that some of the candidates addressed federation
#
bblfish
@elf-pavlik the federation may be part of the API so it may not be that much work
#
aaronpk
hhalpin: we probably won't be able to include federation
#
aaronpk
Arnaud: or maybe we'll have it beacuse it's built in
#
elf-pavlik
aaronpk bblfish double scribing :D
#
aaronpk
is happy to take over
#
bblfish
@hhalpin one author: the author writes a lot of the text, and the editors does ?
#
bblfish
please help me scribing it's easier
#
aaronpk
hhalpin: you need at least one neutral person who doesn't really care to help balance out arguments that arise
#
aaronpk
AnnB: the reason i'm asking is after dec 11 i'm free, and i'm a good editor
#
aaronpk
Arnaud: to get back to the point, the proponents seem to be in agreement to give people a bit more time to choose a starting point, to experiment a bit further
#
hhalpin
JSON-LD has the author/editor distinction - http://www.w3.org/TR/json-ld/
#
Zakim
sees akuckartz on the speaker queue
#
aaronpk
... i'm in favor of doing this , because i rather we start with a more constricted approach rather than saying so and so is winning
#
AnnB
I will not have time before I leave Boeing ... but can probably help edit after I leave
#
hhalpin
Or just all editors, but we need at least one neutral person in case there are severe disagreements
#
hhalpin
Also, we need to see what the implementation commits are
#
aaronpk
... there is value in holding off for a little more
#
Zakim
sees akuckartz, sandro on the speaker queue
#
Zakim
sees akuckartz, sandro, aaronpk on the speaker queue
#
Arnaud
ack akuckartz
#
Zakim
sees sandro, aaronpk on the speaker queue
#
eprodrom
q+
#
Zakim
sees sandro, aaronpk, eprodrom on the speaker queue
#
bblfish
@Arnaud prefer to work towards a more constructive approach, so there is value to holding off a little bit more. Agree that it is unrealistic to have everybody make three implementations.
#
aaronpk
akuckartz: would it be possible to start with writing what is accepted as common ground?
#
bblfish
@akuckartz would it help to work out what the common ground is ?
#
elf-pavlik
q+ to mention we already agreed for 'follow your nose' during last F2F
#
Zakim
sees sandro, aaronpk, eprodrom, elf-pavlik on the speaker queue
pfefferle joined the channel
#
ben_thatmustbeme
I have to go... headed to the ER
#
eprodrom
elf-pavlik: do any of these proposals not do that?
#
eprodrom
Or is that just a point of commonality?
#
cwebber2
how about rhiaro? :)
#
aaronpk
AnnB: what about making an outline? fill in the bits that are known now
#
ben_thatmustbeme
these kids don't want to stay in her
#
eprodrom
rhiaro_++
#
Loqi
rhiaro_ has 81 karma
#
aaronpk
akuckartz: maybe start with a wiki page and collect the common ground
#
elf-pavlik
+1 rhiaro if she would like to take on this challenge
#
Arnaud
ack sandro
#
Zakim
sees aaronpk, eprodrom, elf-pavlik on the speaker queue
#
aaronpk
sandro: i dont think the editors need to be neutral, they just need to be enthusiastic about whatever happens
#
ben_thatmustbeme
AnnB, looks like the twins are coming today
#
bblfish
@sandro: don't think that the editors need to be neurtal, but they need to be enthusiastic about what happens. They have to do what the working group decides
#
eprodrom
ben_thatmustbeme WOW! Go do that!
#
ben_thatmustbeme
yeah, so I'm off
#
AnnB
ohmigosh, ben_thatmustbeme! wOOOOOt!! good luck
#
cwebber2
ben_thatmustbeme, wow, good luck!
#
eprodrom
ben_thatmustbeme It's gonna be great!!!!
#
hhalpin
q+
#
Zakim
sees aaronpk, eprodrom, elf-pavlik, hhalpin on the speaker queue
#
AnnB
hope you have stocked up on sleep
#
bblfish
... how do we handle syntaxes.
#
ben_thatmustbeme
AnnB i wish it worked that way
#
AnnB
never does
#
hhalpin
HTTP REST(ish), common vocabulary (re microformats and ActivityVocab), and fix the HTTP headers so they are common
#
AnnB
the rest of your life will be both challenging and enriched
#
Arnaud
ack aaronpk
#
Zakim
sees eprodrom, elf-pavlik, hhalpin on the speaker queue
#
bblfish
@Arnaud if there are issues that can be expressed independently of the implementation, that can be addressed
#
AnnB
good thing you're not in Paris!
#
eprodrom
concrete steps with deadlines++
#
cwebber2
could we have a prototypes deadline?
#
Zakim
+??P7
#
bblfish
@aaronpk to avoid the issue of endless postponing lets have some deadlines
#
bret
Zakim, ??P7 is me
#
Zakim
+bret; got it
#
bret
Zakim, mute me
#
Zakim
bret should now be muted
#
Arnaud
ack eprodrom
#
Zakim
sees elf-pavlik, hhalpin on the speaker queue
#
Zakim
sees elf-pavlik, hhalpin on the speaker queue
#
aaronpk
evanpro: what i'd like to get an idea of is what we think would be some changes in the state of the WG now that would show us that we're movign forward
#
Zakim
sees elf-pavlik, hhalpin, cwebber on the speaker queue
#
bblfish
eprodrom: what would be some changes to the state of the working group that would show us moving forward.
#
aaronpk
.. concerned about jessica not having time to keep editing the AP doc
#
aaronpk
.. or the solid people drop out because there's a new version of java it can't run on
#
deiu
java?
#
bblfish
... what are the changes that happen that we get going further?
#
aaronpk
.. i'm more cocerned about what are the change that happen that make us sure we're going further
#
elf-pavlik
maybe ES6
#
Zakim
sees elf-pavlik, hhalpin, cwebber, bblfish on the speaker queue
#
aaronpk
.. i'm not sure there's a clear positive way forward, is it that we create a SoLiD/actvitypump/micropub spec?
#
aaronpk
.. is it we find something that's the olowest common demoninator (which right now HTTP)
#
aaronpk
.. what will the change be next time we sit down in japan
#
bblfish
.. I don't know that there is a clear way forward? Is that we create a spec with the lowest common denominator which I think is HTTP at present. How do we see the way forward?
#
Zakim
sees elf-pavlik, hhalpin, cwebber, bblfish, deiu on the speaker queue
#
aaronpk
.. the only change i see that is likely is that we lose members and lose interest
#
Zakim
sees elf-pavlik, hhalpin, cwebber, bblfish on the speaker queue
#
aaronpk
Arnaud: maybe we have different perceptions
#
bblfish
.. the only change I see is likely is that we loose members and move forward
#
aaronpk
.. because you're missing out on being at the meetingand at lunch
#
aaronpk
.. my feeling is there's a lot of common ground and recognizing this and seing ways of converging
#
deiu
q+ to mention "browsing the social graph" as the common denominator
#
Zakim
sees elf-pavlik, hhalpin, cwebber, bblfish, deiu on the speaker queue
#
rhiaro_
It's come through that people care a *lot* this last couple of days
#
rhiaro_
Hopefully we're past worrying about falling apart now!
#
rhiaro_
joins elf-pavlik in pathological optimism
#
bret
Generate 3 specs and let the best spec win? ;)
#
aaronpk
.. we can use every week to say how's that going
#
cwebber2
setting a deadline on that checkpoint is a good idea
#
bblfish
@bret bad idea ...
#
aaronpk
.. it's a bit pessmiistec right now to say we're going to waste time and lose members
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to mention we already agreed for 'follow your nose' during last F2F
#
hhalpin
q?
#
Zakim
sees hhalpin, cwebber, bblfish, deiu on the speaker queue
#
Zakim
sees hhalpin, cwebber, bblfish, deiu on the speaker queue
#
aaronpk
elf-pavlik: i'll try to experiment with different workflows to work between telecons
#
aaronpk
.. i see github and irc very practical
#
aaronpk
.. also for writing the document, trying to capture following the nose idea
#
Zakim
-bret
#
bret
ack lost connection :(
#
Loqi
aww, cheer up
#
Arnaud
ack hhalpin
#
Zakim
sees cwebber, bblfish, deiu on the speaker queue
#
aaronpk
Arnaud: we're quickly running out of time
#
Zakim
-ben_thatmustbeme
#
aaronpk
hhalpin: one way to focus the group would be to not raise as many issues, because issues take a lot of time to reseolve
#
cwebber2
+1 on that
#
aaronpk
... especailly RDF issues, which take a lot of time and are of limited relevance to everyone
#
aaronpk
.. allow the editor to have discretion
#
aaronpk
.. if people are really upset about that, let'sd do it on an issue-by-issue basis
#
aaronpk
.. second thing is in terms of authentication, we need to have a generic, i think the bearer token comment was en point
#
aaronpk
.. the w3c will liekly be starting a web authentication working group in the fall
#
aaronpk
.. the work is pretty baked already, around fido
#
aaronpk
.. we need to keep that out of scope
#
aaronpk
.. in terms of next steps, i'm happy to have aaron and jessica work and maybe someone from SoLiD
#
Arnaud
ack cwebber
#
Zakim
sees bblfish, deiu on the speaker queue
#
aaronpk
.. but two or three people need to take responsibiltiy for converging
#
aaronpk
cwebber2: i think having aaron and jessica and osmone from solid try to find what the common ground is is a great idea
#
Zakim
+??P5
#
bret
Zakim, ??P5 is me
#
Zakim
+bret; got it
#
bret
Zakim, mute me
#
Zakim
bret should now be muted
#
aaronpk
.. it seems like a lot of progress happened in this f2f whereas the last one the message was implementations win but we were going to end up rubber stamping somehing we already had
#
rhiaro_
I agree with cwebber2
#
aaronpk
.. maybe after these converstaions happen, we can start to establish what are the prototype implementation goals
#
aaronpk
.. i do agree we should be moving into implementation phase pretty soon
#
Arnaud
ack bblfish
#
Zakim
sees deiu on the speaker queue
#
aaronpk
bblfish: i think these 3 groups are woring in different layers, so it's quite easy to get them to agree if we understand the different layers
#
aaronpk
.. as i was saying earlier, the container stuff is a container, what i'm seeing from activitystreams is a certain vocab which has certain side effects
#
aaronpk
.. it's kind of a specialized convtainer which does special things
#
aaronpk
.. turns out most of it has been already written
#
aaronpk
.. i disagree with harry about the rdf vocab, if we can think about the modeling correctly, we'll be able to narrow down much more quickly
#
Arnaud
ack deiu
#
Zakim
deiu, you wanted to mention "browsing the social graph" as the common denominator
#
Zakim
sees no one on the speaker queue
#
aaronpk
deiu: we're talking about the smallest common denominator, but we haven't really decided how to model basic things
#
aaronpk
.. like users and identities
#
aaronpk
.. so how to we get to see and browse each other's social graph
#
eprodrom
What about AS 2.0 vocabulary?
#
aaronpk
Arnaud: it'd be useful as a first step to list capabilities and features that we want to have
#
aaronpk
.. it would go along the lines of having an outline of what we want the spec to cover
#
aaronpk
.. we've seen through the deep dives we made there's a certain operation we expect to be able to have
#
cwebber2
a question is, how will that be different from user stories?
#
aaronpk
.. what are the basic blogs we need ot have for this api
#
aaronpk
.. not getting into the details of what the blocks look like
#
cwebber2
will this be a shared technical requirements requirements?
#
eprodrom
s/blogs/blocks/
#
Zakim
sees no one on the speaker queue
#
Zakim
sees deiu on the speaker queue
#
aaronpk
thanks eprodrom lol
#
eprodrom
B-)
#
aaronpk
.. one of the features of the indieweb is the modular approach
#
eprodrom
q+
#
Zakim
sees deiu, eprodrom on the speaker queue
#
aaronpk
.. we don't start building a big spec, we define little specs with different modules
#
aaronpk
.. wecan experiment and argue over those different blocks
#
Arnaud
ack deiu
#
Zakim
sees eprodrom on the speaker queue
#
Zakim
sees eprodrom on the speaker queue
#
aaronpk
deiu: classifying all these items would also allow us to see whether some of them are relevant or not
#
aaronpk
.. which means we might be able to remove some of the work ahead of us
#
elf-pavlik
q+ to very shortly mention extensibility e.g (currently ActivityPump only supports Follow and Like action + relevant collections)
#
Zakim
sees eprodrom, elf-pavlik on the speaker queue
#
Arnaud
ack eprodrom
#
Zakim
sees elf-pavlik on the speaker queue
#
aaronpk
can someone open a window/door?
#
aaronpk
eprodrom: two questions. the idea that we're trying to define the basica building blcoks, isn't that what the user stories were for?
#
Zakim
sees elf-pavlik, bblfish on the speaker queue
#
aaronpk
.. if there's really a lot of question about syntax/strucre, do we need to stop our effort on AS2.0?
#
hhalpin
syntax is JSON-LD with pre or post-processing
#
deiu
q+ to mention that implementing the user stories requires establishing boundaries
#
Zakim
sees elf-pavlik, bblfish, deiu on the speaker queue
#
aaronpk
.. my understanding was we were going to publish AS2.0 as the social data syntax
#
elf-pavlik
issue-15
#
trackbot
is looking up issue-15.
#
hhalpin
unless there are serious objections
#
trackbot
issue-15 -- AS2.0 Vocabulary in many ways duplicates microformats.org and schema.org efforts -- closed
#
aaronpk
.. if we are not in agreement, do we abandon that effortt?
#
hhalpin
In terms of the vocabulary, we just need to map those replications
#
cwebber2
I agree with Evan that both we have AS 2.0 anyway, and also wondering what the difference this would be from user stories
#
cwebber2
I really don't want to go through a user stories thing again
#
Zakim
sees elf-pavlik, bblfish, deiu on the speaker queue
#
aaronpk
.. seems like we need to move the AS2 effort forward, and if we're questioning that, we need to steb back and re-evaluate
#
rhiaro_
AS2 isn't set in stone right? even if it's not right yet, we can change it to make it better
#
rhiaro_
rather than starting over
#
aaronpk
Arnaud: the user stories don't define functional blocks
#
aaronpk
.. they inform you as to what they might be
#
aaronpk
srsly can someone open a window
#
aaronpk
.. with regard to the social API, i don't think anyone has been arguiing to drop AS2.0
#
aaronpk
.. so if we throw that out, we'd be that much closer to the situation harry was describing
#
cwebber2
PROPOSAL: All specs put forward by the group require AS 2.0 :)
#
aaronpk
.. but in fact, we've even heard that aaron, who makes no use of AS2 today said he'd have a use for it
#
aaronpk
.. so let's not be too dramatic about this
#
hhalpin
notes for AC reps that everyone has to leave in 5 minutes
#
hhalpin
likely in order to get to the AC meeting
#
Zakim
sees elf-pavlik, bblfish on the speaker queue
#
Arnaud
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to very shortly mention extensibility e.g (currently ActivityPump only supports Follow and Like action + relevant collections)
#
Zakim
sees bblfish on the speaker queue
#
aaronpk
elf-pavlik: we didn't get to talk abotu extensibility today
#
aaronpk
.. solid is super extensible
#
eprodrom
elf-pavlik, INCORRECT
#
aaronpk
.. activitypump defines some actions but isn't extensible
#
eprodrom
That's not true at all!
#
aaronpk
.. indieweb has some vocab dilemmas, what do i do if i get terms i don't know how to render
#
hhalpin
+1 extensibility
#
Arnaud
ack bblfish
#
Zakim
sees no one on the speaker queue
#
hhalpin
-1 discussing it endlessly
#
hhalpin
We have URI-based extensibility which should work with ActivityPump as is
#
eprodrom
"8.2 Activities The core of any [ActivityStreams] based protocol is activities within. Users post activities to their outbox, from which they are distributed to recipients' inboxes. ActivityPump places no restrictions on the activities which may be distributed; however, it defines certain activities with special behaviors"
#
aaronpk
bblfish: if we can reuse as much existing technology, ontologies, then we can get out a whole bunch of problems
#
rhiaro_
implementation++
#
eprodrom
elf-pavlik ^^^
#
Loqi
implementation has 2 karma
#
aaronpk
.. i was just loking at schema.org
#
hhalpin
Micropub has mp-
#
hhalpin
so...
#
aaronpk
.. then i understood what they were doing
#
hhalpin
we have URI based extensibility and the ActivityVocabulary
#
aaronpk
.. so maybe we can get to the core, specify the key integration points and reduce our workload
#
hhalpin
just see what points there are schema.org+microformat overlap with ActivityVocabulary
#
sandro
eprodrom, it'd be good if you could give us a walkthrough of that. How does an enterprise do travel-authroization (the example that came up yesterday) over activitypump?
#
aaronpk
Arnaud: i'd like to close the meeting
#
hhalpin
Not superhard.
#
aaronpk
.. i think we made good progress
#
aaronpk
.. if nothing else, sharing a lot more understanding, which is critical to being able to converge
#
eprodrom
sandro, sure, I'd love to
#
aaronpk
.. so i hope we can buildon that and continue
#
aaronpk
.. i would like people to seriously consider if they are up to being an editor or not
#
aaronpk
.. we don't want people to volunteer unless they are 100% committed
#
aaronpk
.. if you get in the way it's not going to help
#
aaronpk
.. it's not just editing the document, it's keeping track of the resolution...
#
aaronpk
.. answering public comments
#
aaronpk
.. i'm not trying to discourage people , just want to make sure they know what it takes
#
eprodrom
jasnell does a lot of work
#
aaronpk
MEETING ADJOURNED
#
eprodrom
Arnaud++
#
Loqi
Arnaud has 16 karma
#
eprodrom
elf-pavlik yes?
#
eprodrom
What?
#
eprodrom
What are you trying to say?
#
Zakim
-??P2
#
elf-pavlik
eprodrom, we all had amazing meeting here and see a lot of potential to move forward
#
elf-pavlik
i have impression that remotely you might miss some context and i get impression of you grumpy side
#
Zakim
-bret
#
Zakim
-cwebber2
#
Zakim
-Inria
#
Zakim
Team_(socwg)07:29Z has ended
#
Zakim
Attendees were [IPcaller], INRIA, cwebber2, eprodrom, +1.514.525.aaaa, ben_thatmustbeme, bret
akuckartz, tantek, bblfish, jaywink and pfefferle joined the channel
#
elf-pavlik
ben_thatmustbeme do you get form-encoded response from GET /micropub?q=syndicate-to ?
#
elf-pavlik
tantek ^
#
Tsyesika
I made it to the airport!
#
Tsyesika
starts to look at resovling some issues on activitypump
#
Zakim
excuses himself; his presence no longer seems to be needed
#
rhiaro
Congrats Tsyesika :)
#
rhiaro
is lost in Chinatown
bblfish joined the channel
#
rhiaro
is fine with this
#
Tsyesika
rhiaro: i had the normal rifling through my luggage
#
Tsyesika
i think i'm getting use to it
KevinMarks joined the channel
#
elf-pavlik
going offline ...
#
Tsyesika
oh cool looks like evan has started implementing https://github.com/w3c-social/activitypump-server
#
cwebber2
Tsyesika: fast! :)
#
cwebber2
guess i have to learn Go
#
Tsyesika
just thinking the same thing
#
Tsyesika
their hash map looks weird
#
Tsyesika
defining a map inside a ma
#
cwebber2
oh well, I kind of wanted to learn it anyway!
#
Tsyesika
wanted to learn rust properly
bblfish and melvster joined the channel
bblfish joined the channel
#
elf-pavlik
sadly not JSON-LD lib for Go yet :( http://json-ld.org/
bblfish and LCyrin joined the channel
#
ben_thatmustbeme
same for mp-action