#gRegorLoveHm, I thought you could include an arbitrary github repo in composer.json. Looks like it expects it to be a fork of something on packagist, though, and uses branch dev-master.
#bearusing mf2 to parse ircpeople for domains to scan for stats just showed me a bug in some code - wooo!
#bearh-card urls with /path items I'm not handling cleanly it seems
lukebrooker, Erkan_Yilmaz and gRegorLove joined the channel
#gRegorLoveaaronpk: The repo doesn't have to be on packagist, but composer expects it to be a fork something on packagist, with its own composer.json file. I tried including microformats/test as is and composer said "No valid composer.json was found in any branch or tag of https://github.com/microformats/tests,
#gRegorLoveForked microformats/test and got it working with composer. Thing that took me a while to figure out was had to specify "@dev" stability in the root composer.json or else it wouldn't include my forked repo.
friedcell, loic_m, tantek, mxuribe, squeakytoy2, singpolyma, snarfed and mlncn joined the channel
#aaronpk!tell gregorlove you don't have to ever publish it on packagist.org, but you do need a composer.json file. composer != packagist. also it expects to be able to find a git tag to mark a version, otherwise you have to specify dev like you found.
#snarfedso, once bridgy loses access to the instagram API, we can switch to scraping, but we won't have a way to tell whether a user owns a given account, eg for signup and delete
#snarfedthe options i see are 1) drop auth or 2) indieauth
#aaronpkhm not really. I'm also not super happy with the current indieauth logo.
#snarfedok. the button thing isn't urgent, but it'd be nice eventually, so let me know if you plan to change the logo soon. otherwise i'll hack something together
#aaronpki bet the current logo would work better if it weren't outlined, just the shape, so if you do make a button with it, try that
#tanteka standalone "caldav/carddav server" is an inappropriate focus on plumbing
#tantekthose should just be features of indie contacts and indie calendar
#singpolymaI guess so. It just makes iCal and vCard files on disk on my server and then I do whatever I want with those
rrix, snarfed and glennjones joined the channel
#snarfedbridgy beta testers (kylewm aaronpk tantek KevinMarks), your instagram accounts are now scraping instead of using the API. please let me know if anything odd happens!
#gRegorLoveaaronpk: Yeah, it took me far too long to realize composer is using tags, not branches. I kept wondering "why isn't 'master' working?"
#LoqigRegorLove: aaronpk left you a message 3 hours, 58 minutes ago: you don't have to ever publish it on packagist.org, but you do need a composer.json file. composer != packagist. also it expects to be able to find a git tag to mark a version, otherwise you have to specify dev like you found. http://indiewebcamp.com/irc/2016-03-24/line/1458828897915
#gRegorLovePretty sure I've got the microformats/test suite working, though. Just going to clean it up a bit, submit a PR to add composer.json to it, then a PR to php-mf2.
#kylewmso the plan is, use indieauth to verify they own the domain, and then check for bidirectional rel-mes to verify they own the instagram account?
#snarfedkylewm: right. i'll show you the bridgy branch with what i've done for UI so far.
#snarfed(i started down the road of just typing in instagram username, without indieauth, but then realized we need auth)
yakker joined the channel
#snarfedthe site fetch and bidirectional rel-me check would probably be in bridgy though, unless you think of a reason and good API for it in o-d. seems possible, but unlikely.
#Loqi[kevinmarks] meant to say: well, oauth-dropins returning an h-card for the user would also be nice; at the moment you need to do that per-login method
#snarfed[kevinmarks]: you mean a translated h-card, from their silo profile? granary definitely does that right now
#snarfedo-d is currently independent of mf2, but we could definitely think about how to add that without duplicating granary's code. feel free to file a feature request!
#snarfedtechnically yes someone could MITM your http site and hijack your login, but indieauth'd bridgy accounts won't support publish, so we think the threat is very small