#[tantek]Slack << How to find your TEAM_ID and USER_ID: View Source on the desktop web slack client ( https://indiewebcamp.slack.com/ ) and search for "team_id" in the source. The after it starting with "T" is your team_id, and just before it the value starting with "U" is your USER_ID
#[tantek]contact << How to make a "Slack chat" link: see [[Slack#See_Also]] for how to construct a one click "slack:" URL that others can click/tap to write you private message on the Slack instance of your choice (like on the [https://indiewebcamp.slack.com/ IndieWeb Slack])
#[tantek]alright, that's enough breadcrumbs for now. Let's see if anyone else figures it out from that and adds a Slack chat button to their /contact page 🙂
#[tantek]LMK if you do and I'll be happy to test it
iasai, tw2113, snarfed, KartikPrabhu, [eddie], [tantek], RenoG and KidReese777 joined the channel
iasai, snarfed and KartikPrabhu joined the channel
#@wsteenvoorden↩️ Volgens mij ook een stuk groter dan de huidige Alkmaarklasse en vol met handige tools zoals een drone, microsub en een werkbootje. Ben benieuwd naar de naamgeving. (twitter.com/_/status/1106804608897294337)
barpthewire, iasai, KartikPrabhu, [kevinmarks], leg, [jgmac1106], gRegorLove, xnxx and [tonz] joined the channel
#[tonz]😄 that message above talks about microsub as in ‘micro submarine’ not indieweb’s microsub
iasai, raucao, cuibonobo, myfreeweb, zoglesby, grantcodes[m], astrojuanlu[m], plindner[m], voss[m], Rixon, [frank], gkbrk and KartikPrabhu joined the channel
#GWGI need someone with reviewing privileges in the Indieweb GitHub community. Anyone?
iasai, [jgmac1106], snarfed, barpthewire and [Rose] joined the channel
#snarfedZegnat: eh, code review and QA aren't the same thing
#snarfedpractices obviously differ, but most places/envs i've worked in, the burden of testing is on the implementer(s), and/or occasionally dedicated QA, not on the code reviewer(s)
#ZegnatVery few open-source projects I have ever been involved in have QA. It is up to the person approving the PR to make sure it is OK to be put on the branch that is being merged to (often master, which will be used to cut releases). So I tend to put a little more weight on those reviews (which may or may not include QA & making sure tests run etc)
#GWGThe question is what our community repo standards are
#snarfedah, sure. for PRs to open source projects from non-committers, yes, the reviewer's burden is higher
#snarfed(having said that, in this case GWG is a committer :P)
iasai joined the channel
#ZegnatGWG, I don’t think we really have standards
#[aaronpk]Some people still call OAuth 2 things that, but mainly the terminology is around grant types now
#[aaronpk]So 2-legged OAuth 1 is replaced by the OAuth 2 client credentials grant
#[aaronpk]I think we shouldn't call this something new, it should still fall under the IndieAuth umbrella, we can call it some other grant type though
#[aaronpk]IndieAuth mainly encompasses the idea that user and app identifiers are URLs, and we normally use the OAuth authorization code grant type
#[aaronpk]So I think we should call this IndieAuth with some other grant type, where we need to name the grant type not name a whole new spec
[Rose] joined the channel
#ZegnatThis has from day one been an extension to indieauth, as it requires all of the discovery pieces from that spec to even work. Naming the grant type sounds like a good idea to me.