[jeremycherfas][tantek] I’d be interested in your strong feelings on prevnext, especially if they are more than anti-infinite scroll, which I too hate and would never have on my own site.
[LewisCowles], AbedB, swentel, gxt, asymptotically, [fluffy], mblaney1, kensp, [jeremycherfas], [jgmac1106], [grantcodes], [KevinMarks], patterthing, r4v1, anotheryou, wolftune and [tantek] joined the channel
LoqiIt looks like we don't have a page for "prevnext" yet. Would you like to create it? (Or just say "prevnext is ____", a sentence describing the term)
[jeremycherfas]Calling your link an “article” is interesting, but the content is clever. I too, biassed as I am by left-to-right reading, will always consider left to be backwards in time.
[jeremycherfas]Yup. And I had a colleague who, in showing various graphs with time along the abscissa, would always point out that “as they get older, they move to the right, just like most people”.
[chrisbergr]in ltr, prev is left and next is right. But let's say you also have a pagination, typically page 1 contains the most recent post at first place and the oldest post on the last page (e.g. 22) on the last place. Then you need to define prev as "newer posts" and next as "older posts".
Loqipagination is a UI pattern for navigation across (typically chronologically) sequential pages that show one or more posts such as permalink post pages, archives, search results, and lists of tagged posts https://indieweb.org/pagination
[chrisbergr]After all everyone can do what he/she prefers 🙂 But I would suggest to always use the link text "older/newer posts" instead of prev/next. This is only for the rel attribute
[chrisbergr]Why isn't it in sync? next means next page with same type of content, prev previous page with same type of content. There is no relation to time, as far as I understood those both values.
[LewisCowles][jeremycherfas] my script is a very lightweight PoC that works for me. I'd be incredibly humbled if an initial attempt was a good fit outside of a group of me, but I think it might be weak for a global audience.
[snarfed]one common "mistake" (maybe?) we see sometimes is full length articles that are marked up as a reply to another post, when really they just mention it. do we have something on the wiki about that? trying to find it. possible culprit: https://jaenis.ch/blog/2019/about-mentors/
[LewisCowles]I noticed [tantek] solution as linked from microformats2 which uses an alternative method which avoids calling click. It has a comment about that being for browser compatibility.
[LewisCowles]I did also modify the script to have IE11 and non rel (class based) support. I also made it support the same id's tantek uses hoping that others using his work would find it easier
[LewisCowles]one way to make it easier would be to check classes on body tag, so that inversion (rtl) and other options could be seamlessly integrated without growing the code too much
[LewisCowles]Thanks, I saw that in the spec, but wasn't sure if clients and consumers were capable or if this was an odd case. Thanks I've merged alternate and canonical
[jeremycherfas]All very interesting in the abstract. I will be attempting to get my head around how Grav handles prevSibling and nextSibling during the coming week. The mf2 will be relatively easy once I have that working, but I’ve seen several issues reported.
[Ramiro_Ruiz]Hello, good Sunday everyone. Quick question, what is recommended if you want to reply to a blog post but they don’t receive webmentions or comments. Is posting a reply in your site still encouraged even that is possible the original author is not going to notice?