#oodanii'm working on improving my micropub.rocks report - is it actually possible to get a pass for both 14 and 15? ("Returning HTTP 201 Created and a Location header when creating a post" and "Returning HTTP 202 Created and a Location header when creating a post")
#oodaniit seems like your endpoint would either implement one or the other, depending on if you want to process creations asynchronously or not ?
#ludovicchabant[cleverdevil]: I don't think Bitbucket have 100% pivoted to Git? Last I checked they had a couple of core Mercurial people on staff
#ludovicchabantIf they did it would suck, since Mercurial is my scm of choice so far
[chrisaldrich] joined the channel
#aaronpkoodani: that sounds right. The test numbers are more about testing the completeness of the spec vs needing each implementation to pass all of them
#KartikPrabhuaaronpk: maybe there should be a note about this? as in "your implementation should pass either 14 or 15"
#aaronpkthe test suites were important to advance the spec in the W3C process, and I feel like they need to be tweaked a bit now that the goal is to help people actually test their implementations
#oodanii think it'd make sense to combine them into one test, yeah "returning http 201 created or http 202 accepted and a location header when creating a post" or whatever
#oodanihm, i've built my site so it stores the properties of each entry - name, content, categories, etc. - as static database fields/relations, but as i implement more of micropub i'm getting the impression it really wants me to store properties verbatim, as microformats2 json (for example, this is a mess https://git.00dani.me/00dani/lemoncurry/src/branch/master/micropub/views/query.py#L23 )
#oodaniwould folks recommend using something like the postgres bjson field format to store properties?
#dougbealAnyone have a favorite email gateway? Would be cool if I could generate indiebookclub.biz reading entries for amazon kindle orders.
#oodanii'm thinking of creating a generic "item" table that just contains fields for mf2 type (postgres array of strings) and mf2 properties (postgres bjson) - does that sound reasonable? :o
#[cleverdevil]!tell snarfed is there a way I could make my new Known GitHub plugin automatically tell Bridgy about newly published issues/comments to make them automatically publish?
#oodanioh, also: i know i shouldn't store the access token in the mf2 properties, but i think it would be useful to store *something* that identifies the client used to create the item, like their client id for example! it'd be handy to keep track of how my tokens are being used, as well as perhaps to show a mastodon-style source app for each post? does anyone already use a property for that, and if so what's it called? :o
#Loqi[snarfed]: [cleverdevil] left you a message 6 minutes ago: is there a way I could make my new Known GitHub plugin automatically tell Bridgy about newly published issues/comments to make them automatically publish?
#aaronpkI don't even have a post type column, which i wanted today! So I'm probly going to add that by doing post type discovery on my own storage files
#oodanidang, i like that. i'm leaning pretty heavily on my db right now and it'd be nice to cut down on that
#oodanias for the client, i'm leaning towards something like <a class="u-client" href="{{ client_id }}">{{ client name from h-x-app if there is one, or client id if there isn't }}</a> - it sounds like there's no commonly-used name for that property yet so i'm gonna pick one :p
#Loqigiving credit is a collection of cultural practices related to acknowledging and attributing text, hyperlinks, quotes, utterances to others, typically by name, as a way of recognizing their contribution(s) https://indieweb.org/credit
#tantek.comedited /Mastodon (+489) "put features first, screenshots from h-feed support from aaronpk (will leave it to him to upload and update img URLs accordingly)" (view diff)
#www.kickscondor.comcreated /Indieweb.xyz (+1454) "Created page with "{{stub}} '''<dfn>[https://indieweb.xyz Indieweb.xyz]</dfn>''' is a directory of Indieweb links, organized into ''subs'', similar to Reddit, but designed for self-promotion. A..."" (view diff)
#tantek__GWG++ your edits to /Vouch in general look very good - didn't find any problems with any of your edits, and expanding the explanation with actual names (rather than A, B, C) is definitely a big readability help!
#Loqigwg has 36 karma in this channel (376 overall)
#@martijnvdven↩️ Dit is niet alleen een webmention probleem, maar een generiek probleem: hoe weet ik welke paragraaf op een pagina deel is van de reactie reactie, en welke paragraaf niet? Microformats bieden deze extra metadata, maar dan moeten ze wel kloppen in de HTML. (twitter.com/_/status/1014054694820380672)
#@ton_zylstra↩️ mmm, dan lijkt dat het gevolg van het installeren van SemanticLinks naast de Webmention plugin in mijn WP. Zal eens in mijn settings neuzen, en kijken wat ik op theme niveau kan. (twitter.com/_/status/1014094205453553664)
#[eddie]!tell aaronpk: If I want to make note of potential issues with the IndieAuth spec for discussion, where is the right place to do that? Wiki? GitHub somewhere?
#Loqi[SendAsPost] SendAsPOST: Share extension for iOS and macOS to send photos and links as POST requests
#gRegorLoveI think /Vouch#Vouch_Selection needs some tweaks. It seems to describe a fairly specific way, involving follow lists, but that is only *a* way. I'll think about it some more; might write a post.
#gRegorLoveStep 4 seems incorrect. It only establishes that I follow/approve that domain, not that it's one the receiver has ever linked to.
#LoqiContent-Security-Policy (abbreviated CSP) is an HTTP directive that a site can use to restrict what external resources are retrieved by a browser, to mitigate some XSS and injection attacks https://indieweb.org/csp
#dgoldthe person doing the vienna rss reader says that using the openreader API format has allowed them to acces:B azQux.com, FeedHQ.org, InoReader.com and TheOldReader.com
#[cleverdevil]Ooh... a microsub bridge for that would be nice 🙂
[wiobyrne] joined the channel
#snarfedbased on the casual usage survey i did when i was writing https://snarfed.org/microsub-bridge , the readers in that list are all small (by # of users) except inoreader
#aaronpk[kevinmarks]: thx, but I really don't. I prefer to follow people individually
#Loqiaaronpk: [eddie] left you a message 4 hours, 25 minutes ago: If I want to make note of potential issues with the IndieAuth spec for discussion, where is the right place to do that? Wiki? GitHub somewhere?
#schmartysknebel: yep, webring signups failing despite being able to log in to the wiki.
#schmartyaaronpk: I was hoping to have the webring be an example of minimum-working-system folks could crib from. Using indielogin feels a bit like cheating since it’s not generally available. I am torn!
#aaronpkyeah, sadly relmeauth is a bit of a trick to implement directly
#aaronpkyou have to sign up for API keys for each service you want to support too, so it's not just plug and play as a code example
#schmartyI am leaning towards telling people who want to use relmeauth to set up indieauth.com. 😂
#aaronpkaahhh I wish I was done with myindieauth.com already
#schmartyI think using indielogin.com is the right move for inclusion, since relmeauth is touted as the “look it’s easy” login solution for indieweb
#schmartyMy read on it is that it follows the same steps as a regular indieauth flow except I skip discovery and forward them right to indielogin? So that should be pretty easy.
#aaronpkif you only have one rel=me link then it jumps you straight to that
#aaronpkif you have multiple, it makes you choose just like indieauth.com
#aaronpkif you have an authorization endpoint then it jumps to that and you never do relmeauth
#schmartythanks! Despite being proud of my IndieAuth implementation hack job, indielogin.com really solves a lot of problems.
#aaronpkindieauth is easy! relmeauth is a bit more complicated
[manton] joined the channel
#[manton]Related: I finished updating Micro.blog to handle IndieAuth for external sites today. So you can point any site to Micro.blog's auth and token endpoints and it will work if your site is verified in Micro.blog.
#aaronpki'm gonna have to try that out. sounds like an easy way to get an auth endpoint for my random test domains
#[manton]Let me know if you see any problems. I just tested from WordPress to 🕸. (Of course, Micropub has to point somewhere else if you're not hosting on Micro.blog, but not all apps need to post.)
#[manton]By setting link tags in WordPress to use Micro.blog's endpoints, I mean.
#GWGtantek__: I was wondering what you remember of the original development session for Vouch.
#GWGtantek__: Because the biggest missing piece right now is implementation of sending. There is a lack of suggestions on how you as a sender of Vouches actually find them.
#tantek__GWG, at the time, I believe a few folks (including ben_thatmustbeme) came up with ways to discover vouches among their own resources nearly or completely automatically
#Loqifollow is a common feature (and often UI button) in silo UIs (like Twitter) that adds updates from that profile (typically a person) to the stream shown in an integrated reader, and sometimes creates a follow post either in the follower's stream ("… followed …" or "… is following …") thus visible to their followers, and/or in the notifications of the user being followed ("… followed you") https://indieweb.org/following
#tantek__I have two tabs next to each other now: github.com/indieweb and indieweb.org/GitHub
#GWGtantek__: It would lower the cost of me finding Vouch URLs if I could have a list of people the other person already trusts
#tantek__you wait for them to webmention you when they do, then you can track those webmentions as special if you like by post type
#tantek__e.g. if you kept just a list of received webmentions from other people's follow posts, then you could recreate something very similar to your Twitter followers page (which lists your followers by most recent first) https://twitter.com/dshanske/followers
#LoqiA follower is someone who has chosen to receive updates of a profile, typically by explicitly clicking a follow button, the inverse relation is a following. followers are the list of people who have chosen to receive updates of a profile, often shown on a page by the same name, sometimes paginated. Similarly, followings is the list of profiles that someone has chosen to receive updates of https://indieweb.org/followers
#tantek.comedited /follower (+783) "/* Brainstorming */ subheads for display followers / followings, add how to for both based on follower posts and webmentions, similar to how Twitter displays them" (view diff)
#tantek__hmm since I can't edit the title of that post I won't attempt to brainstorm how to do an /edit post suggesting an edit of the name of an issue
#GWGtantek__: Basically, I already mapped out posting follow posts in my mind. This is a note to also set up consuming them
#tantek__looks like to properly implement edit posts I need to understand Micropub updates
#LoqiIt looks like we don't have a page for "u-follow-of" yet. Would you like to create it? (Or just say "u-follow-of is ____", a sentence describing the term)
#GWGIt notes that chrisaldrich and ben_thatmustbeme used follow-of, and rhiaro(has anyone seen her around lately, come to think of it) used it with the -x- for experimental property