#[tantek]I've started with storing "created" dates for this very reason
jacky, [sebsel] and cybi joined the channel
#omz13[tantek] the fact anybody can create https://indieweb.org/.well-known/security.txt does not mean the problem is with .well-known but is clearly more to do with poor application / web server configuration
#[tantek]I disagree, this is why it's bad architecturally to have such "special paths" mean things
#omz13We are never going to agree on this. At some stage you need to point to where a resource is... whether its in a fixed place (link .well-known/...) or via a reference (like a rel link), I know which way I prefer.
#petermolnaromz13: riiight. And it lists all possible .well-known files :P
#petermolnarit's still a horrible thing, especially to use it.
#petermolnareg you host multiple services, say a website and xmpp under the same domain, and you already need quite convoluted .well-known setup to pass a few of those to xmpp and not others
#Loqiwell-known is literally the path "/.well-known/" under a domain and used as a standardized location for discovering domain-wide meta-data https://indieweb.org/.well-known
#[tantek]aaronpk, re: login vs sign-in, I don't know if this is intentional or inertia because frameworks for sites all have their own "account" assumptions baked in and its too hard to change it
#petermolnarI know ways around it, I just merely surprised
#[tantek]or rather it's easier to "just" bolt-on IndieAuth as another sign-up mechanism than to actually do the hardwork of NOT depending on creating a new account etc.
#aaronpkcould be, but getting an email address to have a way to contact the user is definitely useful
#aaronpkhopefully indieauth can give services everything they need for the simple onboarding case, which is why the latest version includes a way for the service to request the user's email and profile photo and such
#[tantek]maybe it's because we still need a defined account recovery mechanism?
#aaronpkdefinitely depends on the service though, there are plenty where those are not needed and just the authentication is enough
jacky joined the channel
#[tantek]right. and what I'm wondering is would better guidance for how to implement "just the authentication" help more services do that rather than the "create an account" default?
#GWG aaronpk: Is anyone using the profile in a client to your knowledge?
#aaronpkone good example of that i saw is one of the scooter companies, you can download the app and scan the scooter QR and pay all without needing to first go through a signup flow first
#ebjust thought I would share. Cloudflare offers a free netlify alternative with 500 *builds* (not build limits) a month. That's about 16 builds a day, or one a hour. I set up a script to check my indie sources (markdown files, webmentions, etc) for changes every hour. If there is a change it triggers a cloudflare deploy. It's an excellent compromise between static sites and dynamic ones, because changes take less then a hour to sync.
#ebThe advantage of cloudflare/netlify/etc is they have hundreds of servers and your website is on each. I tested my site in 8 different countries across the world and the average response time was 20ms
#ebI've reached out to a friend at cloudflare about the possibility of incremental builds and they said it was interesting but from a pricing standpoint it would be different (they have a paid tier with 5k builds a month for 20$)
#ebStill, I think even as it is it's a good middle ground
#[jgarber]This release of the Ruby client adds Vouch support among other new and improved bits.
#[jgarber]…meaning you can optionally include a Vouch URL when sending one or more webmentions and can optionally include a vouch URL when verifying a received webmention.
jacky joined the channel
#[jgarber]Not sure how many folks are actively using Vouch these days, but… we’ve got another client library implementation. 😄
#LoqiAutoAuth is the working title of an extension to IndieAuth that allows clients to authorize to other servers in the name of their user, without the user being present to confirm each individual authorization flow https://indieweb.org/AutoAuth
#LoqiTicket Auth is an extension to IndieAuth that enables a publisher to send authorization, known as a ticket, that can be redeemed for an access token https://indieweb.org/ticketauth