#Loqitantek has 37 karma in this channel (450 overall)
#[jgarber]I realize now how far behind I’ve gotten on updating old and implementing new features on my website. 😭
#gregorlove.comedited /read (+108) "mv How to Brainstorming subsection since this is still quite new, not formally approved" (view diff)
#tantekaaronpk, next step in my venue cache array is to add lat/lng for each venue so I can show a map on my event posts
#tantekthen again I can "just" use URL or @-name for a venue, have my code translate back/forth as needed for primary post / POSSE tweet, and show map / set tweet location
#tantekthis works well for my event posts because most of my events re-use venues
#tantekso the "cost" of once in a while adding to the venue cache is no big deal (currently)
#tantek__per the opengraph URL kevinmarks shared, there's also "want-to"
#gRegorLoveSo not sure my exact question, but it seems like the mp request could change quite a bit over time and I'm wondering if I should change it now, or wait until it's more stable
#gRegorLoveGoodreads structure is a bit weird. When you add a book to your shelves, it's a "review" entry and I think the recommended-by is one of the fields on that entry, among many others.
#gRegorLoveLooking for examples. Will add documentation / screenshots
#tantek__since issues can have labels in them (as tags/categories) and Bridgy POSSEs them along with the issues, I wonder if the same is true for replies to / comments on issues
#[eddie]tantek: I add project tags when creating issues from my site but those project tags shouldn’t be labels on GH because every issue in the repo would have the same tag
snarfed joined the channel
#aaronpki have the same problem. i want the issue tagged "monocle" on my site, but it's silly to add the "monocle" label to monocle issues on github
#sknebelthat should work with bridgy as long as you don't have a "monocle" label in your repo, but it's still something that could go wrong with a more generic case
#aaronpkis that how bridgy handles it? I might need to fix that in silo.pub then
jgmac1106_ joined the channel
#jgmac1106_[eddie] headed here since we started using parsers and mf2 talk. The entry-content e-content is still enough for the parsers so I will go titleless,
#[eddie]jgmac1106++ for properly moving conversations across channels
#Loqijgmac1106 has 1 karma in this channel (27 overall)
#sknebelaaronpk: at least bridgy docs say it does that. but then it leaves the question of how to create new tags...
#[eddie]Yeah, if you want a photo post, using an h-entry, with u-photo on the images and e-content for the "content" such as the caption text, etc
[stefp] joined the channel
#jgmac1106_[eddie] go ahead and subtract the Karma given I didn’t realize I was back in #indieweb
#[eddie]haha mistakes happen. Keep the karma because you still thought to move
#[eddie]plus aaronpk kind of bated you by replying in #indieweb
[chrisaldrich], snarfed and [jgmac1106] joined the channel
#@Archan79Elon Musk just putted almost impossible engineering stunt creating his microsub. His team literally worked 24h day to achieve that. Fortunatly this Sub wasn't needed, but was almost ready if there will be need. And this amazing piece of engineering can be used in other situations (twitter.com/_/status/1016750055481643008)
#gRegorLove[kim_landwehr], Looks like there's 2 microsub endpoints in the HTML of your page. The first is 404, but the second works. I think the discovery process uses the first one it finds.
#gRegorLoveMight be a bug with micro.blog; I think that's what's running your site?
#gRegorLoveAlso some odd micropub stuff showing at the bottom of the page.
#[eddie]Micro.blog lets you edit the footer, which is where this stuff is located, so I think it should be as simple as logging into the micro.blog footer and removing the microsub link there.
#gRegorLoveOhh, there's an entire <head> element in the footer, and it looks like copy/paste of micropub documentation for a request.
#KartikPrabhuodd to put a <head> element in the <body>
[kiai] and snarfed joined the channel
#gRegorLoveYeah, micro.blog should probably prevent that
#aaronpkthat's tricky, because it shouldn't have too many restrictions on what you can put in the footer
#aaronpkthe other solution is for micro.blog to have a field to enter a microsub URL like manton was suggesting, then people wouldn't have to mess with HTML at all
#LoqiWebmention is a web standard for mentions and conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web https://indieweb.org/Webmention
#tantek__*in practice*, regardless of what the spec "allows"
#tantek__this often happens with new specs, there are aspects that allow for a number of axes of flexibility initially, because proponents of different approaches want to preserve the potential of those different approaches
#tantek__as specs evolve, sometimes those aspects are tightened up, depending on what's adopted and what's not
#KartikPrabhuI would have thought specs start out more specific and expand to suite new uses instead of the other way around