#[frank][jackjamieson] does Yarns already support API calls like Aperture does? I tried a quick test yesterday but got some 404-like errors. I’m not at my machine now, I can share more specifics later if you want. Or make a Github issue?
ichoquo0Aigh9ie, [jeremycherfas], [tonz] and [frank] joined the channel
#[frank]@GWG and [jackjamieson], it turned out to be a scope problem on my side. I updated my IndieAuth plugin and now I can select scopes per token. Which is awesome.
#[frank]So my initial script works with any microsub server. Which to me feels pretty awesome and gives me more reason to continue and improve it.
danyao, voxpelli, willnorris, ludovicchabant and mattl joined the channel
#[frank]First I need to update my NodeJS skills. As I am not a programmer on a daily basis, my knowledge on the language and design patterns faded out a bit.
#[tonz][frank] cool, so I might test it later with Yarns, to migrate my current RSS feeds into it.
#[tonz]From your demo I understood you imported everything into a specific channel. Is there a way to specify channel upon import? Or should I import in badges into channels I want to have?
#sknebel!tell cleverdevil,Eddie always feel free to ask Zegnat or me about "do these microformats look right"
#petermolnarI keep thinking about a micropub service for static sites that is similar to webmention.io - you publish, it stores it temporarily, allows it to be queried and deleted, or auto-delete in X days
#petermolnarthe security devil inside however tells me not to
#petermolnarlike really not to, because eventually, it will be used to transfer nasty things
#ZegnatYes. It'll basically turn into a micropub powered pastebin.
[frank] joined the channel
#[frank][tonz] For now you would have to manually add the channel ID in your .env file to run the script. It just dumps all your subs in this channel. So it misses the granularity you need for your circles. This will be added eventually ofcourse. But this is for later iterations.
jgmac1106, [philhawksworth], [calumryan], paulrobertlloyd and [jgmac1106] joined the channel
#GWGI'm going to be working on optimizing two sets of code that retrieve and process URLs at once.
#GWGApparently, my parsing code tries to extract so much information, it is slowing things down
[Rose], [jgmac1106], [jeremycherfas] and jgmac1106 joined the channel
#jgmac1106!tell jeremycherfas the getting started with php guide in the Kirby documentation is one of the bteer beginner guides I have come across: https://getkirby.com/docs/cookbook/templating/php-templates many not use it for my site in the end but its turning into a great tool to learn PHP
KartikPrabhu and [jackjamieson] joined the channel
#[jackjamieson]!tell [chrisaldrich] Thanks for the offer about documentation. I might just start writing it out and then ask you for a second set of eyes. You’re quite good at documentation so I imagine you might catch omissions or areas for improvement
#[jeremycherfas]That is good news [jgmac1106] Glad you found it.
#Loqi[jeremycherfas]: jgmac1106 left you a message 1 hour, 13 minutes ago: the getting started with php guide in the Kirby documentation is one of the bteer beginner guides I have come across: https://getkirby.com/docs/cookbook/templating/php-templates many not use it for my site in the end but its turning into a great tool to learn PHP
[tonz], [Rose], [jgmac1106], KartikPrabhu, [Zegnat], cweiske, ingoogni, [calumryan], snarfed, gRegorLove, [tantek], Katharina, [frank], leg, jjuran, snarfed1 and [jeremycherfas] joined the channel
#[jeremycherfas][aaronpk] Can you please explain briefly how Resume with geofence works in Compass. I want to obscure some locations. Should I Resume with geofence when I am at that location?
#[tantek]I have vague recollections of [kevinmarks] explaining the two different distinct uses of RSS feeds/elements for link blogs vs. a feed of your blog
#[tantek]right now we have h-feed for "feed of your blog" fairly well defined. What we don't have defined (e.g. for publisher / consuming app interop) is how you would use h-feed to represent / publish a link blog
#[tantek]In particular the way RSS did it, you didn't need your own permalinks for the items
#[tantek]the "link" element (IIRC) would 'just' point to the external thing you're linking to, not your own permalink
#[tantek]particularly interested in folks who have long experience/history with how this stuff worked / works today(?), e.g. maybe [manton] knows
#LoqiIt looks like we don't have a page for "posts about the" yet. Would you like to create it? (Or just say "posts about the is ____", a sentence describing the term)
#[tantek]concrete example, I'd like to add h-feed markup to https://indieweb.org/Posts_about_the_IndieWeb such that it was well defined how to both consume it directly as a "link blog", as well as how to canonically convert it to the RSS feed equivalent of a link blog
#[manton]Mostly it's a usability issue because it's not consistently implemented in feed readers.
#[tantek]this: "Good conventions for blogging have been at a standstill for years. "
#[tantek][manton] is it "close enough" that we could document the more common conventions across some/most feed readers?
#[manton]Good question. I think it's worth revisiting. My main goal with that post was to discourage people from having feeds like this unless they really needed it to work that way.
#[tantek]I understand the discouragement. And I think I agree in spirit, that is, encouraging feeds of permalinks back to your own site, instead of feeds of links to other sites.
#[tantek]However, I think the "one page feed" use-case is strong enough to merit solving in a consistent and interoperable way.
#[manton]Yes, that's an exception where it makes sense, I agree. When you have a list that is really just pointing elsewhere without blog-like commentary, etc. (Again, feed readers could handle this better, but that is worth documenting.)
#[tantek]we can come up with a "best practice" for how a publisher could/should use h-feed for this
#[tantek]similarly, if you know the RSS link blog best practice, we can likely get Granary.io to implement both halves so it can consume an h-feed link blog and produce a canonical RSS link blog
#[tantek]then that just leaves documenting *which* feed readers actually handle that RSS link blog "correctly", praising them for it, documenting *what* they are doing in common that makes it work, and then encouraging other feed readers to recognize and treat such RSS link blogs accordingly
#snarfedgranary supports mf2 html input and rss output now, feel free to try and file issues
#[tantek]I believe we can collectively, openly do each of these steps one by one, and get to a better point of convergence, even / especially with current feed readers
#[tantek]snarfed, yes that's the support I was referring to
#[tantek]I'm positing that there may be some specific details that we'd want Granary to follow for the h-feed linkblog to RSS linkblog feed conversion
#[tantek]we could use the existing pattern of h-cite instead of h-entry to indicate the semantic of a linkblog post rather than a blog post
#[tantek]and then file an issue on Granary to support recognizing an h-feed of h-cite(s) explicitly as an h-feed linkblog, and then do the special work (if any) to convert it to an RSS linkblog (per [manton]'s post / analysis of how one should do so)
[frank] joined the channel
#[frank]Reading up on the conversation above re link-blog RSS feeds. I remember [manton]’s post as well, will have to re-read it. For instance Pinboard does it quite well. Their feeds redirect to the source directly instead of the Pinboard page. But looking at the source, it's all RDF, so different spec then RSS...
#[manton]Looking at that "Posts about the IndieWeb" page, doesn't look like it's marked up as an h-feed yet, so Granary isn't sure what to do with it. (Unless I'm missing something.)
#Loqih-feed is a microformats2 draft specification with a top level feed object to contain h-entry posts and optionally a common author https://indieweb.org/h-feed
#[tantek][manton] right it's marked up just with individual h-cite markup for the list items
#[frank]Looks interesting [tantek] and should work for the usecase
snarfed joined the channel
#[frank]Daring Fireball's feed (mentioned in Manton's post) actually has some interesting use of the <link>-element. Per item he actually has three. For instance his latest post has these three link-items in his feed:
#[frank]In the end it's up to the readers how they implement it. The RSS 2.0 specs say link should point the permalink, where guid might be a way to link to the external URL.
#[manton]Running the wiki page through Granary now, the RSS looks about like what I'd expect: <link> pointing to the external post.
snarfed joined the channel
#[frank]Picking up the feed from Granary in my feedreader gives me exactly how I want it
#[tantek]wait what this is already working for you now [frank]?
#[tantek]all I did was add an explicit h-feed to the page, with p-name and p-summary
#aaronpk[jeremycherfas]: the "resume with geofence" feature is an experiment in battery saving. compass isn't meant to have any privacy features because it's something you run yourself and can choose how to expose that data publicly when you want
#gRegorLovePosts about the IndieWeb mf2 feed is okay in Monocle, too. Headline with the date permalink as the external link. No author name though.