tantek, squeakytoy, squeakytoy2 and pfenwick joined the channel
#ben_thatmustbemenot at the moment. Been working on getting webmention set up
#ben_thatmustbemealso trying to convince a friend of mine to take a look at marking up his site with mf2 at least and get him doing some indie web stuff
#ben_thatmustbemehis first complaint was that the indiewebcamp site doesn't work well on mobile
#kbsoh, just for finding out all the 'validated' pages for a given profile
#gRegor`If it's authorship, the rel=me should have an h-card, yes. Is that what you mean?
#kbssort of more like what indieauth needs to do - given a starting profile page, find all the linked profile pages with a chain of links back to the starting profile pages
#kbsso for example, if I give it snarfed.org/about
#kbsI expect it to give me back ryan's twitter page, g+ page and so on
#kbsbut [to take that example] although [in theory] snarfed.org/about is ryan's "profile" page - the rel=me links on the twitter and g+ page actually point back to snarfed.org rather than snarfed.org/about
#kbsso what's happening [I think] is that while in theory only "profile" pages should have a rel=me link -- both as the source and the target -- in practice, this is not the case
#kbsbut the theory of rel=me is not actually true based on how people are using it. Essentially I have to pretend rel=me and rel=author are equivalent, for all practical purposes
#gRegor`If I'm parsing a page for mf2 to pull in webmentions, for example, I look for an h-card associated with the post as the author. If I don't find it, I look for rel=author and pull in the h-card from there.
#kbsI can no longer prove that gregorylove.com/about is associated with github
squeakytoy2 joined the channel
#kbsbecause there's no rel=me from gregorylove.com to gregorylove.com/about
#gRegor`I guess I see how it can be a problem with domains that have multiple users / authors.
#gRegor`It doesn't seem to be a problem for single-author sites like mine (and most of ours)
#gRegor`But I guess if we're building general-use scenarios, yeah, that's a problem.
#kbsit's because of an accident of implementation I think - when you use indieauth, you probably provide gregorylove.com rather than gregorylove.com/about
#gRegor`E.g. systems shouldn't assume single-author sites
#gRegor`I put rel-me links in the footer, hidden, so I couuld use indieauth, yes.
#kbsyou should ask kevinmarks or tantek when they show up next for the distinction - I had a long interesting conversation with kevinmarks today afternoon when I finally realized what the theory was, and also why it's almost irrelevant because nobody actually makes this distinction
#Loqikbs meant to say: and then some discussion about why this doesn't really happen in practice, etc
#kbsso also in theory, apparently we should all be logging into indieauth using our /about pages, should our "about" page actually not be the baredomain itself. I think part of the confusion is probably because tantek uses his baredomain to represent what we'd all consider an 'about me' page
#gRegor`Hmm. I think I get the gist of it, but still a bit confused. I'll think about it some more. :)
#kbsand I say, hey, this person looks interesting, find out more about him or her
#kbsand let's say, I end up in your /about page, and decide I'd like to know more about you
#kbsThe tool starts crawling all the rel=me links, and checks that they eventually point back to the starting point [that's how I can tell it's "legit"]
#kbsright now, if I crawl your baredomain, it "works" - because you've linked it in such a way that I can see your associated domain(s)
#kbsIdeally, I'd do something quite simple - find the 'author' on any page
#kbsthen chase rel=me links from there - which also doesn't quite work if I happen to start from your /about page
#kbsso I have to do some unholy hacks of merging rel=me and rel=author links and look out for specific domains before anything really works as intended
#kbsI do think that any reasonable person would probably start with the baredomain for any indieweb site
#kbsand that also does work simply because people just want to get indieauth working :)
#kbsgRegor`: yea - that's the intended purpose of rel=me links anyway, if you want to be precise about those tages. But as you also pointed out right at the top - in practice people aren't making this distinction
#kbsso I think any tools that actually use the data are having to make some adjustments
#Loqikbs meant to say: gRegor`: yea - that's the intended purpose of rel=me links anyway, if you want to be precise about those tags. But as you also pointed out right at the top - in practice people aren't making this distinction
#kbsit'd also mean that you'd have to login with /about rather than the baredomain into indieauth - I don't think it's chasing rel=author links
#KevinMarksI think bare personal domains are OK as rel-me targets
#KevinMarksand indeed personal blogs which are often subdomains
#kbsI think the confusion is also because both kevinmarks.com and tantek.com use the baredomain as their 'this-is-me' page. But (for example) ryan uses snarfed.org/about - so as I understand it, ryan would be linking his various rel=me targets from and to snarfed.org/about
#kbsand rel=author from everywhere else to snarfed.org/about
#GWGBut kbs, to go a bit philosophical...aren't you more than just your bio?
#kbs(or, he could mutually rel=me link snarfed.org and snarfed.org/about I guess, dunno)
#GWGFor example, my problem is that I am an author all over the place.
#gRegor`kbs: I guess depending how far down the rabbit trail you want to chase rel-me links, if you started with my /about, followed the link to my github, followed the link back to my root /, then followed the rel-me links from there, it would finally resolve. :)
#KevinMarksthere is s presumption that if you own / you own/about surely
#KevinMarksI think the separate about pages would make more sense for something liek techcrunch
#kbsKevinMarks - hm - does that work for something like a hosted site [like github]
#kbssomeone could arguably claim / without necessarily claiming ownership over /user ?
#KevinMarkswell I have github.com/kevinmarks/ and all below
#kbsto first separate out the 'how to make it work' from 'what should the rel tags be' discussion :) to take a specific example, let's say snarfed.org is a personal domain and snarfed.org/about is the 'about-me' page
#kbsin theory at least, should external rel=me targets go to snarfed.org, or snarfed.org/about ?
#gRegor`I think if it points to snarfed.org, the implication is "this profile is associated with the entire domain and sub-pages"
#gRegor`If it's a multiple author site, then the rel-me links should go to a specific user page.
#gRegor`So in absence of rel-author elements on my site, once you follow the loops and verify my root is associated with the external profiles, you can implicitly assume the original /about is as well.
#gRegor`Er, rel-me should be rel-author two chats up.
#gRegor`Corrected: If it's a multiple author site, then the rel-author links should go to a specific user page.
#kbsI do agree that if one assumes claiming ownership of a rel=me over a url is equivalent to claiming ownership over all urls with a longer suffix, that's indeed the case
#gRegor`That said, I don't like the idea of making systems have to go through loops like that - 4 HTTP requests - just to confirm my /about is indeed associated with my twitter. :)
#kbsit's isn't clear to me anyway, that the rel=me links are intended to claim anything like that
#kbsthough in practice that's what I effectively end up doing...
#gRegor`True. I believe we're talking about additional information that can be extracted from rel-me relationships, outside their base purpose.
#kbsit's a tricky, because it's used for validating claims about site ownership [eg: indieauth] and my cynical mind usually jumps to ways this could be abused
#kbsso I think gRegor` is pointing out that a rel=me claim on http://example.com/page1/page2 is implicitly claiming they own everything "underneath" page1/page2
#gRegor`GWG: implicit information about paths below the "verified" link. E.g. my twitter profile links to gregorlove.com/, so once that's validated you can assume my twitter is also associated with my /about page.
#kbsand not everyone has their profile page sitting at the root of their 'set of owned pages' on all sites
#gRegor`Here's my main question: Why do you need to verify gregorlove.com/about is associated with my Twitter, when you can follow the rel-me loop and verify that gregorlove.com is associated with my Twitter?
#kbsgRegor`: that happens only if I happen to start with the /about page to begin with
#kbsI guess I'd need to find the smallest subset of sites or something, and it still doesn't 'make sense' to me :) plus.google.com doesn't have any profile info, and I shouldn't be taking that sort of link into account
#gRegor`So you start with the g+ and want to verify the domain it's associated with?
#kbsyea, sorry . I start with plus.google.com/+user -> somedomain -> plus.google.com
#kbsI want to find the pages that are 'owned' by the same user
#kbs... have to disappear here, ... will think more too :)
#gRegor`1) Find rel-me from g+ profile and load that page A 2) Look for rel-me in page A that has the base domain you just came from ('plus.google.com'). If it matches where you just came from, verified and halt.
#gRegor`3) If no rel-me found on page A, look for rel-author on A and load that page B
#tantekis this about rel=me in general or RelMeAuth / IndieAuth in particular?
#kbsrel=me in particular. If someone has a personal domain with a separate /about page - should all the external rel=me targets point to the /about page?
#tantekthere's also microformats.org/wiki/relmeauth if that helps
#tantekso it's ignorable from an indieauth perspective
#tantekso we *could* try to make indieauth work with entering your domain/about - but no one's presented sufficient evidence that it's worth it - so meh
#kbshm. I guess as a model of domain identity, I'm trying to follow github.com as owning github, and for me to own github.com/user [ie, as being the target of appropriate rel=me urls]
#tantekthough the algorithm says theoretically how it could work
#tantekkbs - why should indieauth support silo-auth use case like that? quite the opposite, not worth spending any time on it.
#kbsnot indieauth - just trying to understand what the target of a rel=me means
#tantekI mean, ok for github to be an ephemeral auth provider, just not a canonical identity
#tantekkbs - rel-me has to be symmetrical in order to "work"
#tantekand as such, can theoretically work between any two URLs that rel=me link to each other
#kbsyes, but now there's an implied understanding that linking to a top-level rel=me also gives ownership of all paths under that top-level rel=me target
#kbsbut if I rel=me to youtube.com/user, youtube.com could rel=me mutually to google.com (say). Now, who really "owns" youtube.com/user is a bit perplexing to me
#kbsdo let me know the philosophy as you figure it out :) much more entertaining anyway
#kbsat least, I _think_ one thing is that family.com/son and family.com/daughter doesn't play nice with indieauth - but it works with subdomains, as GWG poitns out
#GWGI've always found understanding concepts to be more important than protocols for how I approach things.
#KevinMarksmu uncle set up marks-family.co.uk with really bad URLs for all of us plus frames layout
#kbsif you selectively go marks-family.co.uk/kevin [rel=me] g+/kevinmarks [rel=me] marks-family.co.uk (bare domain) - do you also get to assert indieauth ownership over marks-family.co.uk/dad ? :)
#GWGKevinMarks, it isn't the idea of them. It is the fact I have a gmail and an apps address, and now under the new Google Plus philosophy, every account wants me to create a Google Plus profile, and I can't tell the thing I already have one, and to use that one and stop asking me to join.
#GWGBut the Google Plus revolution was long after you were involved in Profiles.
#GWGWell, I know how hard some of these things are to manage, and how many different problems Google is trying to solve.
#GWGThat doesn't mean it doesn't annoy me when I'm being asked to set up multiple Google wallet accounts.
pfenwick joined the channel
#GWGWhen I can't comment on an Android App because I now need a Plus account, I buy apps through my gmail account, and tied the Google Plus account to my apps account
#GWGkbs: I've spent the last few days trying to figure out how to get people I interact with out of their silos and over onto my site.
#GWGSo, I've been trying to gradually ramp up posting on said site and syndicating it over to the various networks I set up accounts on, backfeeding the responses to my site.
#GWGSo, I have webmentions and the related indieweb tech starting to be set up.
#kbsI'm not much of a social-posting-type guy unfortunately
#kbsbut I have a feeling there are enough here who'll probably be able to share their experiences with that aspect of it [interaction outside silos.]
#GWGBut engagement requires people, who want to hang out on social networks...
cweiske joined the channel
#GWGkbs: I just...if I'm going through the effort to put something out there, I'd like people to actually see it. Otherwise...I might as well talk to myself.
#GWGI don't want to have the readership of a major blog or newspaper. I'd like to at least engage those people I'm affiliated with.
paulcp joined the channel
#GWGSo, the point of syndication to a silo, as Willie Sutton allegedly said, is that is where the people are.
#kbsnot knowing too much about this [I'm a newbie here as well] is it that you aren't able to pull and push comments in and out of (say) facebook easily?
#ben_thatmustbemebasically if friends want to read your content they have to click through to your site, not just read and comment on the syndicated site
#kbsaaronpk: out of curiosity, do you have an analogous example for facebook [meaning, eg: commenting on posts written by others, and not necessarily public, etc.]
#GWGkbs: If it isn't public, then you get into issues of courtesy
#aaronpkkbs: I don't do anything non-public other than strictly private messaging
#KevinMarkswondering if I need a variant of NoterLive for making @pmarca style tweetposts
#KevinMarksthough I need to actually unfuck noterlive first
#kbsbret: I'm afraid to start the conversation :) but I've been fooling around with with discovering all the rel=me linked (and validated) sites for a person, given any one of their profile pages. I have some snapshot here https://dl.dropboxusercontent.com/u/18852638/draft/lindy/lindy.html
#kbsin that process, I discovered that rel=me linking [together with validation] involved some more nuanced understanding of how they work [in theory and practice] and there were many longwinded conversations while people patiently educated me :)
#GWGkbs: I think a discovery webapp tool thingy could have interesting possibilities.
#kylewmintentionally confusing and difficult to navigate, good short term business decision, seems bad long term though
#KartikPrabhukylewm: yup. lets see how the new, new UI goes
#KartikPrabhuof course people will bitch about any change
paulcp_, yaf, bnvk, ttepasse, eschnou, friedcell and snarfed joined the channel
#snarfed!tell rtaibah hey, saw your question on the WP webmention plugin. it tries to send webmentions to every link in a post when you publish or update it.
#aaronpkit's funny, all the people who replied to that post on facebook think the butter idea is weird. but everyone who replied on twitter is like yeah! and is giving suggestions for how to make it better.
#aaronpkbut then i have to make a scheme for generating files and avoiding name collisions and stuff
#snarfedtemporary is definitely a good start. and you could keep it in memory indefinitely, ie until you hit memory pressure or restart
#aaronpkseems like it'd just be easier to throw it in memcache with an 8-char token
#snarfedsure, start with that, see if anyone complains
#snarfedname generation seems doable though, right? source + target, maybe truncated plus an index or timestamp suffix, or maybe hash of source + target?