[fluffy]Hm, the indieauth.com setup instructions don’t provide a <link rel=“authorization_endpoint”> example. It only discusses how to use it as a RelMeAuth provider for things that specifically use indieauth.com for login, as opposed to using it as a generic IndieAuth endpoint. Is that intentional?
tomlarkworthyI have token minting working now for my version of it. Hopefully it will make it trivial to pseudo-self host, I think my hosting costs are about <$0.05 a month. WIP and full of security holes and typos but https://observablehq.com/@endpointservices/relmeauth
[fluffy]For IndieAuth providers I’m listing SelfAuth and the WordPress IndieWeb plugin, and for clients I’m mentioning indielogin.com and Authl (because I’m biased), and then also linking to the indieweb wiki page for more.
[fluffy]I’m calling the presentation “A Little About All About IndieWeb” and it’s just a general overview of the why and the how. Discussion of the core tenets, and a 20,000-foot overview of webmentions, indieauth, micropub, brid.gy, and a couple of platforms (particularly the wordpress plugin, micro.blog, and, of course, publ, because shameless self-promotion)
@CodingPotions↩️ ¡Muy buen artículo! No hay tantos en español hablando de la IndieWeb.
Ahora que lo pienso, ¿se podría implementar un webcomponent para que sea más fácil mostrar las webmentions? (twitter.com/_/status/1379350227287674880)
[KevinMarks], ben_thatmustbeme and jeremych_ joined the channel
LoqiVisual representation, sketch notes from talks, building block logos, images, and slide deck templates you can use in your talks https://indieweb.org/diagram
[tantek][fluffy] since this is a developer crowd, would that graphic ^ help illustrate how the topics you mentioned fit together and enable various use-cases?
[fluffy]Hm, I’m not terribly interested in that graphic just because it focuses way too much on micropub/microsub which aren’t the parts of indieweb that most folks I’ve talked to are interested in
[tantek]diagram << Suggestions for improvement / perhaps alternate diagrams: 1. clean-up all the various colors used so they're minimized (per Tufte) and used to clearly convey specific meanings. 2. re-orient/reformat diagram to focus on user features enabled by Webmention+microformats first & foremost, and the other protocols only secondarily. 3. start at the top left, instead of lower left. or perhaps top middle if it's going to be a clockwise cycle,
Loqiok, I added "Suggestions for improvement / perhaps alternate diagrams: 1. clean-up all the various colors used so they're minimized (per Tufte) and used to clearly convey specific meanings. 2. re-orient/reformat diagram to focus on user features enabled by Webmention+microformats first & foremost, and the other protocols only secondarily. 3. start at the top left, instead of lower left. or perhaps top middle if it's going to be a clockwise cycle," to the "See Also" section of /graphicshttps://indieweb.org/wiki/index.php?diff=75198&oldid=63537
[fluffy]in my slide on “displaying webmentions” I have three tiers: client-side render with webmention.js, render server-side or use a webhook to render static pages, or “galaxy brain: don’t display them at all”
[fluffy]anyway what I’m focusing on are the aspects of how indieweb is about modularity and optional implementation of stuff, and how easy it is to get into the basics of running an indieweb site
[fluffy]the order (and implied priority) in the talk is: 1. what is indieweb/core tenets, 2. webmention (and things you can do with it like brid.gy), 3. indieauth, 4. micropub, 5. everything else
[tantek]that makes A LOT of sense, both as an outline, and strategically to keep the discussion focused and practical (instead of distracted into more academic/hyped stuff)
[chrisaldrich][fluffy] I'd be curious to see your slides as I'm starting prep on a similar presentation in a couple of weeks, but it's geared to a completely non-dev crowd.
[chrisaldrich]I've been looking at that diagram and figure out how to redesign it so that the person's website is either in the center or at the top to provide that as the centerpiece (from an indieweb framing at least) and the other parts are smaller building blocks that stem off of it.
btremWhat the what? I've been under the distinct impression that search engines don't index alt text. I still use alt text when appropriate for accessibility, but assumed it would not impact search results. A simple poke around the interwebs has disabused me of that notion. I wonder how I came to that oh-so-wrong conclusion. :/
KartikPrabhu, [Rose], [tantek], [snarfed] and [KevinMarks] joined the channel
[KevinMarks]To go back a long way, Mark Pilgrim's Dive Into Accessibility said something like "some of the many important blind users you have are search engine spiders"
[KevinMarks]Search engines now will ocr your images and feed them to neural networks, but they will also read your alt text and likely train the neural networks with it
btremYeah, I read some of Mark Pilgrim's articles. I was one of the people saying that Google was one of the most important visitors you'd have. And to view your page in Lynx to get some idea of how a page would work. But somehow, I got the idea that Google ignored alt text. I have no idea how that got into my head.
btremIf I had to guess, I might say that I conflated keyword stuffing/spamming in meta tags -- which are ignored by search engines -- with keyword stuffing in alt attributes.
[tantek]yeah anyone keyword stuff into alt attributes would likely get (rightly) criticized pretty quickly when folks started to hear the stuffing in screenreaders