wolftune, squeakytoy2, RussNelson and nelson joined the channel
#nelsonTwo things, "selfdogfooding" first. It's kind-of a strange term, yes. Maybe CIMBY? Coding In My Back Yard. Advantage? Everybody knows what NIMBY is, so telling them that the C is for Coding should get the idea across.
#nelsonDisadvantage is that NIMBY is a bad thing, unless, of course, *you* are the NIMBY.
#GWGnelson: Dogfooding is a long standing term. That isn't always a good reason though, admittedly.
#Loqidogfood in the context of the indieweb, refers to the software practice of "eating your own dog food" but in particular with using your own creations on your own personal site that you depend on, day to day https://indiewebcamp.com/dogfooding
#nelsonOkay, on to the second thing. I love IndieAuth, but it isn't working with Google+. Yes, I saw the caution, but I've got it in Profiles, not links.
#nelsonOne thing I noticed is that Google+ is using rel="me nofollow". Is that going to screw up IndieAuth?
#aaronpkGerman is good at taking complex concepts and turning them into a single word, right? Maybe there's a german word we can use :)
#GWGIt was inquired about yesterday. I think someone was going to check.
#nelsonUrgh, X-Chat inserted a space where it should be /"
#GWGSo, nelson, what brought you here today? I like to hear people's stories.
#nelsonI've got an account on Known, which I don't use very much because most of my photos get posted to a Facebook group. I want to figure out how I can post photos to my own blog, to the Facebook group, and to Flickr.
#GWGAh, the POSSE dilemma. I know Known supports Facebook. It doesn't support groups? I thought when I saw a demo of it that it did.
#nelsonaaronpk: that's weird. curl isn't logged-in, so we should be getting the same thing. When I run it, I get 25951 characters of which several are the string:
#nelson<a class="OLa url Xvc" href="http://russnelson.com/" rel="me nofollow" target="_blank" title="My home page">My home page</a>
#nelsonyes, I saw @t's name associated with IndieAuth and took a shot in the dark.
#GWGBut it looks like tantek asked KevinMarks if he could look at it. I guess he might still have contacts there.
#nelsonGWG: I don't like how everything used to be interoperable using published protocols, but now you're supposed to log in to a silo and use their proprietary API.
j12t and singpolyma joined the channel
#nelsonaaronpk: this is barfalicious, but: nelson@d2:~$ curl https://plus.google.com/+RussellNelson/about | grep 'href="http://russnelson.com/" rel="me nofollow"' | sed 's!.*<a class="OLa url Xvc" href="http://russnelson.com/" rel="me nofollow" target="_blank" title="My home page">My home page</a>.*!<a class="OLa url Xvc" href="http://russnelson.com/" rel="me nofollow" target="_blank" title="My home page">My home page</a>!'
#GWGnelson: I agree. And sometimes the API is restricted. It would at least be doable if the API was easy to work with
#GWGLook at Bridgy. The fighting to get API access.
#nelsonI could handle logging in IF I didn't have to learn a proprietary API every time.
#aaronpki'm pretty sure that link isn't actually in parsable HTML. i suspect it's in a comment block or some other script thing
#nelsonGithub found it in the comment I posted to that gist.
#aaronpkgithub is likely munging the crap out of that html before rendering it
#aaronpkso they may have removed a script tag or whatever
#nelsonAhhhhh, interesting, when I load that html back into Chrome, it shows me about the same thing you pasted in the gist.
#nelsonI think your theory is correct. I'll look at the HTML and see if there is a work-around.
#aaronpksadly this means any solution is going to involve hard-coding specific behavior for google+, so at that point might as well use the API since it will be less prone to breaking
#GWGaaronpk: I heard they have a new API for that somewhere
#sknebelwow, webstorm nearly craps itself trying to make sense of that file
#tantekaaronpk, if it stops working via curl, we should just document that as an Issue on /Google+ and note that Google has broken their markup, again.
#tanteknelson, are you able to use an alternative for now like GitHub?
#aaronpki *think* that is the case but trying to actually confirm it
#nelsontantek: I'm able to use five alternatives. :-) Every one but G+ works, and G+ works now.
#tantekThe will.i.am problem refers to the problem of auto-linking plain domains on ccTLDs leading to false positives, exemplified by the musician will.i.am (actual spelling) who does not own the "i.am" [[short-domain]], and the likely reason why Twitter does not [[autolink]] ccTLD domains.
#tantekThe will.i.am problem is the problem of false positives when auto-linking plain domains on ccTLDs, exemplified by mentions of the musician will.i.am (actual spelling) who does not own the "i.am" [[short-domain]], and the likely reason why Twitter does not [[autolink]] ccTLD domains.
#singpolyma"IndieWebCards/0.5 like Mozilla or IE or is it Trident? Maybe Presto. Some WebKit influence. Does you sniffer like Blink? Firefox and Iceweasel and Dillo and lynx. Mozilla again."
#LoqiA private account is a silo account where all posts on its profile are private, and only approved followers (or friends) can see posts https://indiewebcamp.com/private_account
#KevinMarkssingpolyma, you've spent more time with gnusocial - does the twitter lookalike skin originate with quitter.se?
#singpolymaKevinMarks: I believe Qvitter (the js;dr twitter-alike GNU Social plugin) was developed originally for quitter.se -- the guys behind quitter.se are also behind the Qvitter github, etc