[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!
[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]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.
[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]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]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]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]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.
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)
[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!
[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.
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
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
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