2016-10-20 UTC
# 00:03 bear fortunately I can change my nginx default setting
ChrisAldrich and AngeloGladding joined the channel
# 00:20 dansup y'all doing amazing work
# 00:21 bear hmm, I don't see why my response for a source query is failing
# 00:21 bear the test doesn't specify what item it isn't finding
KevinMarks, bear_ and thebaer_ joined the channel
# 00:35 bear huh, both of the source tests are failing the "Returned the requested properties with the appropriate values." part
# 00:38 bear oh poo, "if no properties are specified, then the response must include all..."
# 00:43 bear welp, returning type, published, content and category isn't working either
# 00:47 bear for "all" I set it to: type, content, published, category
# 00:48 bear so even tho it's associated with the rules for properties, it isn't *a* property
# 00:54 bear for test 602 i'm returning {"type": ["h-entry"], "properties": {"category": ["micropub", "test"], "content": ["Test of querying the endpoint for the source content\n"], "published": ["2016-10-20 00:52:28"]}}
gRegorLove joined the channel
# 00:59 bear the example result in the spec shows: "content": ["Hello World"],
# 00:59 aaronpk It's checking that the response is an exact match of what it sent
# 00:59 bear so I took my list of lines and returned it
KevinMarks joined the channel
# 01:09 bear my suggestion would be to use the PHP variant of the Python startswith() routine
# 01:10 bear because now i'm special casing my content string to match the test
# 01:11 bear technically I should be able to return [ "Test of querying the endpoint\n", "for the source content"]
# 01:20 bear had to file an issue for this one aaronpk - seems smelly that a testing tool is making me change how text is managed for my site
# 01:22 bear is oddly happy that aaronpk has called one of my thoughts reasonable
# 01:24 tantek double-edged and deserving of further analysis. space handling in text can either be over specified/restricted (thus undesirably limiting user authoring intentions etc.) or under specified (thus resulting into interop failure).
# 01:25 tantek it's one of the hardest balances / edge cases to get right in UX / format / protocol design
# 01:26 tantek and yeah, bear's expression of concern is valid
# 01:26 tantek means there's something worth looking into to see if the changes he's being "forced" into are fixing bugs, or limiting his code's features
# 01:27 bear I was thinking that a small addition to the spec would say "the content array MUST be split by newline"
# 01:28 bear for now I am going to do that but still keep the issue open
# 01:28 bear "Test of querying the endpoint for the source content",
# 01:30 KartikPrabhu weird! does it affect actual posting with micropub or just the tests?
# 01:32 bear the create sends (python tuple version) -- ('content', u'Testing accepting access token in post body')
# 01:32 bear but because I use markdown it gets a newline added
# 01:33 bear booyaa - with that I pass every test except for the 4XX ones
KevinMarks_ joined the channel
tantek joined the channel
KevinMarks joined the channel
# 02:41 aaronpk bear: you just made me realize I should add a test to check that the endpoint is returning the source content specifically, like not returning autolinked HTML
# 02:41 bear I was also wondering why you didn't use the source query for the 4XX tests - to verify the changes
# 02:51 dansup anyone know if there is a php lib for micropub?
# 02:53 aaronpk bear: I didn't want to prevent you from passing the 4xx tests if you don't support the source query
KevinMarks_ joined the channel
# 02:54 bear after implementing all of these the last couple of days, I feel that query and update|add|delete are pretty core and should be considered minimal implementation
# 02:55 bear if anything the source query really points out the oddities that indieweb is with mf2 json stuff
# 03:21 bear I should probably add "opinionated" to that :)
# 03:23 bear kaku is a webmention endpoint implementation - ronkyuu is the library to validate and work with them
# 03:23 bear kaku uses ronkyuu to process the GET request
# 03:24 bear I will be stripping out the micropub helper code from kaku into another library
# 03:25 bear kaku converts things to a json blob with details - so I should be able to have a micropub lib that takes that mf2 json
# 03:25 bear i'll find out soon - just now got kaku to pass all of the micropub.rocks tests
# 03:25 KartikPrabhu you'll have to find a new name for the micropub lib though, kaku suited best ;)
# 03:26 bear I make move kaku's code over to another project and morph kaku back to a lib
# 03:27 bear I have a name for the micropub lib set aside: hakkan 発刊 - to publish
# 03:27 dansup thanks KartikPrabhu :)
# 03:28 bear project names for me are really fluid sometimes :)
# 03:28 KartikPrabhu yeah same here until I use them enough to make them fixed and not confuse myself :)
# 03:29 bear but yea, I want micropub to be able to be passed a raw requests lib object and convert it to python items
# 03:30 bear to smooth out some of what I consider php/mf2/indieweb oddities
# 03:30 KartikPrabhu great will keep track of kaku/micropub progress and use it on my own site. I seemed to have lost touch with micropub changes/improvements to write the code myself
# 03:31 bear the kaku source shouldn't be too bad in a short bit to read/use
# 03:32 bear it's a small amount of code to handle the incoming request, break it down into some dicts and then act on it
# 03:41 dansup im making a gnu/social clone that will use a lot of indieweb/ostatus stuff
# 03:41 dansup getting tired of patching gnu/social, been running a popular instance for a few years
AngeloGladding joined the channel
AngeloGladding, gRegorLove, KevinMarks, chrisaldrich1 and cweiske joined the channel
KevinMarks_ joined the channel
KevinMarks and loicm joined the channel
# 17:09 Loqi ben_thatmustbeme has 175 karma (3 in this channel)
# 17:09 ben_thatmustbeme would anyone like a preview. I think i have all the functionality really. Just UI stuff like notifying when a post is actually created
# 17:31 ben_thatmustbeme oh, yeah, you had logged in before when you tested, so it has it stored in localstorage
chrisaldrich1 joined the channel
tantek joined the channel
# 19:12 aaronpk you're not doing anything wrong there, but you should display the error better :)
# 19:12 aaronpk i was returning "https://pk.dev" at some point in the flow
# 19:12 aaronpk which is what i use when i test things on my laptop off of the internet
# 19:39 aaronpk well when i refresh i get the "state" error but it's still at the bottom
gRegorLove joined the channel
tantek joined the channel
tantek joined the channel
# 20:33 ben_thatmustbeme yay, and it successfully lets you know when your post is submitted, and gives you a link
tantek joined the channel
# 20:43 aaronpk and errors are not shown so I couldn't tell why it wasn't posting
# 21:01 aaronpk it looks like it shoved my whole HTTP response into the link
# 21:01 aaronpk it should look for the location header and get the URL from there instead
tantek joined the channel
# 21:35 KevinMarks Hm, I wrote a post with title and content, and it only posted the content - do I need to change type?
# 21:35 Loqi [Kevin Marks] And post when I return to connectivity
# 21:41 dansup works on a php implementation of micropub
# 21:55 KevinMarks If I change the mp-type options, the saved post only shows me the previous ones
# 21:58 KevinMarks mp-type is the post type being used in micropub. In Known it chooses a post template.
# 21:58 bear mp-type I thought was old school micropub (at least I have that check in my code)
# 21:59 KevinMarks I just switched inkstone from note to entry to get a title in known
# 22:00 aaronpk but...the whole point of microformats and micropub is to avoid explicit typing
# 22:00 KevinMarks (after reading that code, and seeing that mp-type defaulted to note there)
# 22:00 tantek so what's still using mp-type, why, and should it be explicitly deprecated somewhere?
# 22:01 bear sure, it is now - but I have a memory of the first time I was writing an endpoint for posting having to deal with mp-* fields
# 22:01 KevinMarks I'm with you, but known started with post types. Ben has talked about changing that, and that code looks like it will auto detect
# 22:02 KevinMarks So if inkstone didn't send an mp-type, maybe it would pick "entry"
# 22:02 Loqi ok, I added "https://github.com/idno/Known/blob/master/IdnoPlugins/IndiePub/Pages/MicroPub/Endpoint.php" to the "See Also" section of /mp-type
# 22:03 tantek this sounds like all sorts of potential confusion
# 22:03 aaronpk quill doesnt send mp-type and it works with Known, right?
# 22:03 aaronpk i don't know how mp-type got in there, and i can't find any trace of it on the /Micropub edit history
# 22:03 bear the places I saw it (that caused me to add support) was that Postly and some other tool supported it - back in late 2014
# 22:04 tantek aaronpk - this is precisely the "implementers adding extensions randomly" problem
# 22:04 bear well, this was pre spec ... so it's not random
# 22:05 bear it just falls into an edge case variant that the spec should acknowledge
# 22:06 tantek waits for apparently different data/assertions to resolve themselves
# 22:07 bear in my brain (take that with a grain of salt) I don't remember micropub having the momentum it does now until the beginning of 2015 - sure it may have been around -- just observations as an implementor
# 22:07 tantek goes back to previous question - where did mp-type come from? who conceived it / first typed it? implemented it? etc.
# 22:09 bear aaronpk - could this be a conflation from folks who have had to consume old style mf while also working on new micropub stuff?
# 22:09 bear I think that's what I want to say - but seeing how bad I am with recent history i'm just going to be quiet
# 22:10 aaronpk honestly i think it just came from the laziness of programmers wanting explicit types to make the code easier
# 22:11 bear then let's shine a bright light on it and clearly mark it as deprecated
# 22:11 bear will happily remove all of those if checks from his code
# 22:12 bear yes, I patterned mine off of some earlier python parsing code I found
# 22:12 bear so those items have just been carried across
# 22:12 tantek old style mf has nothing to do with mp-type, never did
# 22:12 aaronpk i've never used mp-type on any clients or servers
# 22:13 tantek aaronpk - hence my point about it being an emergent mp-* extensions from implementers
# 22:13 tantek where are mp-* extensions (ideas, proposals, etc.) documented?
# 22:14 aaronpk the example cited is of course the classic "post with location vs checkin with comment"
# 22:22 tantek or rather, never made it out of brainstorming
# 22:22 bear I added "don't crash if you see this" support but I don't act on it
thebaer joined the channel
# 23:24 dansup hi, what is the best way to start contributing to the indieweb project? Register on the wiki?
# 23:25 aaronpk do you already have a personal website? that's the place to start
# 23:26 dansup i have dansup.com, but i haven't done anything with it. I will register on the wiki and get my site up
# 23:41 dansup thanks for the advice aaronpk! Once I get my site up, I will work on my php implementation of the micropub spec
# 23:43 aaronpk cool! then you'll be able to use micropub clients to post stuff to your site!