#kylewmheh, matt mullenweg didn't wait for OCSP to propagate before changing his cert on https://ma.tt/ ... I won't feel bad the next time I do that
#Loqikylewm: tantek left you a message 6 hours, 59 minutes ago: is it possible to send a single webmention to Bridgy Publish to get it to publish to all the POSSE destinations (e.g. both FB & Twitter) you've linked to from your permalink? E.g. with 'target=http://brid.gy/publish' ? http://indiewebcamp.com/irc/2015-11-08/line/1447007012870
#aaronpki was thinking about this today since i'm publishing h-events in my new top-level feed. if someone doesn't recognize how to render an h-event, i want them to do something sensible as a fallback
#ben_thatmustbemewhat do i do well you can say its invalid, but mf2 parser handles it, the question is, what do you do if someone has two
#aaronpkone way to handle the fallback is to make my post both an h-event and h-entry, so that if they don't recognize h-event they'll see the h-entry
#aaronpkbut at that point i can just not specify h-entry and just put a name and content property on the h-event so that the consumer finds those properties ignoring the type
#aaronpkso what i'm wondering is are there actually any real use cases for specifying more than one type?
#aaronpkcause if not, jf2 can just use the first mf2 type
#ben_thatmustbemewe are going at this from different sides, you are assuming it'd probably be better to pick known terms first though, like in this case
#aaronpki was assuming the mf2 parser returns them in the same order as the html
#aaronpkbut i haven't actually verified that now that i think about it
dannyid and [kevinmarks] joined the channel
#[kevinmarks]That is usually true for lists, but not dicts. PHP preserves dict creation order, python returns them in hash order, go randomises them so you don't accidentally rely on order
#ben_thatmustbemeaaronpk: the only reason for two classes I can think of is fallback. If that's the case and we want to have only 1 classes we have to take the fallback option always
snarfed joined the channel
#aaronpkadding a test suite to webmention.io now...
#aaronpkthis is likely what i will be working on during the plane flight back to portland tomorrow
#ben_thatmustbemetantek, aaronpk was trying to figure if there is a need to support multiple types (multiple h-*) ever? whats the use case? the only one i could come up with is fall back. This came up since jf2 tries to use only one single type, and shaners is using class="h-entry h-as-note"
#ben_thatmustbeme[aaronpk]: the end result is that i think it makes more sense to just pick known types out first, (prefer h-entry over h-blahblahblah)
#ben_thatmustbemeif we are only providing one class we destroy fallback otherwise
#ben_thatmustbemeif its well established enough the producer can provide it as h-blahblahblah without fall back, and my implementation will do the same
#ben_thatmustbemereally needs to think before he speaks, a lot of that is unclear
#GWGBased on the way I designed Post Kinds, my usage of the post type matches h-entry
#GWGWhich means if I ever do another top level property it needs to be a different post type
#ben_thatmustbemehuh, aaronpk, tantek, i wonder if it makes sense to figure out what h-* item it should pick first if more than one of the known h-* classes are set
#GWGI want to write a something on microformats to WordPress
#GWGSo is the post post type the equivalent of h-entry?
#GWGWhich would mean any other top level properties would need a custom post type
#petermolnarI'm trying to code the decision algorithm for finding the post type based on that is set for a post instead of setting it manually, but yes, it probably would if they are not the same as you already have
#GWGThe microformats wiki defines h-entry as episodic or datestamped content
#voxpellilike follow/unfollow which can both be represented as the activities of following and unfollowing (probably h-entries) and the actual relation state between A and B which would be rel-contact between h-cards
#tantekpops back in to see some post type plumbing discussions ;)
#tantekben_thatmustbeme: not sure what you're getting at re: h-entry and fallbacks
#ben_thatmustbemeso, if jf2 wants to only have 1 "type" (classes from mf2) and mf2's json format allows multiple h-* we need to select 1, we were trying to figure out the reason for every needing more than on in mf2, and really the only thing we can figure is that you provide h-entry as a fallback to h-mycustomthing
#ben_thatmustbemeif my service to convert mf2 to jf2 provides h-mycustomthing, it breaks the desired fallback the mf2 author included
#sensiblemnplease head over to #knownchat if you want to help me figure out how to get known running in a subdirectory using nginx
#ben_thatmustbemebut providing only the fallback option (in this case h-entry) it basically handicaps adoption of any new values
#voxpelliGWG: if one wants the check-out to publicly show then it needs to be included in ones feed based on when one checks out – and an event would likely be included in ones feed when it is created
#tantekben_thatmustbeme: a little. in practice not a lot of people have been publishing multiple h-* types
#tantekand in practice some of the more common cases like h-as-* have been largely abandoned
#voxpelliben_thatmustbeme: tantek: it's an interesting question though – should it be possible to use new types through some kind of progressive enhancement strategy?
#tantekvoxpelli: we have long thought so, e.g. "h-card h-person" or "h-card h-org"
#voxpelliwe had that problem with Activity Streams on Flattr – none of the existing types really suited us, but since Status.net was the only big deployed consumer we had to pick the least wrong type it supported
#voxpelliand could not define a better type that eg. StatusNet could then later have adopted
#tantekhaving to pick the "least wrong type" seems like a good summary critique of post type design assumptions
#tantekben_thatmustbeme: why not make type an array like category in the examples when there is more than one type?
#ben_thatmustbeme"h-entry h-review" huh, so it makes sense to do both of those?
#tantekthat seems like a "simple" way of handling it
#tantekand then anyone that actually cares about the type can go digging
#tantekin practice I think consuming code will be written to handle properties not types
#ben_thatmustbemewe had been trying to avoid that, simpler to consume if you know there is only one type
#voxpelli+1 on array, in order of preference (because classes in HTML are ordered, right?)
#tanteknah, simpler to consume if you ignore type and just look at properties
#voxpelliben_thatmustbeme: only simpler to consume initially, but since it makes progressive enhancement hard/impossible it will grow messy over time
#tantekthis is getting back to the problem of consuming-code design, where consuming code *thinks* it needs a type to do so something when in practice it actually needs to handle the presence/absence of properties
#ben_thatmustbemei disagree, as if you need a type, you end up having to figure out type from properties, which can be complex
#tantekI always wonder the impression of ordered classes/rel values comes from - nowhere has anyone ever said that - thus it must be something about the eyntax perhaps?
#ben_thatmustbemeyeah, aaronpk originally suggested just taking the first type, but "first" is actually random since its unordered
#voxpellitantek: hm, so it will always be up to the consumer then to pick which representation is the most fitting?
#tantekvoxpelli: rather, practical consumers will discover that no matter what "type" based code they write, they'll have to handle presence/absence of different properties
sammachin1 and [aaronpk] joined the channel
#[aaronpk]You can't keep doing posttypes-- when it's built into the microformats spec lol
#tantekso why not skip all the type-based code assumptions, and *only* implement presence/absence of different properties ?
#voxpelli+1, it would also show if there's some data that is now inferred from the type that should actually be explicitly stated on its own
#tantekfocusing on post types is a sign of inexperienced (like haven't actually built/shipped solutions that interop with a variety of other implementations) or short term thinking in terms of this kind of stuff
#[aaronpk]So should I publish my contact info in an h-entry on my home page?
#tantekfrankly, I'm now myself running into confronting even my shortlink single character type codes
#tantekben_thatmustbeme: for now for jf2, juss stick all the h-* object types into an array if more than one, just like category
#tantekand then anyone that complains, challenge them to produce URLs to real world examples
#rhiaroIf you're consuming, and someone gives you a type, and you know what properties to expect with that type, and you even trust the data you're consuming, you're probably *still* going to check for them before doing anything with them anyway, right?
#voxpelliwonders if any indie-reader would support consuming an h-item of h-item:s like an h-feed of h-entries
#rhiarohowever if you're super lazy or super trusting or have some kind of super generic consumed-data displaying thing, being given a type might be a useful shortcut. But most consuming code isn't going to be like that I suspect.
#tantekrhiaro: yes to " you're probably *still* going to check for them before doing anything with them anyway"
#ben_thatmustbeme#pointless arguement, types make sense for some, not for others
#voxpelliI think the only non h-entry types I have are h-card and h-feed – hard to distinguish between a profile and an article if not using h-card on the profile i guess?
#tantekben_thatmustbeme: nah, they make sense in theory until you start interoperating with the wild world of public web publishing ;)
#[aaronpk]If types really don't make sense then should the microformats spec stop using h-entry vs h-card vs others?
#rhiarohaving types internally in my system helps me query stuff more easily (because I definitely trust and know what to expect from my own data), but I would probably ignore types coming from external sources and just deal with properties
#singpolyma[aaronpk]: h-entry vs h-card improve authorability
#tantekcould we rebuild it and have it "try" to convert every h-*
#ben_thatmustbemeh-card is very useful for representative h-card, or rather, looking for person represented by a url
#rhiaroyeah so all my stuff on my site is h-entry and I've been meaning to add something into my mp endpoint that lets me specify a different mf type, but maybe I won't bother
#tantektypes as internal system cache based on property testing could make sense rhiaro
#ben_thatmustbemealthough i still contend the "note at a location" vs "checkin with text" are different things, but thats for my internal representation
#rhiarobut even h-event might not be necessary because you can figure that out from start and end times existing
#tantekpeople have over time often wanted to make up their own h-* objects, only because they didn't understand they could re-use an existing h-*
#tantekben_thatmustbeme: right, h-feed is an indication of publisher intent
#ben_thatmustbemeand in practice (for social) thats really all i see people using (in IWC anyway)
#tantekbut then maybe we can put any h-* as children of an h-feed
#tantekh-card has the use-case of more robust authorship discovery
#ben_thatmustbemewell, h-event, though i could see arguements that h-event doesn't really have enough need to be its own top level object
#voxpelliwhatever can be expressed as something else than a type probably should be
#voxpellisometimes the type might be the easy solution, but expressing the same value as a property could also be possible
#voxpellinot using types increases the composability of things
#rhiaroI maintain that top level objects that are similar enough to other top level objects property-wise yet still need to be displayed differently are the only ones that should have types. I'm not sure how many of those there really are.
#voxpelliit would be interesting to test and see if one could express them as an h-item through additional properties instead and if that would makes things more or less clear
#ben_thatmustbemerhiaro: i don't totally agree a note can't have a "location" as you can post a note about something, but again, this falls to your interpretation of some data, it does not work as a general rule for determining intent of the author of the data
#voxpellikevinmarks: did you see my tweet btw about possibility to add some CSS to "img.webmention-error" to make failed images look better on your site?
#ben_thatmustbemerhiaro: case is point "Rattlesnake (a place a few doors down from our office) is really sketchy, gave my co-worker food poisoning" I am not checking in, but i cite the location for others
#ben_thatmustbemei am specifically not checking in, because i am not there
#tantekben_thatmustbeme: h-event has the use-case currently of h2vx.com - that is, robust automatic .ics file generation (because calendar programs / sites subscribe to that)
#ben_thatmustbemecan you determine that based on the properties though?
#tantekit maybe reasonable to keep going and make h-item the generic thing that you use when you have no need for a specific top level type
#tantekthe irony there is that then that naming lines up with RSS <item>
#voxpelliben_thatmustbeme: rhiaro: check-in could be done same way as bookmarking / replies etc though? Add an extra "u-in-reply-to"-style to the geo-tag? "p-check-in-at"?
#ben_thatmustbemewhats the difference between item and entry any way?
#tantekben_thatmustbeme: always good to check for examples in response to queries about "could be done"
#tantekas in, "could be done?" should be replied with "how is it done currently?"
#ben_thatmustbemevoxpelli: might be good to throw that in to a brain-storming
#tantekbrainstorms should consider existing practices
#ben_thatmustbemetantek: problem with that philosophy is that is discourages experimentation. "no one else is publishing, so its not needed", but no one is publishing it because there is no option for it
#voxpellitantek: only existing example of marking up whether a location is a checkin or not that I see while skimming through is "h-as-checkin" – and well, that's what started this discussion ;)
#rhiaroI thought it was standard to check all usage not just indieweb?
#voxpelliwe're also lacking consumers, publishers we have plenty, but whether the publishes data is ambiguous might not truly surface until we have a wide variety of readers using that content
#ben_thatmustbemeas thats just reinforcing current indieweb markup, not expressing good practice to look outside of indieweb
#tantekben_thatmustbeme: not at all! it's completely correct to say look at indieweb examples - no part of that excludes looking further ;)
#tantekeven if they lack their research, you can and should do better, set a better example for the next person that comes along and sees how/what they should do
#gRegorLoveDespite having an HTML5 player, /Soundcloud apparently still requires Flash, at least on desktop. No audio and a notice "It looks like you have a Flash blocker browser setting or extension. Please enable Flash to hear this track."
#kevinmarksyep, it's crap. you can switch browser signature to iOS
#GWGAll the event type posts could be grouped together, and all the entry type posts could be. Now I have to rethink.
bengo joined the channel
#GWGI may still do it that way, as it makes sense in terms of them not being in the main feed, but in a separate activity feed.
funwhilelost and friedcell joined the channel
#gRegorLoveGWG: I think a feed of "everything" makes sense, and then separate feeds for each type. Perhaps an option to build hybrid feeds of only selected posts, too. That would give the most flexibility.
#GWGsnarfed: It isn't just that. If I build events as a custom post type in WordPress, I can create a Post UI specifically for activity posts. There's a functional reason.
cleverdevil, bengo, tvn_, shiflett and M-RyanRix joined the channel