Ryan Barrett

yup! and then get at least some preliminary consensus on http://microformats.org/wiki/irc and/or https://indieweb.org/discuss that this is the right direction.

great conversation! also, just fyi, it would probably fit better and get better feedback on [#microformats IRC](http://microformats.org/wiki/irc) and/or https://github.com/microformats/microformats2-parsing/issues.

I'd love this too! sadly there's no comprehensive way to get all events on all issues that involve you. i can get a few beyond comments, best effort, but only...

here's the subset in the notifications API, ie that we can reasonably get: https://developer.github.com/v3/activity/notifications/#notification-reasons > assign You were assigned to the Issue. > author You created the thread. > comment...

understood! which status changes above specifically are blocking you? and as mentioned here and in #915, one big thing we're waiting on here is to see example posts in the...

thanks! beyond github API calls, the other thing we'll (i'll) want to see first is clear mf2 and existing examples in the wild. great to have this issue for collecting...

@dshanske understood! you can still use bridgy publish to own [posting issues, comments, reactions, and labels](https://brid.gy/about#publish-types), of course, as other people like @tantek have done for years, but you're right...

hey, yes! you can enter the URL for one of your old tweets, or blog posts if they have [syndication links](https://indieweb.org/u-syndication), into the _Resend for post_ box on your Bridgy...

right! understood. for any tweet that links to any page on your site, you can enter the tweet's URL into the _Resend for post_ box on your Bridgy user page,...

heh, yes. as mentioned, if your post doesn't have a syndication URL, put each _tweet URL_ into _Resend for post_. i tried it with https://twitter.com/BryanWilhite/status/1212842573535989760 just now, and https://brid.gy/twitter/RehanSaeedUK shows...