#dev 2025-06-03

2025-06-03 UTC
grufwub, oodani, paotsaq and Xander joined the channel
#
[social] I still have an hCard reader script in my bookmarks in Safari (I think it is Brian Suda’s) that parses out hCard metadata and puts it in a vCard format (I ran it, but realized I don’t off hand know of a page with it).
#
[social] I also have an h-Cal parser bookmark.
parnikkapore_x, barnaby, [Jo], doesnm, [Scout], grufwub, [qubyte], ttybitnik, [KevinMarks], gregsarjeant, [manton]1, [manton], [qubyte]1, aaronpk, jjuran, IWSlackGateway, [social]2, [social]4, _sisoma[d], strugee, Salt and voxpelli joined the channel
#
[social] Regarding D3, I think I’ve seen it used in one of the packages an IndieWeb user was using for stats that came with their static web platform.
jjuran_, IWSlackGateway, bitauger, bugliker0, skeuos[d], hidjy[d] and box4649 joined the channel
#
[KevinMarks] you don't have h-feed+h-entry markup on the root page morgan
#
[KevinMarks] d3 is very powerful, but take a fair bit of effort to get your head round. Observable Plot is an easier coding interface to the powerful plotting parts. https://observablehq.com/plot/getting-started
#
[social] I like the ease of Observable, but they are starting to lean into their pricing model, which is pricey.
#
[social] I haven’t looked to see what is still free to use and what is now paid.
gRegor joined the channel
#
[KevinMarks] Plot and D3 are open source https://github.com/observablehq/plot
#
[KevinMarks] https://github.com/d3/d3
#
Loqi [preview] [d3] d3: Bring data to life with SVG, Canvas and HTML. :bar_chart::chart_with_upwards_trend::tada:
barnaby, balintm, NaomiAmethyst and Lars-Christian joined the channel
#
[KevinMarks] https://github.com/suitenumerique/hackdays2025
#
Loqi [preview] [suitenumerique] hackdays2025: For three days, take part in the creation of open-source apps aimed at strengthening European digital sovereignty.
#
[KevinMarks] https://hackdays.numerique.gouv.fr/en
#
[KevinMarks] demo day is tomorrow https://docs.numerique.gouv.fr/docs/edaf6617-5102-4bce-b0f0-523b68728bcc/
#
[tantek] FYI: anyone want to thumbs-up this? https://github.com/mastodon/mastodon/issues/24066
balintm and [mattl] joined the channel
#
[mattl] Thanks to everyone for the well-wishes about http://Libre.fm — to be clear, it’s not shutting down, just accepting no new users. So if you got an account, welcome to the internet’s hottest club.
#
[tantek] [mattl]++ amazing. Major Metafilter vibes 🙂
#
Loqi [mattl] has 29 karma in this channel over the last year (67 in all channels)
#
capjamesg ✨
#
[mattl] The more I think about job stuff the more I realize I really don’t want to work for anyone else… so I’m thinking about how to do this for myself, somehow.
#
[artlung] _When the going gets weird, the weird turn pro_
#
[mattl] er.. this channel is logged, right? I’m going to go rant in the cafe.
barnaby, gRegor, sebbu2, cow_2001, balintm and duanin2 joined the channel
#
[0x3b0b] I just skimmed through some past days of chat that I hadn't read yet and am now entertained by the idea of including on a form, somewhere, sometime, a question for "gender," with two options..."none of your business" and "other."
bret joined the channel
#
[tantek] had a good informal chat today about ways to make it easier to both advocate for IndieAuth "support" (and being specific about what that means), and making it easier to actually build (test, verify) that support as a developer, and what would "superb" (my summary word) support for IndieAuth look like?
#
[tantek] a big part of the discussion started with discussing how to better communicate on all these topics and there were two (at least) three distinct points that came up:
#
[tantek] 1: when talking to internet users, the best (current) term to use for the thing they use to sign-in is, your "web address" (phrase from NYT). This is akin to (relates to) "email address" and makes more sense to more people than your "domain name". The term "web address" is already prominent on https://microformats.org/wiki/web-sign-in and https://indieweb.org/Web_sign-in
#
[tantek] 2: Ask services to support "Web sign-in" as in "consuming" or "accepting" a web address for sign-in, and then supporting at least IndieAuth and preferably also RelMeAuth to sign-in the user with their preferred web address.
#
[tantek] In other words, ask for that support *instead of* merely asking for "support IndieAuth" or "support RelMeAuth" because those are both ambiguous, and ironically focus on the wrong piece (specific plumbing) rather than the UX. / user-benefit which should more directly motivate the service's benefit.
#
[tantek] 3: Be clear about the user-benefits and the service-benefits up front, (positive like user choice, and service independence of silos, and also avoiding negatives like not encouraging users to bind themselves to a silo identity, not having your service drive your users to a silo for identity) rather than "open standards" for open standards sake.
#
[tantek] I feel like that might be enough material for a blog post but wanted to run those thoughts by folks here first to see if anything resonates (or strikes folks as odd or bad)
#
[tantek] and one aside, it's not clear that it's worth advocating from an IndieWeb perspective for existing services to become IndieAuth providers themselves, because that still leaves the existing services in "ownership" of user's identity. we want people to "bring their own identity" that's under their control, not some 3rd party service
#
[tantek] if it's for a plugin for a CMS sure, that makes sense to advocate to provide IndieAuth identity, because then users that use that CMS can more easily use their personal web site to sign into other sites
#
[mattl] what are the minimum number of steps from buying a domain name to using it to sign into http://indieweb.org?
#
aaronpk Probably buy a domain through micro.blog
#
[schmarty] The provider landscape has become more confusing over the last few years. (Don't use indieauth dot com, but that means self-hosting i think. Self host software is at different ages and levels of spec support)
#
[schmarty] Yeah I guess manton can host your IndieAuth provider haha
#
[schmarty] (If hosting your entire site)
#
[tantek] [mattl] assuming you already have a GitHub account, minimum number of steps that is not single-provider dependent is: 1: buy a domain through provider of your choice, 2: setup a GitHub static home page on that domain (i.e. fork the static home page project from GH/IndieWeb) and edit it with your info (name, icon, link to your GH), 3: edit your GH profile to link to your new domain
#
[tantek] (of course obviously neglecting that GitHub is a "single provider" in this case as well) point being, that will get you enough to "sign into http://indieweb.org?"
#
[tantek] this is still easier today than attempting to setup your own IndieAuth provider (i.e. not using indieauth dot com)
#
[mattl] that seems like a fair bit of work just to edit the wiki… but buying one from http://micro.blog seems like a better idea.