#cweiske"However, folding of header lines is not expected by some applications"
#cweiske"204 No Content: The server has fulfilled the request but there is no new information to send back."
#GWGAgain, still think that the webmention specification doesn't require new information sent back. It requires either to alert that it was accepted, or accepted but queued.
#ZegnatI never bothered to check the HTTP headers on my own receiver. I should do that when I get home. My implantation should be giving 202, but I expect I am doing 200...
#voxpellimyfreeweb: if you have time for a PR, then that usually speeds things up. I guess a concern for aaronpk is also that there might be a need for some backwards compatibility
#aaronpkI will have to think about the backwards compatibility of that. I've been doing those kinds of changes in quill with a backwards compatibility flag and a notice where you can opt in to the change when you're ready
#aaronpkOh dear my SSL cert expired a few minutes ago. For some reason my auto renew failed!
#myfreewebit's just weird that your client is not compliant with your spec
#myfreewebit's unlikely that anyone implemented an endpoint that only responds to GET /micropub with the config, but not GET /micropub?q=config
#GWGThe specification was still partially undefined when several implementations came out.
#GWGIt means that I am not sure what constitutes a reference implementation/client.
#aaronpkoh! i wasn't using letsencrypt for my cert!
#aaronpkthere we go, fixed it and put it into the rotation
#aaronpkyes, quill is meant to be a reference implementation but i am behind on it since i've been making faster progress on the micropub spec lately since it's been in the w3c
#GWGaaronpk, I appreciate you. I do not think I am alone.
#myfreewebyeah i could make it work with a one line fix. but this is still incredibly frustrating. i want to follow the spec, not the client's implementation
#voxpelliI'm happy that aaronpk has such a great client and that he values to stay compatible with us early adopters – everyone can write their own clients if they want or contribute to the ones that exists
#voxpelliit's that atmosphere of mutual contributions that I find so appealing with the IndieWeb
#ben_thatmustbemecweiske: your comment was queued for approval as it wasn't whitelisted and didn't have a vouch
#aaronpkmyfreeweb: normally what i do is i check my logs to see who is using a particular feature and if there are people then i will create a feature flag for the change and let them opt in to the change when ready
#aaronpklooks like it never mentioned anything about a GET request to the endpoint with authentication and no query parameters
#aaronpklooking at Quill, it actually expects all the config info to come back in a single request which is probably why I made my endpoint return both the syndicate-to list as well as the media endpoint on an empty GET request
#voxpellisuch iterative evolving is key to the momentum – waiting for a full spec before implementations kills any momentum
#cweiskeI wonder why the media endpoint is in that config at all, and not at the same place as the micropub server link
#aaronpkcweiske: that was a tricky one, I wasn't totally sure about which way to go with it
#voxpellias it's an instruction to the micropub client
#aaronpkI figured that for the most part, the media endpoint is an implementation detail of the micropub endpoint, so users shouldn't be bothered with it
#ben_thatmustbemebtw, cweiske, yeah, that tool isn't done yet, i was just testing its ability to post
#aaronpk(assuming the user is at least aware of the html tags that go into their home page)
#cweiskevoxpelli stores a list of all his user's token endpoints
#voxpellicweiske: if I were to have thousands of users of my endpoint, then it would probably be because I was running a small indieweb friendly social network or similar and then I would be in control of all those social network profiles as well
#voxpelliI'm sending a nuke to the server location right away – not
#aaronpkIf it's hard coded then you haven't really made it work with arbitrary token endpoints
#cweiskebut all generic micropub endpoints will have this problem
#cweiskethey get a request with a token, but don't know which token server to query
#voxpelliaaronpk: it's an environemtn variable right now but could be loaded from the database just as well
#voxpelliwell, they know which token services that are allowed to provide access, but they don't know which one of those a token is from if there are more than one
#voxpellithat issue comes from the fact that micropub has primarily been designed with a single user in mind – but if one has a multi-user site, then the problem will arise – especially if people of that multi-user site will log in with their personal sites
#cweiskeso when mr. malicious X logs into such a generic micropub server, his token endpoint will be added to the list of potential token endpoints
#cweiskeand thus will in future get all tokens handed to him
#voxpellicweiske: the generic micropub server would give Mr X his own micropub endpoint
#cweiskethat'd be a way to circumvent that issue indeed
#voxpelliand if Mr X doesn't add anyone else to his own micropub endpoint, then no other token endpoints than his will be checked for access
#voxpelliaaronpk: then I'll check your token against the ones configured for that specific endpoint and since the token isn't recognized by any of them it will fail
singpolyma joined the channel
#aaronpkvoxpelli: i'm just confused about what the config file is for. you have to be discovering token endpoints dynamically
#voxpelliaaronpk: no, my endpoint isn't dynamic yet, this version is manually configured – in the future I will probably launch a dynamic hosted version that will discover token endpoints automatically and save to a db
#voxpellipeople still have to self host and manually configure this version
#voxpelli"To specify multiple values for a property, such as multiple categories of an h-entry, use array bracket notation for the property name." – seems to be the generic suggestion?
#cmalyeah so we can finally stop having this plumbering argument and focus on how to implement proper security protocols on top of it (the necessity of TLS changes MUCH in this regard)
#aaronpknow i just gotta go figure out what was using it and update that
#gRegorLoveShould be minor and not change most things, though maybe indieauth with weird capitalization of domain names.
#gRegorLoveLearned to write the tests first. I'd actually written up code to find the t.co meta refresh and use that before I realized cURL was getting the 301 redirect already.
#gRegorLoveAgreed, the 400 just seems like a shortcut for the simple AJAX. Would be better to make the AJAX more robust to handle different responses / warnings.
cweiske joined the channel
#cweiskesome sites show which tool has been used to create the post. is this information transmitted through micropub? which property is used?