mpardalos[m], AramZS, [KevinMarks] and neceve joined the channel
#AramZ-S[m]capjamesg Hey, did you open source your hovercard.js stuff individually or is it just in your blog's GitHub? You didn't link but I'd be interested in looking at the code and potentially adapting it to my own use.
#barnabythe keys are based on the OAuth server metadata spec https://www.rfc-editor.org/rfc/rfc8414 so I’d imagine the existing ones not likely to change very often, but there could be new ones
#capjamesgThe issue is new keys would require an additional release to add.
#capjamesgWhich is why I wonder if this is a rare case where the library should return the raw data like you said barnaby.
#barnabyperhaps, or in addition to parsed/validated values
#capjamesgAs a developer would you prefer the raw data or an object barnaby?
#barnabycapjamesg: briefly glancing through that code, I’d add a “raw_server_metadata” key to the indieauthendpoints dataclass and put the raw values there in case people want to look for them
#LoqiIt looks like we don't have a page for "GruberVille" yet. Would you like to create it? (Or just say "GruberVille is ____", a sentence describing the term)
#GWGThey could theoretically change anytime.. but the existing ones won't... just new things could be added
#aaronpkoh boy, Laravel is on version 9 now, and Meetable is on 7. wonder if I should spend a day upgrading now so it doesn't get too far out of date
#aaronpkmy own website is on an even older version of Laravel and i'm a bit terrified to even attempt to update it :-/
jacky joined the channel
#barnabyI’ve never used laravel, is it usually a pain to upgrade to new versions?
#aaronpkyou have to carefully read the release notes because they keep changing how various internal things work
#[marksuth]I’ve gone through the process of upgrading a number of Laravel sites recently, the jump from 7 to 9 isn’t that painful, I think there was 1 or 2 lines that needing adjusting in serviceproviders where things had been replaced but otherwise it was fairly smooth
#barnabyaaronpk: is it easy for you to set up a duplicate of your site on a subdomain to try the migration there?
#[manton]I didn’t know about archive.ph… Love the Internet Archive but that’s great to have some other folks doing this. Wonder how big they can scale?
#gRegorI thought there were a couple but looks like they're aliases of archive.ph (archive.today and archive.is)
#[manton]Kind of inspires me to make my archiver more available… Currently only used for Micro.blog bookmarks but I always wanted to open it up. With limits. I can’t be the Internet Archive. 🙂
#LoqiIndieArchive is a project to collaboratively grow an archival copy of pages replied to (possibly also mentioned) in indie web posts https://indieweb.org/indie-archive
#[tantek][manton] ^ you might be interested in that, in the Indie but not trying to be Internet Archive way
#[manton]Thanks. I should probably add a few notes to that wiki page about what I’m doing too.
#[manton]Internet Archive will always be the gold standard of nearly everything, but I like the idea of several (or more) smaller archives.
[benatwork] joined the channel
#[tantek]agreed. smaller, perhaps more focused archives can help fill the holes
#[tantek]those ":white_heart: by author" reactions are 2nd order, that is they are in-reply to comments which are then in-reply to the top level post. Displaying that 2nd order response on a permalink of the original post demonstrates a clear use-case for salmentions (webmentions being propagated further upstream as it were)
#capjamesg[tantek] Today is the day I think I finally got my head around Salmentions.
#capjamesgThe concept previously would not register in my mind.
#capjamesgI was wondering if indieweb-utils could do anything here but it seems pretty implementation specific?
#aaronpkinitial upgrade of meetable to laravel 9 went smooth. i suspect there may be some issues with the more obscure features though
#angelocapjamesg get_post(permalink, upstream=1) that gets the post at permalink but also recursively fetches responses `upstream` levels deep and collapses all of the interesting bits into a dict
#capjamesgUpstream as in the post to which a reply is replying?
#capjamesgangelo That feels like a great function to have.
#angeloupstream to imply salmentions (salmon swimming upstream)
#capjamesgThen parsing would be getting all the upstream info into a dictionary?
#angelohm the like of the reply here would trigger a mention to the reply which would trigger a mention to the original post.. that'd be the upstream part. i suppose this reverse discovery would be downstream.
#angelomaybe just use `depth=1`.. so the original author here would need to only fetch the reply (which would have the like on it). however a reader that's fetching the original post would have to fetch one level deeper `depth=2`.