#Loqi[[tantek]] no it's technically proprietary Google protocol that happens to use OIDC as a large part of its implementation
#aaronpkexample: Okta is a service that handles user login, by default it uses a built-in user/password database
#aaronpkhowever you can configure your account to connect to external identity providers, including a few proprietary ones, as well as arbitrary ones if they support OIDC
#aaronpkso you can make your okta organization support an arbitrary number of nascar buttons by adding a bunch of external OIDC identity providers
#aaronpkthat's what i mean when I say that OIDC enables delegated sign-in
#aaronpkbut if that isn't supported for one reason or another, then it requires the app developer signing up for a developer account and getting API keys
[fluffy] joined the channel
#aaronpkfor example if you want to use "sign in with google" in your website you have to sign up as a developer, go into the console, register an app, etc
#[tantek]^^^ so I'd call that a proprietary solution wrapped around a standard protocol
#aaronpkbut this is the reason IndieAuth is useful
#[tantek]as someone (a website) consuming "Sign-in with Google", I'd consider that a proprietary "protocol" purely because it's polluted with the proprietary sign-up process
#aaronpkit depends on your definition of proprietary
#[tantek]this is classic "embrace and extend" technique of making something open/standard into something proprietary
#aaronpkthere are a _lot_ of things that are not proprietary about it
#aaronpkthe main argument I hear fo requireing developers sign up for api keys manually is that the services want the developer to agree to their terms of service
#[tantek]it's not even like Google is claiming their proprietary TOS is good for you — it's merely good for them
[benatwork] joined the channel
#@Cambridgeport90Have any #indieweb folks found the Yarns Plugin in #Wordpress to be a good Microsub server? Or am I better off hosting Aperture or something? Advice would be great. Thanks! I'll go for either; it's about time more microsub springs up anyways. (twitter.com/_/status/1151306830251012096)
gRegorLove, [KevinMarks], [Michael_Beckwit, [Rose] and [tantek] joined the channel
[Zegnat], jgmac1106, [jgmac1106] and gRegorLove_ joined the channel
#@SandervHooft↩️ The only thing that's keeping me from migrating from WP to a static site is that I'm not ready to let go of the comments section - love the interaction. Haven't found a decent alternative for this yet. Don't like Disqus' UI, Webmentions are no easy read either. (twitter.com/_/status/1151455164412416000)
#Loqisnarfed has 46 karma in this channel over the last year (79 in all channels)
#[schmarty]so around summit i recall some folks saying they follow the micro.blog discover feed and/or photos feed. ... ... how are y'all doing that? micro.blog/discover and micro.blog/discover/photos don't seem to have mf2 or reference sidefile feeds. 😕
#[schmarty][Franco_Scarpa] when you say "POSSE model for Twitter", what are you including in that?
#[schmarty]at its simplest, POSSE is often manual. post on your own site, then go post the same or similar on twitter, and you're done.
#[Franco_Scarpa]I'd like to create a JSON file of my personal notes on my website. But I want these notes to be published on Twitter using IndieWeb's POSSE model.
#[schmarty]if you have a single JSON file of personal notes, with publish times for each note, you should be able to write a Netlify function to post the most recent note on twitter.
#[schmarty]keeping track of whether the function has already published a given note might be tricky, since netlify functions don't have persistent storage as far as i know.
#[schmarty]kartikprabhu mentioned bridgy publish (https://brid.gy/publish) which takes care of keeping track of which posts are already on twitter, and handling the twitter API itself.
#[Franco_Scarpa]Well, yeah but I'd like to get my hands dirty and write my personal lamba function to get the job done.
#[schmarty]to use it, you sign up with brid.gy (to verify your twitter account and give brid.gy permission to publish on your behalf), then include some markup in your pages.
#[schmarty]the markup has two parts: one to help brid.gy understand the content of the page that you want to post, and the second to confirm to brid.gy that you want it to publish it.
#[schmarty]you'd still need to trigger brid.gy for each new post, which would be accomplished with a netlify function that runs after a successful publish.
#KartikPrabhuif you want to handle the JSON directly, then you might have to deal with the twitter API. bridgy uses the microformats+HTML on your site
#[schmarty][Franco_Scarpa] these days twitter has a fairly in-depth approval process that new apps must go through before they will issue any keys and tokens.
[snarfed] joined the channel
#[snarfed]also single-user twitter apps are the exception. most are multi-user, in which case all of that info is important