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
[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]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
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?
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
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][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]!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
[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.
[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
[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?”
[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.
[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.
[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
[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
[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]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.
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
[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
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