@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)
Zegnat!tell oodani looks like a definitive problem with Indiewebify, you can’t ever have multiple representative cards. Parsing specifies to always take the first one that matches the requirements. http://microformats.org/wiki/representative-h-card-parsing
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
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.
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
@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)
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.
...
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
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
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)
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)
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
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.