#GWGIf a good micropub for Android client works, there will be a flood of those when I move them over from Pinboard
#[manton]Are those "syn-text" and "syn-link" CSS classes a convention that is widely used, or just for your site?
#GWG[manton]: No. They are just for styling. u-syndication is a microformat.
#[manton]Thanks, that's what I thought. So I could hardcode Micro.blog to remove them or style them differently, but I try to avoid that if possible unless it effects tons of sites (like some default from WordPress.com). It seems better to just not include that text in the feed.
#GWG[manton]: I think I will be coding it to not appear in the jsonfeed specifically, and instead add it as a _syndication property
#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.
...
snarfed joined the channel
#GWGtantek: It is core microformats2, but is it core JSONFeed?
#GWGI'm not sure if I have an opinion. I just disabled adding the data as part of the content.
#aaronpkGWG: my point is that the example in jsonfeed of prefixing with _ is for a vendor-specific property
#aaronpkwhereas the "syndication" property is not vendor-specific
#aaronpk*technically* right now jsonfeed says any additional properties have to be considreed extensions and use _, although i suspect what they actually *mean* is that vendor-specific properties should use _
#kaushalmodiBut the downtime info cannot be authorative/fair i.e. we cannot always record *all* the downtimes of all silos and all instances of Mastodon
#schmartyi am pleased to have found a suitable name that fits in my awful Saved by the Bell naming scheme. i have rhearamakrishnan.com to thank for the name suggestion.
#tantekschmarty I have no idea what you're talking about but it sounds fun!
#schmartytantek: ah, i don't think you have the micropub authorization, token, and micropub endpoint headers set. probably because you don't use micropub. :}
#schmartyi want to make a nicer set of error messages, like quills, that explain how to set the needed headers.
#schmartyi should probably also make a "demo mode" so folks can see what it does without logging in. it can stop just before posting.
KartikPrabhu joined the channel
#schmartybedtime for now, though. goodnight, indieweb-dev!
[jgmac1106], AngeloGladding, tantek and [kevinmarks] joined the channel
#tantekI've realized that my brainstorming for minimal reply contexts synthesized purely from knowledge of URL structure (e.g. Github issue etc.) is actually two separate things - the "Replying to a" pre-text which is specific to a reply-context, and the synthesized summary of the url e.g. "issue n on Github project xyz"
#tantekthe latter can be used in a number of different contexts for providing a more human text-friendly summary of a URL if you have no other information (i.e. a URL-only h-cite, and no retrieval of the URL itself for link-preview information)
#[snarfed]github is somewhat unusual in that you can get much from URLs though. other big silos, generally you just get ids, sometimes username, and only very occasionally post type
#tanteksnarfed, fb you can get many post types, event, photo
#tantek.comedited /reply-context (+654) "/* Minimal text reply contexts */ preferring In Reply To, note synthetic summary of a URL as a component" (view diff)
#jmacI have some questions about em that the folks here have encouraged me to ask about / file issues against, and i plan on it with my next shipment of CFT
#jmacBut yeah, flaws and all I found it a great resource
snarfed joined the channel
#pstuifzandI found that my 50% implementation, works with ~80% of websites.
#jmacsalutes whatever stackoverflow page he ripped this list from
#ZegnatAn interesting HTML5 parsing test was added to the PHP parser not too long ago, which also made us pick a userland HTML parser
#Zegnatjeremycherfas: the core difference between authentication and authorization is that authentication says βI am Xβ and authorization says βX gives permission to do Yβ. So with your authentication done, an application can go to a /token endpoint/ and say βX says I should have permission for Yβ, and if everything checks out it gets a /token/ that is proof of that.
#jeremycherfasSo everything we were discussing was about authentication.
#ZegnatBut both are often handled from the same login screen. E.g. selfauth can be used to authenticate as yourself, but for authorization will show little check boxes with what permissions are being asked for.
#ZegnatBecause technically, the first step is always the same: communicate with an authorization endpoint to make sure you are you. And the difference is only whether I am asking to proof you are you (authentication) or also asking for some permissions I want you to give me (authorization).
#jeremycherfasRight. But essentially there are two steps, because if you cannot authenticate that I am who I say I am, there's no point offering me the checkboxes.
#jeremycherfasFrom what you just said, the first step is au8thentication, not authorisation.
#ZegnatWell. It happens to be the same first step. My application can send 2 different requests to your endpoint: 1) ask for authentication, 2) ask for permissions (scopes). Because if I get an answer on 2, I can assume authentication also took place.
#ZegnatSo when Quill asks you to login, it is always going to ask permissions immediately.
#jeremycherfasRight,. And that's your application. I'm trying to understand the logic. Even if your app sends two requests, the first one has to be authenticate.
#ZegnatWhen you enter your URL into Quill, it will ask Known for a "create" permission so it can post over Micropub. If it gets a positive result back, it is happy. It isnβt going to bother with first authenticating you as you
#ZegnatBecause presumably, Known wouldnβt have given a positive result if you werenβt able to login to Known ;)
#jeremycherfasBut that's after having logged in to Quill.
#jeremycherfasWhcih I did by allowing it to show me my Known login.
#jeremycherfasRight. So Quill already knows I am who I say I am. Cool.
#ZegnatQuill, when it doesnβt know anything about you, asks for your domain. It will check if you have all the required Micropub bits and bobs. If you have, it means you have an authorization endpoint. And it is just going to go ahead and immediately ask for posting permissions from there.
#skippyquill knows that your Known instance has accepted you as you, using whatever credentialing Known might use. Known tells Quill "this is X", and Quill accepts that.
#tantekmade a note for future impl, in case I start using URLs like that
snarfed, calumryan, [jgmac1106] and chrisaldrich joined the channel
#tantek[jgmac1106]: instead of a credential post kind, just skip to the conclusion and make it a badge which is a response to someone else, i.e. you reply with a badge to someone else's post to award them that badge for their post.
#tantekthen they can display that badge in their webmentions received, and link to your original badge reply post so anyone can verify their badge by clicking through!
#tantekpresto done - badges with webmention - zero bloated JSON files needed
#aaronpk+1 for badges! i don't even know what a "credential" post means
#aaronpkalso badges have a built-in fallback behavior of being just a photo reply post
#tantekaaronpk, a "credential" post means you're granting me some level of access to some thing ;)
#tantekaaronpk, true, a badge could be a special kind of photo reply
#tantekand your own "my badges" page could just be an aggregation of all the badge reply webmentions you have received!
#Zegnataaronpk, can you confirm, is the API for indielogin.com just IndieAuth?
#aaronpkyes, with the caveat that when you use the indielogin.com api you don't need to check the domain of the user after they finish since it handles that for you
#aaronpkalso there is the option of having indielogin.com provide the web sign-in form
#aaronpkif you just don't include a "me" in the first request
#ZegnatI didnβt see any mention of IndieAuth in the dev docs when I was reading them. And although my spidy sense was tingling, I mostly just wanted confirmation that it indeed was IndieAuth
#aaronpkit is, but I don't want to confuse that again
#aaronpkswentel: indielogin.com is a reimplementation of that part of what indieauth.com does
#Zegnatwonders privately if the wiki is going to use indielogin.com or is going to self-host an instance on something like login.indieweb.org
#aaronpkgRegorLove: if you want a demo try signing in to https://pin13.net/login/ although since you use indieauth.com as your authorization endpoint probably nothing will look different
#aaronpkZegnat: i was gonna use indielogin.com, I don't see much reason to use a private instance. i could be convinced otherwise tho.
#gRegorLoveAh, is that why it went to indieauth.com? I was wondering if it would stay on indielogin.com
#aaronpkgRegorLove: yeah if you have an authorization endpoint set then it will use that, and you probably won't even see indielogin.com at all in the flow
#ZegnatgRegorLove, temporarily remove the authorization_endpoint from your HTML to see indielogin instead :)
#swentelso is indieauth.com going to go away then?
#aaronpkoh yeah case sensitive, i need to fix that
#swentelSooo indielogin is purely for logging into a site, what happens then with that user is up to the site, no further interaction anymore. (my)indieauth.com is for authentication for say micropub so that a site can validate access tokens coming from clients like quill and indigenous ? Is that a good summary ?
#aaronpknope indielogin.com has nothing to do with micropub or authorization
#aaronpkoh sorry yes, i missed the myindieauth.com part
#aaronpkyes myindieauth.com will be an authorization endpoint as a service
#swenteland also, way easier to explain actually :)
#aaronpkideally your blog software includes an authorization endpoint built in, to avoid relying on external services, but it's convenient to have one in some cases especially when starting out
calumryan joined the channel
#swentelmm it's really neat, I can now more easily make the distinction, especially in the documention, in the Drupal plugin
#ZegnatNo, but it never will be if nobody starts using it. I used it last IWS, I documented on the wiki, and I used it again now. It just didnβt get accepted.
#tantekso that's not really enough to justify spec'ing it
#ZegnatThat is not going to keep me from continueing to post it though
#tantekI post it in my visible text but I stick with supported rsvp values for my p-rsvp
#tantekI figure that's good enough for now to gather examples
#ZegnatXRay not picking up on my authorship is a bigger problem however. Even if I make 2018.indieweb.org accept the remote RSVP, it will break stuff :(
#Zegnatjust wrote a patch that would make remote yes accepted
#ZegnatI guess my only reason for liking a space over dash is that it felt like additional information to the yes. And HTML already has these nice space separated token lists all over the place.
#ZegnatWill add that snippet of thought to the wiki tomorrow, I am off to bed right now :) Have a good one all!
#tanteksyntax driven design is not really a good principle, or rather should be a last consideration of clean-up, not a reason to base a proposal
#tantekI think it's worse for old impls to treat "remote yes" as yes
#tantekpoint is it's not just "additional information" to the yes - it's a very different kind of yes
#tanteknow if we had yes+1 that would be additional information
#tantekI got in-stream reply-contexts working locally!!!!
#tantekalright, going to diff code changes and deploy
#tantekso much scope creep in this effort. I went from "in-stream reply contexts for reacji" to in-stream reply contexts for all replies including RSVPs including synthesized URL summaries for all
#tantekdiffs verified, Falcon & CASSIS updates deployed live
#tanteksnarfed, reload tantek.com, scroll down and see if you see anything different :)
#tantek(especially down to the series of π posts)
#tantekalright, I've got my demo ready for tonight :D
#tantekaaronpk - hopefully my h-feed looks better in Monocle now too
#aaronpksweet, i will find out when there is a new post
#tantekwill it re-read the in-reply-to of past h-entry s also?
#LoqiA badge (AKA achievement) is a visual indicator of completing some sort of accomplishment, usually associated with completing specific tasks within a system that is frequently recognized as "achievement unlocked", or "you unlocked the xyz badge!" https://indieweb.org/badge
#LoqiIt looks like we don't have a page for "badge post" yet. Would you like to create it? (Or just say "badge post is ____", a sentence describing the term)
[tantek] joined the channel
#[tantek]Gah we donβt call them note posts either
#[tantek]Gwg do you post photo replies now? You could photo reply to someone with your own badge graphic as a proto-badge post if you have such content to try posting
#GWGaaronpk, you sent a screenshot, would you be willing to build a form that renders a specific post or feed using your system? It would be very useful as a debug tool
globbot, eli_oat, tantek and [manton] joined the channel
#[manton][aaronpk] You might find this interesting... I'm working on Instagram .zip import and want to make sure that it doesn't create duplicates if someone already has used OwnYourGram. Incredibly, the date/time in the Instagram media.json file appears to be in local time. No time zone. (I was going to use the post time to match things up on Micro.blog-hosted sites.)
#GWG[manton]: If you need help, tell me. I just submitted two last night and I have more ideas.
#Loqi[Aaron Parecki] Just downloaded my @instagram dump and I'm pretty disappointed. π
β’ My comments include only the comment text, a timestamp, and the photo author. No way to know what I'm commenting on
β’ Same for photos I've liked
β’ There's no indication of ...