#[jgarber]!tell aaronpk Just confirmed the indieauth.com TLS certificate expired tonight: “Not Valid After Saturday, June 30, 2018 at 7:59:59 PM Eastern Daylight Time”
#[jgarber]I’m running my website locally (it’s a Rails thing running on `localhost:3000`). With IndieAuth, the redirection flow works (through IndieAuth then GitHub) and I can successfully log in on `localhost`.
#[jgarber]Based on your statement from a few minutes ago, IndieLogin won’t support that development workflow.
#aaronpki'm confused, where are you logging in to?
#[jgarber]I’m working on some features on my personal website (sixtwothree.org). It’s a Rails app and before deploying anything, I work on it locally. Rails apps run in development mode on `http://localhost:3000`.
#[jgarber]On `localhost:3000`, I can step through the exact same auth flow (via IndieAuth) as I would on the live version of the website and I end up authenticated and back on `localhost:3000`.
#[jgarber]> was there a reason you didn’t integrate a regular github or twitter login button via omniauth?
#[jgarber]Maybe? This version of the site was my first foray into IndieWeb stuff several years ago.
#[jgarber]The vibe I’m getting is that I’ve done something rather novel here without realizing it…?
#aaronpki'm skeptical of allowing this sort of use of indielogin.com, since that wasn't really the intent of it. it sounds to me like this might be something better suited to the other half of what indieauth.com provides
#aaronpkbut I also hadn't actually considered this use case for that new service
#[jgarber]…and now I’m confused as to the purpose of IndieAuth and IndieLogin…
#[jgarber]Hah, did I bend the “sign in with your domain” back in on itself?
#aaronpkit's more that I want to avoid getting back into this confusing situation that indieauth.com is in
[jgmac1106] joined the channel
#[jgarber]No worries. Seems like I should be looking at other options for authenticating myself to my own site.
#aaronpkindielogin.com doesn't ever issue access tokens, which you need for micropub
#aaronpkmy plan is to write an "IndieAuth server as a service" and launch it at myindieauth.com, and that is what you'll be able to use for building a micropub server
#[jgarber]Ah, so IndieLogin is identity not authorization?
#aaronpktell you what, if you're willing to be a guinea pig for a few months, i'll enable your domain and localhost:3000 on indielogin.com, as long as you are willing to eventually change that to myindieauth.com if I decide that ends up beign a better place for the part where you want to log in to your own site
#[jgarber]If you think it’s a worthy pursuit for IndieLogin, I’m game.
#[jgarber]But wouldn’t that then bring along the authorization baggage to IndieLogin? Or have you got an idea or two up your sleeve?
#aaronpkwell indielogin still won't help you with the micropub side of things, but it will let you log in to your site
#[jgarber]Hrm, I don’t want to railroad IndieLogin’s development.
#[jgarber]IndieAuth is working well enough right now (and will continue to do so until it goes away).
#aaronpklocal development of things that indielogin is intended for is still a valid use case
#aaronpkwhat I end up doing is running my own local copy of IndieLogin where I have a different set of whitelisted client IDs, but that isn't really sustainable if I'm running this as a service for others :)
#[jgarber]I’m game to give it a shot then if it’s helpful!
#aaronpkit's so that your auth code verification bit doesn't get tricked into sending the auth code somewhere else, since you should first check that the state matches what you expect before verifying the auth code
#Loqi[jgarber623] micropub-endpoint-ruby: A Ruby gem for discovering a URL's Micropub endpoint.
#[jgarber]There are some differences in the Webmention and Micropub endpoint discovery specs that we might consider bringing into alignment. I think there’s an issue on the w3c/Micropub repo… I was looking at that earlier today.
#[jgarber]aaronpk Thanks for merging that webmention-client-ruby PR! I’ve got a few more queued up. I’ll get to that tomorrow, though. It’s getting late here on the East Coast.
#aaronpklooks like you might be able to collaborate with barryf on further development of webmention-client-ruby! have you chatted yet?
#[jgarber]I pinged him here at some point in the last week, but haven’t heard anything.
#[jgarber]!tell barryf Hey, buddy! Drop me a line when you see this. I’d like to pair up on some of the IndieWeb Ruby things if you’re interested.
#[jgarber]aaronpk Also think I got IndieLogin mainly working. I’m not properly using `state` yet, but was able to (with a few changes on my side) get to where I can log in locally.
#gRegorLoveAdded some consuming of read-of to indiebookclub: query parameter read-of will take a URL and parse it for h-entry.read-of and populate the form. If that's not found, it falls back to checking for h-cite.
#Loqi[[eddie]] Well, I didn’t get the final couple of features done that I wanted to for Indigenous, but I didn’t change the pre-order date either, so for better or worse... it’s live! 😱
loicm, [manton], davidmead, [jgmac1106], [Vanessa] and iasai joined the channel
#[manton][schmarty] Is there a definitive "announcing IndieWeb Ring" post to link to? Added initial support for web rings to Micro.blog today. 🙂
#schmartyOh man. There will have to be, soon! I just got home last night after OSBridge and am dealing with some pet problems at home though :/
#[manton]Oh, sorry to hear it. No rush of course. (We've waited 15 years for the return of web rings, so a few more days, weeks, or months will be fine.)
[barryf] joined the channel
#[barryf]Hey [jgarber]! Sorry to have missed your pings. I’ve been tied up with a new baby and switching jobs for the last few months. I may be able to help with some Ruby in between things though.
#Loqi[barryf]: [jgarber] left you a message 11 hours, 6 minutes ago: Hey, buddy! Drop me a line when you see this. I’d like to pair up on some of the IndieWeb Ruby things if you’re interested.
[jgarber] joined the channel
#[jgarber][barryf] Not a problem! Was catching up on your site this morning and saw the big life changes. Congratulations all around! 🎉
#[jgarber][barryf] Thinking about a workflow for alerting folks to review requests without being annoying. Would you be okay if I requested reviews on PRs on GitHub?
#[jgarber]Same question for any other fellow Rubyists here. 😄
#[jgmac1106]Was going to be my IndieWeb summit project, but ended up doing community support.
#[jgmac1106]Installed FrancisCM will finish build after vacation
#[jgmac1106]My partner built our app on RoR trying to drag him into indieweb
loicm joined the channel
#[jgarber][jgmac1106] Nice! On Ruby 2.5.1 no less. Nicely done!
#[jgmac1106]Launching Ruby and installing gems is fun
#[jgmac1106]Wanted to leave summit with RoR solution with static page gem but helping WordPress took precedent
#[barryf][jgarber] Thanks very much! Sure, I’d be happy to help as long as you don’t mind slowish responses. I had a few ideas back when I last hacked on it.
#[jgarber]I’m hoping there’s a small handful of folks interested in Ruby-things and we can keep things moving forward without any one person having to be the gatekeeper/blocker/etc.
#[jgmac1106]Plus we like the two eyes before PR approach
#[jgarber]Related to that… I’m going to add a section to /Ruby: “Support” where folks can register their interest/availability.
#[jgarber]e.g. “jgarber is knowledgeable in Ruby, Rails, Sinatra, and available for PR reviews. His github handle is…”
#[barryf]I know [gerwitz] is developing a fork/rewrite of Transformative. He may be interested too.
#[jgarber]Done! [barryf] [gerwitz] [jgmac1106] and anyone else interested in Ruby, please add yourself to the “Support” section on /Ruby if you’d like to be tagged in on code reviews, etc.
#[jgarber]I listed my skills (such as they are), GitHub username, and what I’d be interested in helping with, but don’t consider that a template for your own addition.
#[jgarber]☝ Also: [deeden] may be interested in this, too.
#Loqimanton has 6 karma in this channel (59 overall)
[chrisaldrich] joined the channel
#JeenaHm I can't log in to https://xn--sr8hvo.ws/ I'm getting "ReferenceError: Micropub is not defined" and because there is no link to the author on the page I have no idea who to talk to about it.
#ZegnatTalk to schmarty about it. Though that sounds as if he is in the process of tweaking things.
#aaronpkI don't send vouches yet, I just receive them
[dougbeal] joined the channel
#aaronpksomehow I still get a few spam pingbacks leaking through, and if you look at my referer logs those are just a total mess of spam, so i'm not convinced that's much of a useful signal
#GWGThere aren't a lot of implementations because of the lack of suggested ways to send them.
[Vanessa] joined the channel
#aaronpkyeah. there's a big difference between a spec and an implementer's guide
#aaronpkthe Vouch spec is correctly defining the minimum it needs for interop, but as you're seeing, that leaves a gaping hole in other parts.
#aaronpkpstuifzand: your photo of your like isn't showing up on my post because it's running through your media proxy and that blocks it unless it's got a referer header of your own site
#GWGaaronpk: To do that, I have to figure out what to suggest people do to generate vouches.
#ZegnatI'd say definitely query webmentions you have received. I think that's a pretty good sources for vouches, and one you already have available in WP, I assume?
#GWGThat would mean when the webmention comes in, I should be storing more information though, right?
#ZegnatYou would need to able to query your webmentions for the domain they came from. Then when you are sending a webmention to a page, you query on the domain, and send the last webmention you received from it as vouch
[manton] joined the channel
#ZegnatSo you may need a separate column for domains to query on, although that might already be possible if you just have the URLs...
#GWGZegnat: I have the source URL for every webmention received.
#dgoldgdpr issues, certainly, probably violates the new california law too
#ZegnatIffy as in, we couldn't come up with a clean way of generating it.
#aaronpki'm not saying Vouch is actually the best solution, it just sounds like there is some misunderstanding of the specific problem it was created to solve
#ZegnatGDPR issues with storing link relationships, dgold?
#GWGWell, the simple solution is to encourage sites to do the work for you
#GWGFor example, if I have a followers page on my site.
#GWGI know chrisaldrich, snarfed, and a few others are posting blogroll/following pages
[schmarty] joined the channel
#[schmarty]woohoo! 🕸.ws now uses indieauth for authentication only, using a questionable fork i made of grantcodes' micropub-helper that drops all the tokens and scopes and whatnot.
#aaronpkthe problem that will happen tho is if all people have to do is log in, then you might end up with a bunch of people logging in to try but then never actually adding the link
#[grantcodes][schmarty] actually might make sense to separate out the auth part of micropub helper into another module for this use case. But also include it in micropub helper by default
#[schmarty]is really having trouble balancing 🕸 launch with getting TWITIWAE done
#Loqischmarty has 15 karma in this channel (91 overall)
#[schmarty]oh, i also set up mocha for tests but they only test against my live site right now, haha
#[schmarty]that's why it's on my private git host and not github
#[grantcodes]I did start writing tests for micropub helper but never got around to finishing them...
#[grantcodes]Would be good to work with you on other indieweb express middleware, as I think my micropub endpoint is going to end up including token and auth endpoints too in the future
#[schmarty]grantcodes: that'd be great! i am pretty far behind on best practices for this stuff, so i'd love some extra eyes and hands as i'm stumbling through.
#Zegnataaronpk, I do like that it should enable the use of wildcard with any domain no matter where the dns is from. But it still looks like a lot of overhead. I think I’ll stick to non-wildcard certs for now
#aaronpkoh definitely if you don't need wildcard certs don't do this
#aaronpkbut at this point I would benefit a lot from using wildcard certs on a couple domains so I'm trying to sort it out
#ZegnatI start different subdomains on zegnat.net for all experiments. But sometimes I don’t feel like doing all the steps again and end up dumping it on an already existing domain. Having a wildcard cert on that domain would get rid of one step, and would just make that easier for me.
#ZegnatBut current setup admin-tax is too high. I’ll stick to the extra certbot call
#Zegnatfor subdomains on different servers you should have separate certs. For security reasons you don’t want the same cert (the private key part, really) on multiple servers.
#aaronpkfor example *.micro.blog is way easier done as a wildcard cert instead of making a new one for each user that joins
#gRegorLoveI should write up a post with some Vouch thoughts and what I've implemented. I think I've only written on the wiki very briefly, then IWS discussion.
#aaronpkMaybe I'll try analyzing the referers again and just filter out all google URLs. The last time I looked the vast majority of my data was ugly google URLs
#GWGI meant Google Analytics, which is why I capitalized.
#GWGI was thinking of trying this just as an experiment. I could write a plugin that does this in an hour as I have all the relevant code.
#LoqiIt looks like we don't have a page for "goaccess" yet. Would you like to create it? (Or just say "goaccess is ____", a sentence describing the term)
#LoqiIt looks like we don't have a page for "GoAccess" yet. Would you like to create it? (Or just say "GoAccess is ____", a sentence describing the term)