#microformats 2020-09-23

2020-09-23 UTC
paulrobertlloyd, [snarfed], [tw2113], jamietanna[m], KartikPrabhu, [fluffy], justache, [jeremycherfas], [grantcodes], 94KAASXDU, iwaim, [Ana_Rodrigues], jeremycherfas, [Murray], [James_Gallaghe], [KevinMarks], [Rose], [chrisaldrich] and [jgmac1106] joined the channel
#
@oss_go microformats - https://github.com/willnorris/microformats (twitter.com/_/status/1308789797637574657)
[Emma_Humphries], [schmarty], KartikPrabhu, [fluffy], [James_Gallaghe], jeremycherfas, [Murray], jamietanna and timotimo joined the channel
#
timotimo greetings
#
GWG Greetings, timotimo
#
Loqi GWG: [tantek] left you a message 5 days, 18 hours ago: could you take a look at https://github.com/microformats/h-entry/issues/25 and LMK (reacji / comment) if it makes sense to you or if it doesn't, ask question(s)? I'd like to make sure that this method of attempting async h-entry process update proposal / discussion works before filing more such issues (also for anyone else who publishes or implements consuming h-entry, especially if you're
#
timotimo currently working on mf2 on my ghost blog
#
GWG timotimo: How is it going?
#
timotimo it's going okay i think
#
timotimo an automatically generated "previous post, next post, related post" section should be its own h-feed i assumo?
#
timotimo https://wakelift.de/how-would-you-like-a-1000x-speed-increase/ - does this seem all right from a microformats standpoint?
#
timotimo i guess the tags above the title would also want a h-feed of their own
#
GWG https://php.microformats.io/?url=https%3A%2F%2Fwakelift.de%2Fhow-would-you-like-a-1000x-speed-increase%2F
#
GWG You are marking up related posts as an h-feed?
[jgmac1106] joined the channel
#
GWG May be slow at times
#
GWG That's interesting.
#
timotimo i was using the pip13 thing
#
timotimo pip13.net
#
timotimo i think that's the same output
#
GWG Same parsing, different software
#
GWG But what is your intent with the h-feed?
#
timotimo i was mostly thinking putting many h-entry on the same page should have them in a h-feed to logically bundle them
#
GWG Yes, so the feed represents what?
#
timotimo but i guess an h-entry with url and uid set to the other address and just leaving out the content would be more correct
#
GWG The URL is that of a single post, right?
#
timotimo you mean the page's url or the url the entries link to?
#
timotimo or the url that the feed currently links to?
#
timotimo that last one would be the "all posts in the main tag of this post"
#
GWG <timotimo> https://wakelift.de/how-would-you-like-a-1000x-speed-increase/ - does this seem all right from a microformats standpoint?
#
GWG That url
#
timotimo ah, yes, that is the url of one post
#
timotimo the canonical full url of this post
#
GWG Okay, so inside the h-entry that represents the post, you need a u-url property that reflects the canonical link...
#
GWG That ensures consumers know that element is the pagr
#
GWG page
#
timotimo ah, i didn't realize that was missing
#
GWG As for h-feed, I would suggest it have a p-name of it's own so it can be identified
#
timotimo would i necessarily turn the title of the post into a u-url / u-uid, or would it be fine to have some invisible element instead?
#
GWG You seem to have it as h-name accidentally
#
GWG Invisible is fine for that if you don't have a visible permalink
#
timotimo ah, i don't have an intuition for the prefixes yet
#
timotimo would a meta tag make sense for this?
#
GWG Not really, because meta tags can't have a class
#
GWG u- is a url property
#
timotimo when i have a link to, say, /tags/foobar, would i turn that link into a h-feed h-url h-uid so that a consumer would know that there's a feed at that url, even when the current page doesn't have any of the entries from the feed in it?
#
GWG p- is plaintext
#
GWG h- is a root property
#
GWG e- is usually an HTML property
#
GWG I'm summarizing a bit
angelenos joined the channel
#
GWG No. h-feed wouldn't apply on a link
#
GWG But you could do rel=feed
#
GWG What is rel-feed?
#
GWG Hmm...that usually works
#
GWG http://microformats.org/wiki/rel-feed
#
GWG Although some say it is only for the feed of the same page
#
GWG However, rel-alternate does that right now
#
GWG https://indieweb.org/rel-feed
#
GWG This is probably a better definition
#
GWG u-url would be seen as representing the URL of the element it is inside
#
timotimo so where-ever i have "the author is timo" i would have a h-card with a u-url of /authors/timo/ inside of it
#
GWG Yes, correct
jeremycherfas and [fluffy] joined the channel
#
GWG We really should stage an online class
#
GWG I think we have a session recording from an Indiewebcamp about this
[schmarty] joined the channel
#
timotimo ok i changed h-name to p-name, i should toss out the h-feed for the related articles, but keep them h-entry?
[Emma_Humphries] joined the channel
#
timotimo i'm using (or will be using, i guess) whim to do webmentions; is there anything i have to do in particular to make sure i don't get mentions from every post on my site to every other post on my site? i think whim --content is the right way to do that
#
jmac timotimo: One way to do that in whim is to add your own domain to your blocklist
#
timotimo oh, that's kind of obvious in hindsight
#
timotimo how do i get this right, so that wakelift.de doesn't also block completely unrelated site notwakelift.deb
#
jmac That's a good question and I'll need to look that up myself! (In the meantime we might want to take this to #indieweb-dev or even #whim since this isn't really about microformats per se)
#
timotimo 'k
[chrisaldrich], jeremycherfas, Phae, craftyphotons_, twisted`, [snarfed], [LewisCowles], [tb], voxpelli, willnorris, jmac and [schmarty] joined the channel