#@azzamsyawqi↩️ I was looking around trying to find your Preact implementation. It's not in your "eleventy-webmentions template". So I am going to write it my self. Turns out http://mxb.dev is open source :).
Some people use Cron and WebSocket, but I prefer this preact approach :). (twitter.com/_/status/1286208060759842816)
#jeremycherfas!tell aaronpk I just saw notice of a plugin for Grav that implements simpleSAML. Looking at simpleSAML, I see it supports OAuth. Do you think it might be worth my looking into so I could use my Grav site without relying on rel="me"?
#Loqiaaronpk: jeremycherfas left you a message 8 minutes ago: I just saw notice of a plugin for Grav that implements simpleSAML. Looking at simpleSAML, I see it supports OAuth. Do you think it might be worth my looking into so I could use my Grav site without relying on rel="me"?
#Zegnatjeremycherfas: had you done any Grav plugin work before? It may be easier to implement selfauth than you think. And for first version, you could still outsource token endpoint to https://tokens.indieauth.com/ if you did not want to also merge in full token handling
#jeremycherfasThanks for the encouragement zegnat. I did take a close look at some plugins a while ago, when I tried to figure out the webmention plugin. For now, this will have to be quite a lot priority. I should update my itches.
#ZegnatIt would be nice, as Grav has 2FA and flood protection (against password guessing) build in. Automatic step up from selfauth's protections
#GWGNo, I caught twtxt...missed the WordPress plugin
[Zegnat] and [schmarty] joined the channel
#zenendoes anyone get kind of overwhelmed at the amount of knowledge required to build a webpage from the ground up?
#Loqizenen: [LewisCowles] left you a message on 2020-04-09 at 7:06am UTC: I think when borrowing design, it also helps to keep the wrote copy local to your PC, and then experiment with a design
[jgmac1106], nickodd and [michael_lewis] joined the channel
#[michael_lewis]And instead of Django you could take a look at Flask. It is a micro framework, and anything with micro in the name is usually good. Convention over configuration and all that.
[fluffy] and [benatwork] joined the channel
#craftyphotonsI'm trying https://bulma.io for my website now, liking it so far — CSS only and no JS which aligns well with my goal of having my site be JS-free if I can help it
[chrisaldrich], TakeV and TakeV1 joined the channel; nickodd left the channel
#TakeV1[KevinMarks]: Epic suggestion for newcss. This is exactly the kind of thing I've been looking for.
#[KevinMarks]Not necessarily a bad idea, but a stronger dependency on a particular model
jamietanna and [fluffy] joined the channel
#aaronpkattempts to catch up on some of the micropub discussions before the weekend
zenen joined the channel; builder left the channel
#[fluffy]Seconding Flask, it’s what I use to build all of my personal websites these days. Well, most of them are using Publ which is built on Flask, but I have a few plain Flask things too. 🙂
#[fluffy]It’s really easy to get started with and it gives you a lot of lego bricks out of the box without forcing you to do things in one particular way.
#[tantek]aaronpk, pretty sure you can merge things as you see fit into the Micropub Editor's Draft, however I'd advise not merging anything other than editorial changes for that fork
#[tantek]and instead, fork the Micropub spec to github.com/indieweb org, and transfer normative issues and pull requests accordingly, and then serve *that* version from micropub.spec.indieweb.org
#GWGThere was some discussion with Angelo last night on the HWC on Micropub
#[tantek]I can give reasons why you should do (and not do) what to the /w3c org fork of Micropub vs a /indieweb fork of Micropub
#[tantek]I know all the process / IP nuances there (many of which you may recall, though I may be more recently aware since knowing that stuff is now literally (again) part of my day job as an Advisory Board member)
#aaronpkespecially after 2 days of this oauth conf
#GWG[tantek]: Did you check the event page for the website URL?
#aaronpkmainly i want to catch it up to the current oauth best practices, which the biggest change will be adding PKCE
#aaronpkthere's also a functional difference i want to make which would essentially remove a whole section of the spec to make it simpler, but i'm a little worried about that because i don't quite see how to do that in a way where both can be supported simultaneously
#aaronpkat least with PKCE it was designed to be backwards compatible so that clients can roll it out even if the servers don't support it
geoffo and KartikPrabhu joined the channel
#craftyphotonsIs there a reasonable way to do automated POSSE to Instagram these days?
#craftyphotonsMy current goals as I get my site set up are articles to Medium and Dev.to, notes to Micro.blog and Twitter, and photos to Instagram and Flickr
[grantcodes] joined the channel
#[grantcodes]Don't think there ever was or will be again 😑
#aaronpkthere has never been a way to do automated POSSE to instagram
#[grantcodes]There was, I did it and it worked. But is wasn't "reasonable". And now it doesn't work 😂
#craftyphotonsI remember there being some third party extension someone made for Lightroom once that led me to believe there was some way to fool their API with some user agent trickery or something like that
#craftyphotonsOh well then, I can settle for automation to Flickr and leave IG as a hand curated silo I suppose
#aaronpkyep and sadly they're making it hard to even pull photos out anymore, so PESOS is becoming less and less possible
#craftyphotonsOh yeah that was going to be my next question and then I remembered that thing they did recently on the web version where you need to be authenticated even to look below the fold on someone's public profile
#craftyphotonsWhich.. suppose you could write a full on scraper with Selenium or something and authenticate yourself
#craftyphotonsI think what I'd ultimately want to do there though even if that's possible would be to come up with a hashtag convention to ID my IG photos to the scraper and tie them back to the originals I would've posted on my site
#aaronpkhmm, adopting the Pushed Authorization Request spec would also be a breaking change so maybe IndieAuth 1.1 or 2 or whatever this is should just go for it
#aaronpkthe short version is you first POST to the auth endpoint with the details of your request, and you get back a string that you use when you redirect the user's browser
#[schmarty]oh it's a way of reducing the stuff sent in the URL bar of the initial auth request
#aaronpk1: it improves security, 2: it opens up the possibility of including a lot more detail in that request, which is being used for things like authorizing a request to move money between specific bank accounts
#aaronpklet's wait til saturday and see how it goes, and maybe we can even decide on a date then because i suspect it'll be a lot of the same people interested