#cameron1Basically that. Does cool stuff like autoscaling to zero, and it's effectively free for low traffic sites
#[tantek]There are bunch of IndieWeb related services that people have running on App Engine: https://indieweb.org/App_Engine#IndieWeb_Examples but you might be the first person here actually running your personal site on App Engine!
#cameron1it's handy because I host dozens of services on my website
#[fluffy]the Flask endpoint stuff that it provides is geared towards using a session cookie for managing auth, and presently makes it a persistent cookie for Reasons although I’ll probably make that configurable.
#[fluffy]also the downside to using IndieLogin.com is that you need to register your app with it (or run your own instance) and there’s no fast way of doing that; basically you need to ask [aaronpk] and hope he gets around to it 🙂
#[fluffy]IndieAuth itself is a modification of OAuth2, which allows a mechanism for unattended application registration.
#[fluffy]IndieLogin is a wrapper around IndieAuth and RelMeAuth.
#cameron1ahh yeah I've added rel me tags to my site
#[fluffy]The reason I’m writing Authl is that those two use cases didn’t cover all the bases for me and I wanted to be able to support magic email links and other OAuth-based providers (e.g. Mastodon, Twitter) directly rather than via RelMeAuth.
#cameron1magic email links are great, I hope they see more adoption at some point
#[fluffy]I have mixed feelings about them but they’re nice to have all the same.
#cameron1so from what I gather, IndieLogin is a 3rd party which confirms your link between your domain & regular oauth accounts?
#[fluffy]It’s easy to get confused with the terminology, and I’m fairly new to this world myself so let me see if I can do a better job of explaining…
#cameron1Ah it just seemed to me that IndieLogin was a way of avoiding running your own OAuth server
#[fluffy]IndieAuth is a federated identity protocol built on OAuth, which allows for people to use an OAuth login flow to verify their ownership of a domain to identify themselves to someone else.
#[fluffy]RelMeAuth is a federated identity protocol using rel=“me” links on your website to say “ask this other provider to tell you who I am”
#[fluffy]IndieLogin is a *consumer* of IndieAuth and RelMeAuth
#[fluffy]so like, if you want to identify yourself to other sites, you can use IndieAuth and/or RelMeAuth on your site. Since you’ve set up rel=“me” links you already have a de facto RelMeAuth provider set up.
#[fluffy]There are plenty of self-hostable or third-party IndieAuth providers as well.
#[fluffy]If you want other people to identify themselves *to* you, you need to consume IndieAuth and/or RelMeAuth, and IndieLogin.com makes that easier.
#[fluffy]My interest in consuming auth (and why I’m writing Authl) is for private posts.
#[fluffy]IndieAuth is also used for other things like providing authentication for MicroPub and MicroSub, which are rabbit holes you don’t have to go down just yet 🙂
#cameron1one of my plans before I discovered IndieWeb was to integrate Standard Notes with my site, have a specific tag for public posts and automate everything around that
#[fluffy]That sounds like it might be a use case for MicroPub.
#cameron1right now everything is currently stored in markdown files which are read into memory & parsed when the server boots
#[fluffy]heh, that’s not too different from how Publ (my Flask-based CMS) works
#[fluffy]The way I’m doing private posts in Publ is I’m setting up identity/permissions groups that basically just say “If someone authenticates as this identifier, let ’em see it.” With a bit more fine-grained control than that but that’s the tl;dr anyway.
#[fluffy]And I’m just storing it in a text config file that gets read whenever someone authenticates.
#cameron1do you use any kind of server-side templating for that?
#KartikPrabhuI do. I use Django and its templating system, but a lot of the long-form stuff is just HTML
#KartikPrabhucameron1: just saw your posts in the main channel. Instead of IndieAuth, I would actually start by 1) posting/publising to your website 2) Webmentions for responses 3) POSSE (which I do manually using bridgy)
#KartikPrabhubridgy will also send a webmention for replies/likes etc... to posts you have syndicated to (say) Twitter
#[tantek]KartikPrabhu, I think IndieAuth support is a fine place to start with where cameron1 is (and in terms of scratching your own itches 🙂 ) - plus then he can sign-in to the wiki!
#KartikPrabhu[tantek]: cameron1 of course all of these can be implemented in any order :P
#KartikPrabhuI was thinking more in terms of "getting an 'social media' type stuff on your site"
#KartikPrabhualso I have found Webmentions much easier to do that all the IndieAuth dance (which I still only barely understand)
#[fluffy]yeah webmentions give you a huge bang for the buck for indieweb
#[fluffy]and cameron already has RelMeAuth implemented, so can therefore login to the wiki 🙂
#[fluffy]for webmention I just suggest using webmention.io as your endpoint. It’s really easy to use, and I also have a client-side javascript library (webmention.js) that’ll work with it.
#[fluffy]Although supporting it server-side isn’t a terrible option either.
#KartikPrabhuyes. you can start by off-loading it to webmention.io and then build your own and switch to it
[grantcodes] joined the channel
#cameron1[KartikPrabhu] POSSE was a concept I was already starting to implement with some CLI tools, though bridgy looks much more of an elegant solution
#@kleinfreundOnce again not being able to wrap my head around webmentions. Especially the sending webmentions part.
I don’t understand the success criteria for the http://webmention.rocks tests. I get the first couple discovery tests to pass (1–9), but the rest don’t work. (twitter.com/_/status/1149960483329445889)
#KartikPrabhuyou can use display: contents on the ".hederTitle" to essentially get rid of it from the layout. But then you can't use some styles or a fragment link on that element
#jackybut when it's used blindly (like this) then it's trash
#jacky[cleverdevil]: thank you! if there's any presentation issues, lemme know - aiming to nail the UX
#petermolnarI'm starting to hate the post-gdpr/post DDOS-for-hire world; oath and it's idiots who put rss feeds behind gdpr consent which can be bypassed using 'googlebot' as user agent, cloudflare who thinks you're a bot if you don't accept cookies
#petermolnarmaybe we really do should go back to gopher
#jackyjust that syndication ones are specific to form encoded
#petermolnaranyone has a saved deviantart image url? Could you please try if it still works? I have a bad feeling; I see wix url returned for images, and knowing wix they didn't bother to retrofit the old scheme
#sknebelpetermolnar: you mean hotlinked images from deviantart? just checked a few on some random googled forum and seems those still work