#ZegnatSeems like a valid way to do things, [jgmac1106]. As long as parsers that you want to handle it actually support parsing h-entry elements by fragment ID
#GWGI need to write that out as part of the algorithm
#ZegnatDo we actually have a start for that algorithm somewhere? A “which mf2 object to return for a given URL” algorithm?
#[jgmac1106]looks pretty good, but in that one I may have the webmention being sent to the wrong url there as I would want it going to the url of the evidence
#[jgmac1106]well I can't tell Marquis how to license, because he is a student worker I have to pay him an unfair below market rate...So I am letting him own the code and choose the license but just give me and anyone who buys me a...blah blah..legal stuff
#[jgmac1106]from discussions he is going to choose an Open Source option
#[jgmac1106]and i am working to Open Source ReVIEW this month. For other legal reasons I had to wait until end of July of this year
#[jgmac1106]Using Kirby actually to build the Course Builder and Badge Maker....Unviersity paperwork taking forever and a day to get through payroll....I am excited to start
#GWGZegnat, will start on the h-feed page re discovery
#GWGYou know, I can't find an h-feed with a photo property in the wild so far
#GWGBut the people on the h-feed page aren't exactly current
#MrKapowskiI'm planning to bake h-feed into the WP theme I'm working on, so I'll be interested in if there are any recommendations come out of your review
#[jgmac1106][grantcodes] as a call back to yesterday's discussion about dt-updated would there be an easy way in Glitch to use the Git checkpoints to display the last time a page was updated rather than doing it manually?
[tantek], farrah, gregjeanmart[m] and [schmarty] joined the channel
#MrKapowskiHow do people feel about h-feed for comments/webmentions, etc, on a permalink page? I'm thinking specifically as embedded within an h-entry. Good idea? Bad idea? Irrelevant-because-nothing-supports-it idea?
#[jgmac1106]MrKapowski I always made a comment feed in my classroom planets, encourages greater interaction would do the same with webmentions if I built using h-feeds and not rss
#aaronpkso you can click"view comment thread" on a post
#aaronpkInstead of leaving Monocle to view the original post
#KartikPrabhuaaronpk: is a nested h-feed necesary for that?
#KartikPrabhuMonocole could retrieve a list of "p-comment"s directly
#MrKapowskiI meant XRay/Parse This, etc, but I just realised why they weren't working with my test page (my fault :-) )
#MrKapowskithere's a typo in my markup. Once I get a chance to fix that I expect it'll work
#KartikPrabhuMrKapowski: I would suggest not using excessive markup for your theme for now. If /readers add support of this later, then you could add it to your theme then
#MrKapowskiit's only an extra couple of classes to implement… I'm not changing the structure of anything to add it, and lean markup is one of my goals as it is :)
[manton] joined the channel
#[manton][grantcodes] I noticed that the new Together no longer works with Micro.blog's Microsub endpoint ("Error loading channels"). Any tips for what might have changed? Micro.blog still works with Monocle.
[grantcodes] joined the channel
#[grantcodes]Hmm maybe the same thing davidbeal has been experiencing
#[grantcodes]If you open up the console, there should be a link to open an issue with all the details
#[grantcodes]Looking in the database, it has your token and endpoints stored. (although not necessarily correct)
[miklb], [tonz] and gRegorLove joined the channel
#aaronpkKartikPrabhu: yes of course, I was not suggesting any particular markup
[jeremycherfas], [schmarty], dietricha and [grantcodes] joined the channel
#[grantcodes]!tell [manton] Figured out the microsub issue. The data fetching I am using adds a trailing slash onto all urls by default for some reason. And your endpoint returns null with a slash on the end
#Loqimulti-factor authentication (commonly two-factor authentication, abbreviated 2FA or TFA) is an authentication process that requires at least a second component to a standard authentication method https://indieweb.org/two-factor
#[grantcodes]Random thought about your privateish pages [snarfed]: have you thought about webmentions and microformats? For example if I like it my site is going to automatically grab a copy of any mf2 on your hidden pages
#[snarfed]grantcodes sure. i'm trying to implement privacy and unlistedness, _not_ "security," ie not preventing other people from individually generating partial copies like that
#[snarfed]having said that, likes of private posts would do the same thing, right?
[fluffy] joined the channel
#[fluffy]Unlisted posts are fairly straightforward to support webmentions from, although sending a mention from an unlisted page to a public page then makes the unlisted page de-facto public.
#[fluffy]They’re just now listed on someone else’s site that you can’t control.
#[snarfed]right. grant meant webmentions _to_ unlisted pages.
#[eddie]I think one thing to help with unlisted and private pages would be adopting p-visibility as a possible mf2 attribute. Something I'm planning to experiment with once I've got the basics of my iOS apps. That would allow me to basically make any replies to posts that are unlisted or private into private posts
#[snarfed]huh. that implies writing is restricted. wonder if there's an alternative with an eyeball instead of pen
#[fluffy]I don’t know why emoji has a “closed padlock with an ink pen” emoji but it seems like it’s specifically for this use case 🙂
#[snarfed]apologizes and slowly backs away from design
#[fluffy]for unlisted-but-hidden I’d probably use 🔓 (open padlock)
#[fluffy]although it’s kind of a subtle distinction, at least on the macOS font.
#[fluffy]anyway I’d love to see a `p-visibility` or similar in addition to visual cues. Make it so that micropub et al clients can at least present a warning like “hey are you sure you want to do that?”
#[eddie]Yep, exactly. I think with unlisted and private posts becoming a key part of people's set ups over the next year, I think that'll be needed
#[fluffy]also I’m trying to figure out how I can reasonably receive webmentions on my actually-private posts. Right now if someone’s unauthorized they get redirected to another page to actually handle the login.
#[eddie]So I'm gonna add it to my stuff when I have the time and we'll see if others follow suit
#[eddie]Yeah webmentions to private posts is difficult currently
#[fluffy]So the webmention endpoint would probably do the same unless it’s authorized via AutoAuth. and I don’t like the idea of giving a potentially third-party service read access to everything.
#[eddie]I think AutoAuth has the option of a "realm" which I don't fully understand
#[eddie]but maybe you could separate posts into different realms? or even have a realm per post?
#[fluffy]I suppose I could also make it so the initial page access doesn’t redirect and just publishes the webmention endpoint for the actual target page but that gets tricky too
#[eddie]then the token for that realm would apply to a subset of your posts
#[fluffy]I’m not sure what a “realm” is in this context
#[fluffy]I mean personally I’m not a fan of other peoples’ replies to my private stuff being potentially broadcast on the public Internet anyway
#[fluffy]I’d much rather people use my own native comments (which are disqus at present but that’s beside the point) to reply to things that I have locked down
#[eddie]If you don't want replies to private stuff I'd remove the webmention endpoint on private posts
#[eddie]I want people to reply from their own site on private stuff, I just want to ensure they make them private posts as well
#[fluffy]yeah I guess I could do that, the templates could just be like `{% if not entry.is_private %}<link rel="webmention" ...>{% endif %}`
#[fluffy]I hope that this becomes a problem I have to address in the future! But for now things are too scattered/vague for me to see any reason to worry about engineering a fix.
#[fluffy]as it stands, all of my privacy-post-enabled friends are either using an RSS reader or manually polling my site for updates, and the ones with a reader just see a placeholder stub like “🔏 Private entry [Jhs]” which is the compromise I decided on.
#[fluffy]basically the most recent unauthorized entry gets a stub entry with a login link and the initials of the actual post title.
#[fluffy]If someone happens to use a cookie jar or similar to share their login session cookie with their feed reader, they’ll get the full post.
#[fluffy]ooh and I just realized I don’t have the privacy indicator in the title in that case
#[fluffy]not that I have any evidence that anyone’s actually gotten that working though.
#[fluffy]this is a thing I’m hoping AutoAuth makes possible in the future but that requires soooo much stuff to happen on the reader side before it will.
#[fluffy]nice, I just verified that a cookie jar WILL work with a feed reader, by giving it my admin session’s cookie.
#GWG"Do we actually have a start for that algorithm somewhere? A “which mf2 object to return for a given URL” algorithm?" - I asked where we should put such a thing
#[jgmac1106]started searching Google when someone showed me: javascript:alert(document.lastModified) but that is just a popup modal so I started googling ways to call it HTML
#GWGI want to document the work Parse This does to standardize output and share it
#Loqi[Greg McVerry] Lesson One: Images, Headers, Links and Text
#Loqi[Greg McVerry] Lesson One: Images, Headers, Links and Text
#[tantek]GWG I linked to where it was described, and no it doesn't have to be after parsing, in fact you could do it much more efficiently if you go "pull out" the fragment element subtree first and just parse that
#GWG[tantek] I have a bunch of issues I would want to go over.
#GWGI was trying to find a place to document all of them for people writing similar code
#[tantek]GWG, see above re: my request to file an issue for that
#[tantek]yes and it's quite valuable - good work there GWG++
#LoqiGWG has 31 karma in this channel over the last year (158 in all channels)
#aaronpkXRay parses from a fragment url but I can't remember if that's XRay finding the fragment and handing just that part off to the mf2 parser or what