#meta 2022-03-19

2022-03-19 UTC
#
tantek.com edited /Planning (+486) "Austin / Texas issues, remove self" (view diff)
#
tantek.com edited /Planning (+72) "move IWCs with candidates up to top of list, move others down" (view diff)
#
[tantek] GWG, want to offer your opinion / likelihood for various upcoming IWC dates? https://indieweb.org/Planning#Dusseldorf and the next few others
#
GWG [tantek]: I feel like I want to talk this out.
#
GWG I debate my comfort level regularly.
#
@MichaelWDelaney ↩️ Anything’s a CMS if you indieweb it hard enough! This is super cool. (twitter.com/_/status/1504976136190713858)
#
david.shanske.com edited /Planning (+130) "/* Dusseldorf */" (view diff)
#
david.shanske.com edited /Planning (+127) "/* Summit */" (view diff)
[tw2113_Slack_], [James_Van_Dyne] and kimberlyhirsh[d] joined the channel
#
@artlung I got a IndieWebCamp T-Shirt on @Gumroad: https://indieweb.gumroad.com/l/iwc-shirt #IndieWeb (or... I'll have it when it arrives!) (twitter.com/_/status/1504985307602583555)
John, Seirdy, jacky, strugee and gRegor joined the channel
#
@benwerd One of the most interesting aspects of @bluesky is its inclusion of the broad decentralization community, from indieweb to blockchain. It’s a very impressive approach, and a broad, open tent, that gives me a lot of hope for the future of social and the internet. More, please. (twitter.com/_/status/1505016361151447040)
gRegor joined the channel
#
jacky but they've more-or-less rejected a lot of the indieweb tenents because 'it relies on DNS'
#
jacky IIRC
#
[snarfed] jacky actually no, that was our mistaken assumption. they appreciated the indieweb proposal but didn't like that it requires some explicit support from silos, eg for rel-me links
#
jacky ah gotcha
#
jacky hmm how else would people migrate/bridge then?
#
jacky guess that's not a concern
#
[snarfed] (see indieweb section on https://blueskyweb.org/blog/satellite and https://twitter.com/arcalinea/status/1470818566987399169 )
#
@arcalinea @schnarfed @haxor To clarify, I don’t hate DNS; the winning solutions were more decentralized than the indieweb ones because their implementations did not require platform level support from sites like twitter. (twitter.com/_/status/1470818566987399169)
#
jacky hmm
#
[snarfed] generally the other proposals used the plaintext contents of post(s). like some popular service a while ago named key-something (I think) that's escaping me right now
#
[snarfed] regardless, you're right, [benwerd]'s description of bluesky "including" indieweb is overly generous
#
jacky keybase perhaps?
#
[snarfed] yup that one, thx
#
jacky hmm
angelo, strugee, gRegor and trig[d] joined the channel
#
[KevinMarks] They own twitter, it's in their power to put the standards support and interop back again
#
@JasonRouet ↩️ Honestly I haven't made my choice between the indieweb project and the antispam bee project yet! :P (twitter.com/_/status/1505108476019806210)
#
@JeroenHabets Exploring #IndieWeb (https://indieweb.org/) a bit using https://indiewebify.me I had to fix some rel="me" links but other than that #Mastodon seems well prepared :). (twitter.com/_/status/1505116638672216073)
#
@hagengraf Ich bin dann jetzt mal beim #Cloudfest #Hackathon angekommen und freue mich auf das #wordpress #indieweb #fediverse Projekt https://www.cloudfest.com/project/wordpress-and-the-indieweb Ist denn noch jemand aus meiner Bubble hier? /@pfefferle (twitter.com/_/status/1505131000539619329)
sayanarijit[d], jacky and Seb[d] joined the channel
#
@Cambridgeport90 Using Drupal for #indieWeb has really caused me to consider HTML as a serious option for site updates. I'm so used to either plain text or markdown; needless to say, I've been spoiled. (twitter.com/_/status/1505193079807959042)
#
jacky HTML++
#
Loqi HTML has 1 karma over the last year
#
@Cambridgeport90 what are some decent fields where the E-content class of #Microformats should be applied on various content types? #Drupal #indieweb #tech (twitter.com/_/status/1505197572939345921)
jacky and johnnrs[d] joined the channel
#
@Cambridgeport90 I got the timestamps on my notes to display properly; now to fix the syndication targets. Still want to use something else over bridgy publish. I have a previously created Twitter app that uses the API. #indieweb, working on my web site. Bridgy #backfeed, though... (twitter.com/_/status/1505229221462888448)
[aciccarello], barnaby and jacky joined the channel
#
[tantek] indeed that message from jay made me more optimistic. agreed snarfed about [benatwork]’s tweet being a bit generous, however I wonder if that kind of public generosity also helps as a form of positive inclusion nudging. maybe that's a good way to build bridges from a social perspective?
mro joined the channel
#
jacky perhaps!
#
jacky it'd probably come from our community
mro and [benatwork] joined the channel
#
[benatwork] I can neither confirm nor deny that this was my intention
#
[benatwork] I know that their intention really is to be inclusive
#
[benatwork] But also
#
[benatwork] I've enjoyed conversations I've had with Jay in particular.
#
@JasonRouet Awesome team for an awesome project: #IndieWeb + #WordPress lead by @pfefferle. The challenge? Thinking how to make the #Webmention plugin more visible and easy to set-up! #CloudFest #WFHACK #WFHACK2022 (twitter.com/_/status/1505271831384801286)
mro and gRegor joined the channel
#
gregorlove.com edited /Planning (+3) "/* Vancouver */ disambig Vancouver, BC vs WA" (view diff)
jacky joined the channel
#
[tantek] pfefferle++
#
Loqi pfefferle has 1 karma in this channel over the last year (6 in all channels)
#
tantek.com edited /Planning (-1) "cleaner heading link, no comma" (view diff)
[pfefferle] joined the channel
#
[pfefferle] ☺
barnaby joined the channel
#
GWG [pfefferle]: Hi
#
boffosocko.com edited /pronunciation (+7) "tweaked quote" (view diff)
#
[tantek] as much as we self-criticisize for having "walls of text" on the wiki for explanations / instructions, at least we're not as bad as GitHub which literally has four subpages of walls of text to explain how to setup a domain with GitHub Pages. There is no reasonable explanation for why it should be that complicated: https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site
#
[tantek] It's not obvious at all which of the four links on that page I should click first
#
[tantek] Clicking the first one turns out to be useless and confusing with a bunch more links that go to who knows what
#
[tantek] https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages
#
[tantek] Why put the "www" option first? This isn't the 1990s. It's very bad guidance to put dated advice first in a list of options. It shouldn't even be in a list, it should be in an appendix for supporting legacy style "www." URLs purely for a 1990s aesthetic if that's your jam
#
[tantek] Then "Custom subdomain", like seriously WHY?!? Why make a *more* complicated option the second option? Why do I now have to pick*another* name (the subdomain) in addition to the domain name I just bought?
#
[tantek] then "Apex domain", finally the sensible "simple" "plain" domain option, except using jargon. like WTAF, no one I know except backend webdevs typically even know what an "Apex" domain is
#
[tantek] what is an Apex domain
#
Loqi It looks like we don't have a page for "Apex domain" yet. Would you like to create it? (Or just say "Apex domain is ____", a sentence describing the term)
#
ragt.ag uploaded /Special:Log/upload "uploaded "[[File:indiemark-concentric-circles-v2.svg]]" https://indieweb.org/File:indiemark-concentric-circles-v2.svg"