#social 2015-05-02

2015-05-02 UTC
#
melvster
i have tried indieauth and helped test the twitter integration, i have helped with the indiecert spec, it's more than a 'tiny' effort
#
melvster
but you're welcome to your views
#
elf-pavlik
ok, so you already can use IndieAuth?
#
melvster
as i said, i support it ... ive been using it on my homepage for years, you could have checked that too
#
elf-pavlik
i got no matches on curl http://melvincarvalho.com/ |grep rel="me"
#
melvster
try escaping the quotes
#
elf-pavlik
my bad! curl http://melvincarvalho.com |grep rel=\"me\"
#
melvster
i was able to log in
#
melvster
maybe they can pick out some data from my home page such as my name and avatar to personalize it
#
melvster
or my friends
#
elf-pavlik
do you use XFN ?
#
aaronpk
showing your name and avatar is a great idea
#
elf-pavlik
or h-card?
#
melvster
i use foaf : img in my rel tag
#
elf-pavlik
ATM I would only expect understanding of
#
elf-pavlik
"https:\/\/twitter.com\/melvincarvalho",
#
elf-pavlik
"https:\/\/github.com\/melvincarvalho"
#
elf-pavlik
"openid.server": [
#
elf-pavlik
"http:\/\/openid4.me\/index.php",
#
elf-pavlik
"http:\/\/openid4.me\/index.php"
#
elf-pavlik
"openid2.provider": [
#
elf-pavlik
"http:\/\/openid4.me\/index.php"
#
elf-pavlik
expecting... from app developed as part of IndieWeb explorations
#
elf-pavlik
just as SoLiD exploration might not understand data people publish with h-card and XFN
#
melvster
when you're parsing "rels" it may help to see what something is relative to
#
melvster
just grepping the string isnt really robust
#
aaronpk
rel values are relative to the page URL
#
melvster
no, they're not
#
melvster
they are relavent to the URL or to a section of the page
#
melvster
this was what facebook said when we had them in the XG
#
melvster
for example comments can come from various sources
#
melvster
but a comment on a post may contain a rel and not be the same as the post itself
#
melvster
it's very good to parse out machine readable data from rels, but it's important to see what the data is relative to as well
#
melvster
need to add a subject to the json
#
elf-pavlik
which JSON?
#
melvster
the one you showed me and pasted above
#
elf-pavlik
melvster, IMO we all can try to put more effort into understanding the other instead of getting upstet that the other dosn't understand me
#
elf-pavlik
and it goes to all of us in all the ways
#
melvster
but it's easier to go from a triple to a double, than it is to go from a double to a triple, because information is lost one way, and not the other
#
melvster
so sometimes even if there is understanding the information loss provides a barrier
#
melvster
that's the advantage of tying rel values to a subject
#
elf-pavlik
on API endpind side, i started compiling also comparison for that https://www.w3.org/wiki/Socialwg/Social_API/Comparison#Endpoint
#
elf-pavlik
micropub+webmention and pumpio seem to have a lot in common
#
melvster
which is already standardized, so sometimes it's less about understanding, and more about implementing an existing standard, then it's possible to run a test suite
#
elf-pavlik
aaronpk, ^
#
melvster
elf-pavlik++
#
Loqi
elf-pavlik has 19 karma
#
melvster
yes i saw that
#
melvster
timbl, as usual, is right
#
melvster
and as usual wasnt listened to
#
elf-pavlik
he makes certain point, you and me can agree with it others not, we also don't agree on various points with each other (ehm HTTP 303) let's try to do our best with what we can agree upon while working in patient way where we don't understand each other
#
aaronpk
pretty sure HTML5 defines rel to be relative to the entire document http://www.w3.org/TR/html5/links.html#linkTypes
#
melvster
trust me im being patient, this stuff was standardized 15 years ago, but im still here, working with what people are doing
#
elf-pavlik
aaronpk, for example in Social WG charter we have JSON not HTML so maybe we shouldn't try to apply HTML5 spec to everything we work with?
#
melvster
well, which ever subject you think a rel is relative to, put that in your @id field
#
melvster
it may be different based on the doctype
#
elf-pavlik
aaronpk, so microformat page with list of people couldn't allow to use rel="me" for each person to link to their social accounts?
#
aaronpk
correct, you'd just use a list of h-cards and multile u-url properties
#
aaronpk
that would be relatively easy to add to this page if we wanted to start listing more than one URL for people https://www.w3.org/wiki/Irc-people
#
elf-pavlik
what about feed agregating posts from many feeds (plantet style), each post can't have it's own rel="webmention" ?
#
aaronpk
that's an interesting idea, but you'd just need to fetch the URL of the post and find the webmention endpoint from there
#
elf-pavlik
so in general nested microformats can NOT have any rel?
#
elf-pavlik
just the top level one can
#
aaronpk
correct, you use regular mf2 properties for describing microformat objects, rel values describe the whole page
#
aaronpk
that's why parsers always include the rel values outside the list of items
#
elf-pavlik
what about again planet type feed, each item can't have rel="shortlink" or even rel="author"
#
aaronpk
u-shortlink and "p-author h-card"
#
elf-pavlik
hmmm... so u-shortlink and p-author in a way duplicate two http://microformats.org/wiki/existing-rel-values
#
aaronpk
in practice people are using the microformats properties more than rel values, with the exception of things like rel=webmention and the indieauth ones
#
aaronpk
that's different
#
aaronpk
you were talking about properties specific to individual pieces like single blog posts on a page
#
elf-pavlik
i think he could put them all in HTTP Head and just use anchor there for each *subject* https://tools.ietf.org/html/rfc5988#section-5.2
#
elf-pavlik
should really go to sleep
#
elf-pavlik
aaronpk, melvster nice talking with you - see you on monday \o/
#
aaronpk
waves!
kylewm, bblfish, KevinMarks, the_frey, the_frey_, jaywink and elf-pavlik joined the channel
the_frey and stevenroose joined the channel
cwebber2, bblfish and the_frey joined the channel
the_frey, the_frey_ and bblfish joined the channel
the_frey joined the channel
the_frey, bblfish, melvster1, LCyrin and Arnaud joined the channel
#
cwebber2
hey elf-pavlik
#
cwebber2
oh, that was a bit of an old o/
#
cwebber2
but hi anyway :)
#
elf-pavlik
cwebber2, hi :)
#
cwebber2
<rhiaro> Can we find a way to pitch how beautiful and harmonious it is that rdf and microformats actually fit together so well? :)
#
cwebber2
<rhiaro> Can we also get a big button someone can push whenever two people start arguing about terminology that indicates "you are actually saying the same thing, stop arguing"
#
cwebber2
yes yes
#
cwebber2
rhiaro++
#
Loqi
rhiaro has 67 karma
#
cwebber2
infinitity karma for rhiaro
#
cwebber2
everyone says they want different groups to come closer together
#
cwebber2
indieweb people and linked data people in theory both express the desire for common ground
#
cwebber2
but there's simultaneously a pushback from certain members of the group from doing a technical analysis, because technical analysis in theory shouldn't happen because implementations win
#
cwebber2
but how can we make our communities work together
#
cwebber2
elf-pavlik++
#
Loqi
elf-pavlik has 20 karma
#
cwebber2
you get karma too
#
cwebber2
thanks elf-pavlik and rhiaro for trying to bridge groups
#
cwebber2
I feel like both of you are doing the hard work of trying to analyze how our groups are different and how they are similar, and that needs some real appreciation
#
cwebber2
so, I appreciate it
#
cwebber2
(that comic from the actually generally safe for work though it doesn't sound like it is from the domain, and ever great http://butthug.com/ ... a fun distraction, if you are in need of some)
#
cwebber2
oh I shoulda checked before I linked, now I'm afraid the second comic currently on that page makes me look wrong!
#
cwebber2
ohhh well.
#
cwebber2
I hope everyone gets along and conversations are productive and the face to face is used as an opportunity to understand each other
#
cwebber2
yes, even from... maybe even especially!... a technical perspective :)
#
cwebber2
indieweb, linked data type people have a lot to learn from each other. High implementability is great. Explicit and clear architecture is great.
#
cwebber2
there's my background cheerleading.
the_frey and melvster2 joined the channel
#
elf-pavlik
thanks cwebber2 :)
#
elf-pavlik
i sit at flat where bblfish and listen to his feedback after he took first look at schema org ....
#
elf-pavlik
my ears start hurting ;)
#
elf-pavlik
a lot of critique, in most places well deserverd
#
elf-pavlik
we do need to stop getting stuck in differences and get better at finding things we can agree on
#
elf-pavlik
and of course i keep failing here *a lot* myself!
#
elf-pavlik
recommended to my by some people presenting at http://apidaysberlin2015.apistrat.com/
#
elf-pavlik
in general i find it important to go to such events and see what people do nowadays
#
bblfish
Well I understand why schema.org do things the way they do it. For search engines it provides a great improvement of data. But for people like us who want to develop light weight JS clients to read data, having strings used in place of URIs, etc... is not going to make our life easy