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.
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.
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
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
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!
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.
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
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