[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.
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.
...
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.
schmartytantek: ah, i don't think you have the micropub authorization, token, and micropub endpoint headers set. probably because you don't use micropub. :}
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
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
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.
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.
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.
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
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.
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!
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
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
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
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
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 ?
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
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.
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 :(
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.
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
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]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
[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.)
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 ...