bterry, mro, IWSlackGateway, lagash, geoffo and [manton] joined the channel
#[manton]Curious if [aaronpk] or anyone has feedback about this… After talking to another developer who wasn’t familiar with IndieAuth, I decided to write a help page from the perspective of thinking in OAuth when using Micro.blog. I was thinking maybe it’s a stepping stone… First use OAuth, then add the “prompt for domain name” at the beginning of the flow so it works with other blogs. https://help.micro.blog/t/oauth-in-micro-blo
mro and [jacky] joined the channel
#[jacky]This looks good! I think once more people realize that it's _built on something existing_ (which first sometimes requires pointing out what "Sign in with X" might be), then it'd be second nature
#[manton]Grabbing some HTML and looking for <link> tags is easy, but I wonder if it feels kind of foreign to some programmers who are used to platform APIs. Not sure there’s a solution for that other than more docs.
mro, [schmarty], [KevinMarks] and [tantek] joined the channel
#[tantek][manton] we have some documentation / libraries for that on the wiki I believe. pretty sure I split that out "some HTML and looking for <link> tags" into its own page
#LoqiIt looks like we don't have a page for "link rels" yet. Would you like to create it? (Or just say "link rels is ____", a sentence describing the term)
#[tantek]maybe we need something like "link rel discovery" that provides that kind of a focused explanation (why & how), more specific than https://indieweb.org/discovery-algorithms — [manton] would such a page ("link rel discovery") help the kinds of developers you are thinking of?
#Loqi👃 follow your nose is an intentional local & web-centric methodology for designing discovery algorithms that start with a specific URL that to discover things about, inspecting its contents, often for specific hyperlink rel values to predictably discover information about & resources for that URL, in contrast to the “well-known” approach of instead checking outside that URL, like using only its domain with a hardcoded path https://indieweb.org/follow_your_nose
#[tantek]also related (so to speak) ^ [and needs dfn copy-editing to make it fit]
[aciccarello] joined the channel
#[manton]Thanks, I’ll look through some of those wiki pages, I don’t think I had seen all of them. That /link_rel_parser looks like a great start as a simple intro page.
#[manton]And to be clear, I’m not sure this is actually a problem. Just was thinking that link rel parsing is a fundamental think that other building blocks sit on.
#Loqi[preview] [temp_account_32] It's funny to see how half of HN frontpage in the past weeks has been Show HN thin wrappers around an API call to ChatGPT disguised as full startups.
All while HN posters were warning us about a flood of low quality AI generated content, well, here i...
#superkuhNow we can move on to thin wrappers around llamas and alpacas running locally. Progress.
#[tantek]capjamesg re: link discovery, not from the summary/description, and not going to watch a video to answer a question. if there's a text transcript you can point to that would make it easier to evaluate.
#capjamesgIt was built by the former CEO at GitHub, who is now involved quite a bit in the AI industry I believe.
#capjamesgMy comment was sarcastic. It works by scraping links from a page then using a Python library to follow them :P
#[tantek]The phrase "GPT 3 to control a web browser" should be a giant red flag
[schmarty] joined the channel
#prologicIsn't the whole *GPT* and AI all just hype anyway? I mean they're just LLMs running on some pretty beefy hardware with huge amounts of data trained on