#tantek[allegory]: there's a lot of "web standards" and most of them have open source implementations
#tantek[allegory]: got a personal domain you're using recently?
gRegorLove, snarfed, barpthewire and [colinwalker] joined the channel
#[colinwalker]tantek aaronpk That DuckDuckGo search result was really surprising. Don't have a clue why DDG would be ranking it so high when it's nowhere on Google.
#jeremycherfasThe real drag about working with Grav — quite aside from the problems petermolnar has mentioned, which I don’t understand — is that I seem to be the only person using it who has any interest at all in IndieWeb. Makes me think that if I want to continue, I should switch back end, again.
#ZegnatThat’s definitely a tough point, especially if you don’t consider yourself a developer able to build the tools themself
#voxpelliloves working with backendless systems for eg. that reason – make it less of an all or northing
#ZegnatI do like my backends voxpelli, but I do like modularity :) My webmention endpoint runs on completely separate code from the rest of my site
#voxpelliZegnat: yeah, I have a backend for my webmention endpoint as well, just not for my main site, which kind of forces me into such modularity, which is insane and lovely at once :)
KartikPrabhu joined the channel
#ZegnatIndieAuth and Webmentions are both supported by separate folders with a few files in them. I could swap out the implementations at any point without touching my site. It does feel good.
Garbee, sl007 and [kevinmarks] joined the channel
#petermolnarmy wm endpoint ties in with my site "source code" and with the generator itself, but since the site is generated html it's definitely simple to decouple
#petermolnaralso my reason for PESOS for the interactions
#petermolnarI can safely break my pulls without losing the ability to react
#Loqiaaronpk: petermolnar left you a message 10 hours, 54 minutes ago: my FF doesn't like your archive layout (linux, FF esr 52.2) I even turned ublock and umatrix off, didn't help. https://petermolnar.net/tmp/aaronpk.png
#dgoldi thought that the media css was broken, spent a little while checking it over
tbbrown joined the channel
#LoqiJust generated this week's newsletter! You still have a few minutes to make changes, and I'll re-generate it 10 minutes before it gets sent out at 3pm Pacific time. https://indieweb.org/this-week/2017-07-21.html
#tantekaaronpk - any chance of that mini "Federating IndieWeb with micro.blog" post before ^^^ ?
#tantekalso your wmio feature upgrade is definitely worth syndicating to IndieNews
#tantekschmarty I see you fixed your "like" post :)
#schmartytantek: yep. thanks again for the heads-up. my likes, reposts, and bookmarks were all missing the u-*-of properties after trying to make them a little more "legible" and excluding the link-preview info from the content.
#schmartyi need to take another stab at it. i've now got the content simplified to something like "★ Favorited http://...some.url"
#schmartybut the link-previews are represented as u-*-of h-cite, so it shows up as a second "like-of" from the mf2 parser
#schmartyso, e.g., woodwind shows the same preview content twice :|
#tantekare you having to link to the thing you liked twice in the same post?
#schmartyfor now. i was inspired by gRegorLove's simple like-of post design and they way it showed up in woodwind as just the action and url. however, on my site i also want to see the link preview.
#schmartyi originally designed my link-preview templates as reply-context, so it expects to put some kind of u-* h-cite on the previewed content.
#tantekthis should be solvable. your u-* h-cite should work *outside* the e-content but still *inside* the h-entry
#schmartyi need to take another pass at it. particularly to clean up cases where link preview fetching failed or is incomplete, which is what led me to take the shortcut of putting u-*of on the link in the content.
#schmartycurrently got it as "p-name e-content", a pattern i have seen a few times and am cargo-culting. name vs summary vs content is something i often have to re-read to load the differences into my head.
#tantekand could probably use additional documentation
#[kevinmarks]They're a 3 part structure, but they collapse in notes which gets confusing
tbbrown joined the channel
#[kevinmarks]Name is the headline, summary the brief version, content the complete post.
#[kevinmarks]For a note, the name and the content are the same.
#[kevinmarks]One way to think about it is that the name and summary are on your homepage to encourage you to read the content. If the name is the content, you don't need a summary.
#tantekkevinmarks - still a bit abstract to actually be actionable
#tantekbiggest challenge is understanding / explaining when you *should* use summary
#tantekI started writing a "Federating IndieWeb with micro.blog" post and as I wrote the opening paragraph (summarizing what federating means) I realized we're not quite there yet
#tantekHere's my opening sentence and I'm curious what others think:
#tantekFederating across social media sites means two people can post and respond to each other, each using a different site and service, each without having to use the other site or service.
#schmartyThat almost sounds more like interoperability than federation.
#Loqifederation in the context of the indieweb refers to services and features on indieweb sites that work directly with other indieweb sites peer-to-peer, without being bottlenecked by any kind of centralized service or silo https://indieweb.org/federation
#TheGilliesI guess that's not really a "bottleneck" in that there isn't vendor lockin
#tantekright. Bridgy is also open source, so you can run your own
#tantekschmarty: updated slightly: Federating across social media sites means two people can post, see each others posts, and respond to each other, each using a different site or service, each without having to use or setup the other site or service.
#tantekI'm saying setup in addition to use because that's where I tripped up regarding the indieweb and micro.blog example
#schmartyi like that. it focuses on steps that users are likely familiar with.
#tantekaaronpk, https://aaronparecki.com/2017/07/19/24/webmention-io and responses are not quite federation because it still required you to create an identity on micro.blog and set it up to get posts from your personal site to show up to other users there.
#tantekmaybe we need to make a way to measure "how federated" a combination of systems are
#tantekbecause there is still value to the "set it up once and forget about it" caveat
#tantekthe funny thing is that email is sorta approaching that, with so much server specific configuration / setup that is needed to get your message accepted by other servers
#tanteklike if you have to contact help@ some domain (Gmail, Yahoo, etc.) to get them to configure their mail servers to accept mail from your server, then it's a similar step down from full "federation"
#schmartyit would be hilarious to see a light and peppy how-to video about setting up your own email server
#tantekI think petermolnar had some recent experience with that
#schmartyin the style of a "look at our cool easy social network features" ad
#tantekwhere he tried to switch domains and his email stopped working
#schmartyoh, those federation howtos are really interesting!
[cleverdevil] joined the channel
#[cleverdevil]Private photo sharing is a critical use case for gen3/4.
snarfed, gigitux, KevinMarks, davidmead and [manton] joined the channel
#[manton]Agreed that we're not quite there with Micro.blog and federation. Hopefully on the right path. There are a few areas (such as incoming webmentions) that are tied to accounts and should be opened up.