snarfed, [kevinmarks] and petermolnar joined the channel
#@nilshaukThis evening I’ve been trying to build a minimal http://glitch.com app which supports IndieAuth login. After some head scratching I see it’s a tweaked oauth2 flow, I think.
Goals:
- remixable (Glitch shines there)
- transparent
- well tested (twitter.com/_/status/1016121386077687810)
#[jgarber]Looking at the Verification section of the Webmention spec, I came across this: “In a JSON ([RFC7159]) document, the receiver should look for properties whose values are an exact match for the URL.”
#[jgarber]Are there any examples in the wild of anyone verifying a JSON file like this?
#KartikPrabhu is anyone sending webmentions from a JSON document?
#[jgarber]KartikPrabhu: That’s what I’m trying to figure out. The spec mentions it, but… I haven’t ever seen anyone doing it or talking about doing it.
#sknebelits a bit odd that something apparently nobody ever did made it into the spec. there was some talk to use it for some of the JSON-LD based W3C specs, but I believe they all recommend LDN now
#GWGThere were some interesting talks about doing it
#[jgarber]GWG: Any links or references or anything would be super helpful.
#[jgarber]I was surprised to see that in the spec. But… if someone’s out there doing it, I can write support for it into this verification library I’m working on.
#GWGI remember a discussion about doing it as a way of sharing bibliographic data.
#LoqiIt looks like we don't have a page for "web annotations" yet. Would you like to create it? (Or just say "web annotations is ____", a sentence describing the term)
#LoqiAnnotations are comments (including marginalia), highlights or any other interactions that add to (part of) a post, typically added by individuals other than the author https://indieweb.org/annotation
#aaronpkOh yeah there was that implementation... it is hopefully documented on the wiki...
#aaronpkI don’t know what came of it since then, but I was impressed
#[jgarber]_lawd_ okay. This is super useful documentation.
#[jgarber]Based on the way the spec is written, it seems to imply that only values in a JSON object that _exactly_ match the target URL should be considered valid.
#[jgarber]That would discard the target URL being referenced in, say, a `"content"` key’s value.
#[jgarber]At face value that seems like a curious choice, but… it makes the parsing a little less heinous.
#[jgarber]aaronpk: Is there a reason the spec went with the precise match?
#aaronpkI think because JSON lacks both a hyperlink mechanism as well as a mechanism to say what content type values are so a partial match might lead to false positives
#[jgarber]…and I imagine a conforming verification library would need to crawl all the way down the JSON structure until one runs out of key/value pairs?
#[cleverdevil]Yeah, [aaronpk] I’m gonna have to figure out how to do the token exchange without passing it as a GET parameter. I’m doing it that way now because it was an expedient way to have the Lamba app redirect to the static website which then generates the links using JavaScript.
#[cleverdevil]I think I can do the redirect and potentially pass the values in HTTP headers and then extract them client side but I’m not sure.
#Loqicleverdevil has 36 karma in this channel (106 overall)
[cleverdevil] joined the channel
#[cleverdevil]Now, a gen 3 type customer could sign up for Micro.blog, then sign into Aperture, Indiepaper, and Together/Monocle and have a great experience.
#[cleverdevil]Not sure how to automate that without having to special case it in Micro.blog.
tonzyl, eli_oat, snarfed and [manton] joined the channel
#[manton]When I have a chance to think through more of the Microsub stuff, it probably makes sense to have a field on Micro.blog that adds a <link> tag for Microsub for the user, similar to how it works for Twitter, etc.
#Loqi[aaronpk] @manton OAuth has become the de facto standard for authorization and authentication on the web. Nearly every company with an API used by third party developers has implemented OAuth to enable people to build apps on top of it.
While OAuth is a great ...
#aaronpksomehow my site sent a webmention from that page to micro.blog, and then micro.blog matched it up as a reply to manton's post from last week?
#[manton]Yes, it's a perfect storm of 2-3 Micro.blog bugs.
#[manton]Don't think you are doing anything wrong.
#aaronpkoh... I linked to that post in the article!
#aaronpkok, not a salmention problem (that would have been on my end)
#aaronpklooks like micro.blog isn't limiting matching to the in-reply-to URL
#[manton]Yeah, it "worked" but it really shouldn't allow long replies like that and it should get the HTML instead of just the text version.
#aaronpkwell my post isn't a reply to yours either tho
#aaronpkI wouldn't expect generic mentions of a micro.blog post to appear in the conversation view
#[manton]Okay, I'll check the markup and see if I can better detect non-reply webmentions.
#[eddie]That’s true. But also it’s an article, so it should have shown the title and the url
#snarfedhey GWG. one thing that makes reviewing this PR hard is that there's no diff, since the code moved across files. ideally there are no functionality changes in this kind of PR, just moves...but i noticed that eg admin_menu is entirely new. are there other new things i need to find? can you tell me where?
Lovi, snarfed, snarfed1 and [manton] joined the channel
#[manton][aaronpk] I just realized why that webmention was showing up on Micro.blog all of a sudden. My old blog didn't support receiving webmentions! When I moved manton.org to M.b, the webmentions started arriving.
#[manton]Anyway, I'm fixing the in-reply-to check.
#skippywhat are folk's workflows for reposting something and syndicating that repost to twitter? Do you repost non-Twitter sources and syndicate those reposts to Twitter?
#[eddie]Gotcha. I thought retention_days = 0 might be it but I was worried about testing that without verifying for fear that it would delete everything. haha
#tantek__skippy, AMA about that section, did a lot of thinking/design with it, and subsequent follow-up on /repost as well
#tantek__several times got close to implementing /repost posts on my site, but fell short of the required time to finish it while keeping the whole design "in my head"
#skippyno real questions. Only need to decide if I want to undertake the effort to fetch source contents from URLs for truncated inclusion in syndicated tweet...
#skippyi don't currently repost non-Twitter content; but I suppose I could.
#tantek__right, it's an incremental thing you could do based on need
#LoqiLiking and disliking things is a false binary. There’s really 4 potential states.
Like
Passive Dislike (e.g. “Not for me”)
Active Dislike
No Opinion
We should strive to have as few things in our “Active Dislike” column as possib...
#skippyi think it'll just send the url in the repost-of param, right?
#tantek__it's up to your server to do the right thing with that for sure
#[eddie]aaronpk: Is there anything I’m forgetting I should do while updating Aperture? composer install and php artisan migrate
#[eddie]IndiePaper logged me in via IndieAuth, but the articles don’t seem to be getting passed through now
#aaronpkthat should do it. and if you're running the worker in production mode make sure you restart it
#[eddie]Ohhh I’m seeing an error from predis. Is that a somewhat new use? It’s been a couple of months since I updated Aperture, I don’t think it was being used before?
#aaronpkdepends on what you're using for your queue/cache
#[eddie]That would be awesome. I've been doing individual certs for all of my subdomains
#sknebelok, then I'll expand my notes to a blog post :)
#stevestrezayou can get one cert that covers multiple subdomains that isn't a wildcard cert, I'm not exactly sure how it works but the letsencrypt docker image I use does it
#LoqiIf either of you has any connections in desperate need of a co-sponsor in the City who can make a space donation. Three rooms, projectors, solid wifi.
#tantek__[jgmac1106]: interesting, that post has no link to bridgy but has other problems, e.g. the "Also on" Twitter link is a local-to-twitter-com link which makes it 404 on your site. in general your syndication links should use absolute URLs, unless you're planning on adding local redirects / caches for your syndication links!
#tantek__[jgmac1106]: this code: <a class="u-syndication link-twitter icon-twitter" rel="syndication" href="/status/1016396209785798656" target="_blank">Twitter</a>
#[jgmac1106]Yeah and the h entry was missing and this pulled in my gravatar
#[jgmac1106]But now leaning on recommending to folks who don't want to change theme to: A use a subdomain and a new WP instance for their status updates or B: use a page builder on a static homepage when using an IndieWeb theme
#tantek__[jgmac1106]: there's almost enough useful things in WP themes by default for old style hAtom (with class="hentry") that we should be able to figure out a way to make it work backcompat
#[jgarber]Hacking the fragment identifier (e.g. `#t=10,20`). Clever.
#[jgarber]I’d… argue they’re semantically consistent activities (commenting on a run of text and commenting on a length of audio), but I won’t since the community’s already made the decision that they’re different things. 😄
#[jgarber]Related to sending webmentions to media elements, the spec outlines a few and the list of elements that would allow linking documents, files, etc. is…
#[jgarber]`<a>`, `<audio>` (including `<source>` children), `<img>`, `<object>` (via the `data` attribute), `<picture>`’s `<source>` children, and `<video>` (including `<source>` children).
#LoqiIt looks like we don't have a page for "read-of" yet. Would you like to create it? (Or just say "read-of is ____", a sentence describing the term)