[iambismark], [matpacker], renem, [chrisaldrich], [cleverdevil], tantek__, ben_thatmustbeme, miklb_ and [eddie] joined the channel; mblaney and miklb_ left the channel
#GWGOkay, extraction code for manifest with fallback written. Next need to hook it up to something
#GWGAnyone have redirect_uri on their client? Want to make sure it picks them up.
#LoqiIt looks like we don't have a page for "event embed" yet. Would you like to create it?_ (Or just say "event embed is ____", a sentence describing the term)
#LoqiIt looks like we don't have a page for "calendar embed" yet. Would you like to create it? (Or just say "calendar embed is ____", a sentence describing the term)
#tantek__calendar embeds are more common so I'll go with that
#tantek__calendar embed is a feature of [[event]] hosting sites that allows a series of events (sometimes just one) to be embedded into another site, supported by [[silos]] like [[Google Calendar]], [[Eventbrite]], and [[Facebook]].
#Loqi[Michael Bishop] Tonight is our first Open Hack night to pick up where we left off from National Day of Civic Hacking. We’ll be meeting every Wednesday if you can join us this week.
#tantek__miklb, definitely, looks like a meetup embed! would be great example to add (or maybe it's worth splitting off /event_embed as a separate thing?)
#miklb_not sure. Was purely a coincidence that I was creating that post when I saw your activity in the channel
#miklb_related, it looks just fine in Together which is exciting as I'm still using 2016 with the mf2 plugin
#Ruxtontantek__: indingenous reader on Android shows RSVP action for events, starts a new RSVP post where you select yes/no/maybe/interested - https://puu.sh/Bin2c/bdcb4f9c92.png
#tantek__Ruxton: that is very cool! If you have my site in your reader, did you see such buttons for the recent indie event I posted (2nd to most recent post)
jjuran joined the channel
#petermolnarZegnat: you've recently had an interesting CSS experience, it seems like I'm having one as well: the 3px bottom border on my site's main menu are becoming trapezoids o.O
#ZegnatYeah, og: was discussed as an option, the biggest downside of og: is that there wasn’t a way to identify a page as an application unless we wanted to define our own namespace :(
#ZegnatI should maybe add og: data to the survey as well
#GWGI just assume many web pages end up putting in og:title for other reasons, so if nothing else is there, I pull it as it is often better than the title tag
#ZegnatNot sure what the good way is to fallback to application-name when you don’t know what language to pick. Especially if you maybe are taking other information from the manifest file, as you have no way of knowing what language manifest file you were given.
#ZegnatThere is an interesting problem with the application-name fallback as well. application-name can explicitly be multilingual per HTML spec (which is amazing!) but web app manifest has removed all multilingual aspects, recommending instead the server supplies separate manifests for separate languages.
#sknebelsomething like wordpress has a configured UI langauge
#sknebel(which is interesting: make the requests to find the manifest with set language headers to get the right one? is that how the manifest discovery is supposed to work?)
#ZegnatBut its a bit double edged. Say you `accept-language: la` and get a manifest file back. You have no idea if the website really did offer a Latin version, or just gave you their default. And if they gave you their default, what language application-name fallback do you use? You don’t know their default.
#sknebelI'm not sure why the fallback has to match the manifest?
#LoqiInternationalization (AKA internationalisation, i18n; localization, l10n.) is the process of adapting software/content to various languages https://indieweb.org/i18n
#sknebelit's only proposing a different mechanism for it, isn't it?
benwerd, koddsson and KevinMarks joined the channel
#Zegnatsknebel, yeah, it is proposing a different way of doing the same i18n. I am just not sure it is a better way. How often do we see conneg go right? How many are going to craft multiple manifest files? I think there was probably a reason for the HTML5 way of offering translations within the same document.
#ZegnatUgh, that horcrux metaphor is wrong. Horcrux aren’t fragmented :P
#ZegnatI seem to recall checking that out and disliking it a lot, haha
#aaronpkit's definitely weird, but it does the job super well
#aaronpki was able to write a filter to remove all css classes except ones that are microformats classes, which was neat
jackjamieson joined the channel
#ZegnatThis is why I didn’t like HTML Purifier: it has both ForbiddenAttributes and AllowedAttributes configurations. Hard to figure out exactly where it would be removing what
#sknebelaaronpk: where exactly did that issue come up right now?
#aaronpktrying to allow inline style height attributes on images
#aaronpkthe actual post is more like <div class="h-entry"><div class="e-content"><p>sample emoji <img src="emoji.png"></p></div></div> so doesn't trigger it
#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/PTD
KevinMarks joined the channel
#ZegnatThat’s the full answer ^^^ the micropub endpoint could run PTD on the mf2 object it recieved. This will tell it if it was an article or note (or something else entirely)
#ZegnatShould probably just open PRs for manifest files for him too... Hmm. This might be a nice little task for tomorrow morning!
snarfed joined the channel
#tantek__Zegnat: re: WAM and fallback, I think we should only do the fallback in the spec (meta application-name, link rel icon) and not go down the path of rando proprietary values (apple-touch-icon)
snarfed joined the channel
#tantek__and aaronpk noted that manifest 404 came from a copy/paste of setting up icon rels
#tantek__something that did favicons and gave you markup to copy/paste (also a good reason not just copy/paste a block of meta markup)
#ZegnatI know. It just skewed the statistics on manifest usage in the first iteration of the survey. Statistics have been fixed by [eddie] though.
#ZegnatI am just doing discovery to see what clients are publishing. Felt like the correct first step in figuring out what things may replace h-app
#tantek__as long as there is rel=icon, we can ignore the others
#tantek__what would be more interesting is if there were cases with proprietary markup *only*
#ZegnatThe survey data did surface something else that I need to bring up in mf2 parsing. I was using the rel parser from the mf2 parser to find the URLs, and rel-icon is super useless there because we aren’t keeping the `sizes` attribute
#ZegnatNot in the survey, so far, tantek__ :) So that was a good thing to confirm too
#tantek__great, so it confirmed we can ignore proprietary icon markup
[grantcodes] joined the channel
#GWGI am tracking sizes in my pending implementation as a fallback to manifest
[cleverdevil] joined the channel
#Zegnattantek__, do you know if there is some clever way to pick the correct language application-name fallback?
eli_oat, dougbeal|mb1, rhiaro, renem, [pfefferle], KartikPrabhu and [jgmac1106] joined the channel
#snarfedhey GWG, re micropub on localhost allowing missing token (https://github.com/snarfed/wordpress-micropub/pull/162#discussion_r212028124), i'm not sure when it was removed, but i'd like to keep it, built in, and not change to requiring users to write PHP code to handle a filter. mind adding the built in behavior back, in a new PR?
#snarfed(asking here instead of in #-wordpress to avoid distracting them from a useful ongoing conversation :P)
#LoqiA disclosure is a bit of content, typically on a home page, on an indie web site that proactively discloses some aspect about the site that the site owner wants the user to explicitly be aware of https://indieweb.org/privacy_policy
[schmarty] joined the channel
#Zegnat[kevinmarks], you can probably just use my local version? I haven’t looked at it for a while though. Maybe I should brush it up
#Loqi[Zegnat] verify-me-locally: A spin-off of @kevinmarks’ verify-me without external dependencies.
KevinMarks_, leg, KevinMarks, KartikPrabhu and barpthewire joined the channel
#NinjaTrappeurHey indieweb! I'm a having a problem related to webmentions. I have been stuck for the last 2 days with this, I think I could use some of your brain power :) It's a bit too long for a chat message, here's the problem: https://alternativebit.fr/rand/webmentionioweird/
#Loqi[NinjaTrappeur] Confusing Behaviour when Integrating with webmention.io
#aaronpkNinjaTrappeur: did you try %20 instead of +?
#GWGsnarfed, I will restore a localhost override, but suggest WP_DEBUG be required
#snarfedGWG: thanks! what's your concern? what problem are you hoping to avoid?
#aaronpksknebel: i don't think a space has ever been a valid character for a path
#NinjaTrappeuraaronpk, you're absolutely right, the actual RFC about this is here: https://www.ietf.org/rfc/rfc2396.txt (section 2.4.1) . Interesting rabbit hole, I guess I can now go to sleep a bit less ignorant :)
#@ndwExploring webmentions (mostly implemented) took me back through some micro formats stuff. So angry/sad/frustrated to see namespaces “fixed” by using “-“ instead of “:” and removing any extensibility. You got to h- and u- first! You win, whatever you are! (twitter.com/_/status/1032381785047425024)
gRegorLove, miklb__ and tantek__ joined the channel
#snarfedGWG: many reasons. do they change your work at all? probably not worth enumerating them really.
tantek joined the channel
#GWGI just wonder because I like things under my control
KartikPrabhu joined the channel
#snarfedheh, a luxury we sadly have little of with software we ship. all we can control is the code, config, and docs, and even those aren't foolproof.
#snarfed...which is one reason it's easier in many ways to build services instead
#GWGWordPress isn't built by me, but I have more control
#tantek__though then Zegnat filed an issue for mf2 parsers not picking up the "sizes" attribute in link tags, but it's like wait, if you're using rel=icon you're already not relying on a microformats parser
#tantek__so it doesn't make much sense to me (issue on mf2 parsing for a use-case that is specifically about *not* using an mf2 parser)
#tantek__gRegorLove: tl;dr - some devs would rather do another http request and parse JSON, than use mf2 parser apparently
#sknebelbecause some questioning the use of microformats means nobody should use a microformats parser for it, and potential issues in related areas should not be noted if they don't perfectly fit in the story?
#tantek__sknebel, point is, if you're using a mf2 parser, you can already use the h-ap
#sknebelso we assume that everyone will be publishing WAM and microformats, despite at least part of the reasoning for WAM just yesterday (or the day before?) was that WAM is an easier sell than microformats to e.g. the Oauth groups?
#tantek__consuming a JSON side-file is *trendier* for webdevs, and apparently more palatable to OAuth groups
#tantek__there is no one "easier sell" to everyone
#sknebeleven in our community, the rel=icon was pretty common, on pages without h-x-app
#sknebelif we consider taking rel=icon into account, it makes sense that a microformats parser can do that
#sknebel(mentioning WAM was actually wrong, since discovery for that's already covered with what the parser can do. bit late here...)
#sknebel(I personally think all reasonably widely accepted link-rel-attributes should be covered by the parsers, since it's a very easy addition to the parser and the effort for the parser users that might want a rel-parser too to add another parsing thing just to see the properties the microformats parser doesn't cover is pretty annoying in comparison)
#tantek__I suppose we can try to figure out an optimal order or something for discovery, e.g. look h-app, then WAM, then WAM fallbacks
#tantek__aaronpk, point being, if you (web dev) already don't want to do mf2 parsing, then by the time you get to step 3, WAM fallbacks, you're not using an mf2 parser (you started with that assumption) so there is no need for the mf2 parser to cater to you
#tantek__do I need to write out the proof, Geometry Class style?
#sknebelso I as a web dev willing to use a microformats parser (since I already use it for all kinds of things) now get to find another parser just to find the size= on rel=icons if a site forces me to fall back to that, because ... ?
#tantek__aaronpk, also, in all your usage of h-app, did you ever get use-case / feature requests for app photos of different sizes with sizes property or something?
#tantek__no sknebel, you as a web dev using an mf2 parser, parse the h-app and you're done
#sknebelokay, so everyone is going to publish h-app
#sknebeleven in our community they don't, but they will
#tantek__depending on tools and consuming code iteration
#tantek__but yes, if you make it easier / more useful, then people will
#tantek__heck maybe even some sort of script that auto-converts your h-app to WAM.json
#tantek__so you never have to maintain that sidefile yourself
#tantek__like some folks do with auto-generating their RSS/Atom from their parsed mf2
#tantek__that's likely the easiest path for publishers
#aaronpki'm just saying the fewer different ways to parse things the better. less code, fewer test cases, fewer ways things can go wrong.
#tantek__i'm just saying history is now showing that dead-end sidefile formats are what ends up enabling proprietary silos to take-off, so keeping information publishing/consuming in evolving HTML is the longterm strategy for openness