#ZegnatDoes anyone here know why rel-feed didn’t make it? According to http://microformats.org/wiki/existing-rel-values is was proposed somewhere in the HTML5 spec but it doesn’t look like it made it into the final version
#Loqipfefferle: snarfed left you a message 14 hours, 13 minutes ago: thanks! where is the front page webmentions setting? i don't think i changed it from the default.
#Zegnat“Conformance checkers must use the information given on the microformats wiki existing-rel-values page to establish if a value is allowed or not: […] values marked as "discontinued" or not listed in either this specification or on the aforementioned page must be rejected as invalid.” - https://html.spec.whatwg.org/multipage/semantics.html#other-lin
#ZegnatMakes it sound like the HTML spec does not allow unregistered relations
#voxpelliI quite liked the Link Relations spec in that it tried to unify link relations across data formats – such link relations enables extension and composition of different standards in a very powerful way
[kevinmarks] joined the channel
#[kevinmarks]The html spec allows lots of things - it won't remove unlisted release values or anything.
#jonnybarnesright, if my client html form wants multiple targets, and keeping names consistent, the form name is `mp-syndicate-to[]`
#jonnybarnesbut for the generated JSON request POSTed to the endpoint, its just `mp-syndicate-to` right?
#jonnybarnesThis is an example of what my app is generating to POST to an endpoint: string(209) "{"type":["h-entry"],"properties":{"content":["Hello Fred"],"in-reply-to":["https:\/\/fredbloggs.com\/note\/abc"],"mp-syndicate-to":["https:\/\/twitter.com\/jonnybarnes","https:\/\/facebook.com\/jonnybarnes"]}}"
#aaronpkthe [] thing is a convention for sending multiple values of the same property name in urlencoded format. most backends that receive that form post will convert it to an array structure internally automatically
#aaronpkin JSON format, there isn't a need for a workaround like that, you just send an array
#aaronpkthat looks correct. also you should be able to use micropub.rocks to check this stuff
#jonnybarnesyeah, never quite worked out why some json used { and some uses [, specifically why is the json `"properties":{` and not "properties":[`
#aaronpkthat's just a JSON thing. {} is an object with key/values, [] is an array for containing multiple values
#jonnybarnescos to me it looks like properties is an array
#aaronpkreally you shouldn't have to worry about it, create the data structure natively in whatever language, and use a JSON encoder to generate the JSON
#jonnybarnesyeah, but I'm writing a PHPUnit test where I’m trying to test the JSON my client code generates is correct
#aaronpkthere is a difference internally, you just access arrays and hashes both using $foo[$bar] syntax
#[kevinmarks]did they change it internally? it used to be possible to have an array $foo of ["a","b","c"] and then do $foo["bar"]="baz" and it would then be {0:'a', 1:'b', 2:'c', 'bar':'baz'}
#aaronpkthat is a theoretical situation that is only interesting if you care about the language internals. in practice you don't do that, and everything works like expected.
#aaronpkwell that was a weird rabbit hole that ended nowhere. It occurred to me that technically I don't need a silo profile to include a rel=me URL on the profile page if I can check the user's website using their API.
#aaronpksince I already have to have API keys in order to do OAuth, I could make an API request to check the user info as well
#aaronpkthat does mean more code per silo, but that's not necessarily the end of the world
#aaronpkso I tried it with Flickr, since Flickr's API is probably the most stable of the silos
#aaronpkfirst off, I had forgotten about the mega confusion between flickr profile URLs and flickr usernames
#aaronpkmy username is "aaronparecki" but my profile URL is "flickr.com/aaronpk" (someone else has the username "aaronpk")
#aaronpkthankfully there's an API endpoint to find the flickr user ID given a flickr profile URL
#aaronpkhowever, the userInfo endpoint returns the bio but doesn't return the website field that the user enters!!
#voxpelli[manton]: btw, I'm failing to connect to my Micropub endpoint in the Micro.blog app, are there any known issues with that implementation or could I help debug it?
#voxpelliI'm getting: Authorization "code", "state" or "me" parameters were missing
tantek, KevinMarks, gRegorLove and [cleverdevil] joined the channel
#[cleverdevil]I've been having similar issues, @voxpelli. I think manton is aware. Just other higher priority stuff to deal with at the moment. I did provide manton with an account on my Known instance to test with when he gets around to it!