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
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
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
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
[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.
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?
[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!