eli_oat, snarfed, Mandrake, jjuran, [jgmac1106], [kevinmarks], chrisaldrich and renem joined the channel
#@JmacDotOrgOpinionated Perl nerds: Is “Web::Mention” a good name for an implementation of a tech called “Webmention”, or should I avoid cuteness and go for the banal brutality of “Web::Webmention” or whatever. (“Webmention” is neither my invention nor my name for it.) (twitter.com/_/status/987147558152794112)
#oodaniyeah i noticed that! it /does/ show you the first one it found, but it shouldn't really be complaining that there are multiple since. there aren't
#ZegnatSounds like you got it all figured out then :)
Mandrake and swentel joined the channel
#petermolnarcan a h-review be nested in a h-entry? would it make sense?
#ZegnatAnything can be nested. But what is the usecase?
#petermolnarthat's why I'm asking; I have a long entry about a smartphone and fixes to it, but I want to add a rating to it
#petermolnarso the thought is to nest the h-review in the h-entry
#petermolnarbut I'm uncertain if things would parse it
[jgmac1106] joined the channel
#ZegnatHmm. Not sure. Who are you envisioning as the consumer though? h-feed readers will still be displaying the contents as long as it is part of the h-entry’s e-content.
#ZegnatAnd if you want Google to pick up on it, it doesn’t really matter where on the page the review markup is, I believe.
eli_oat, [jgmac1106] and [matthilt] joined the channel
#swentelaaronpk, do you have an example somewhere of a webmention with an rsvp in the payload ?
#LoqiAn RSVP is a reply to an event post that says whether the sender is or is not attending, might attend, or is just interested in the event https://indieweb.org/rsvp
#swentelwell, I've looked there, which is great for microformatting, but wanted to see where it's nested in the payload hook that gets send then in a webmention
#LoqiA review is an evaluation of a product or service, usually involving a written description, but can also be limited to a numerical scale https://indieweb.org/review
#aaronpkswentel: sorry I need to add more docs to webmention.io. But the Web hooks use the jf2 format, so if you run an rsvp post through XRay that's what you'll get from webmention.io
KartikPrabhu joined the channel
#@sandhawke↩️ So... how do you feel about the WG *also* standardizing stuff that competes with AS and AP, including WebMention, Micropub, and WebSub? Once the group gave up on convergence, some folks moving forward with AS/AP wasn't really an obstacle. (twitter.com/_/status/987353633657425920)
KartikPrabhu joined the channel
#aaronpkWow what a weird parsing bug on some of my last mentions from ownyourswarm
#aaronpkXRay gets a weird author name from it, and I don't understand why
#Loqi[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML.
...
#aaronpk"name" is the h-entry vocab for it , maybe I should rename it in the UI
#KartikPrabhumaybe something like "post name" would be clearer
#skippyAs a relative newbie, I'm used to my content have "titles", not "names". the Quill UI makes sense to me; but the post body was surprising until I read the spec.
#aaronpkOh maybe it's been a while since I've gotten a comment from swarm! That seems entirely possible that it's been longer ago than the mf2 parser update that changed the implied name parsing
#skippyoh, and TIL that there is no MF2 "note". Notes are just entries without titles. Hrm.
#KartikPrabhuskippy: yes, those are intentional decisions to prevent blowing up of many vocabularies which do the same thing
#LoqiPost Type Discovery specifies an algorithm for determining the type of a post by what properties it has and potentially what value(s) they have, which helps avoid the need for explicit post types that are being abandoned by modern post creation UIs https://indieweb.org/post-type-discovery
#Zegnataaronpk, I think the php-mf2 alpha is only whitespace testing? Not sure if anything is in the alpha that is neccessary for release.
snarfed and tantek joined the channel
#skippythe MP spec defines "in-reply-to" but does not specifically address "repost".
#skippyAre MP clients scraping the source site for posting locally, or do folks do that manually and include a "repost of" MP attribute?
#KartikPrabhumicropub clients should not be doing any scraping
singpolyma joined the channel
#skippywhat are workflow examples of reposts? I assume many will use Bridgy to backfeed; but i'm more interested in POSSE.
#LoqiIt looks like we don't have a page for "workflow examples of reposts" yet. Would you like to create it? (Or just say "workflow examples of reposts is ____", a sentence describing the term)
#ZegnatMP spec should also not be defining vocabulary ...
#ZegnatSkippy, any MP client may submit any valid microformats JSON representation. So if someone is reposting, they should submit that as a property on the entry they are sending to their MP endpoint
#@MisterKapowskiManaged to get things working 😀 mainly by switching to the IndieAuth PHP client, instead of rolling my own code with Guzzle. Then I figured out why it wasn’t working, but didn’t see the point in switching back… (twitter.com/_/status/987386881225773056)
snarfed and AngeloGladding joined the channel
#sknebelaaronpk: so this is a terrible hack, but for microsub demo-purposes you could maybe make an aperture instance and block all POST-requests to it? then it'd be effectively read-only
#aaronpkoh like so others can make microsub api requests to it?
#aaronpknot a terrible idea. i could make it not require any authenication also.
#sknebelor make some automatic auth, since the clients probably expect being able to auth
#aaronpkthere are some really tricky examples in the tests
#ZegnatSo I was just doing some minor rewriting to the u- parsing to move resolution down the chain (per mf parsing spec issue #10). The move made me fail one test, which isn’t too shabby.