#dev 2018-03-18

2018-03-18 UTC
#
aaronpk
hm I think I didn't document it yet cause I wasn't sure this is the best way to handle it yet
snarfed joined the channel
#
eli_oat
legit, legit
eli_oat, tantek, [kevinmarks], snarfed, leg and renem joined the channel
#
oodani
yo i'm implementing webmention receiving right now, based on the spec - is there any particular format that status pages should be in? i know i return the url of the status page as the location header, and i've done that, but idk what it should actually /contain/
#
oodani
the spec doesn't seem to describe what a status page looks like, just how you make it discoverable
#
aaronpk
For now the status pages that exist are human readable I believe
#
eli_oat
Hey oodani, I'm not certain if their is a best practice (I just use webmention.io to receive webmentions) but I'd probably model my status page after what webmention.io offers: https://webmention.io/eli.li/webmention
#
oodani
ah, hmm. i was leaning towards json, i can make it human-readable text instead if that's preferred :p
#
aaronpk
If you make it JSON you should at least pretty-print it :-)
#
aaronpk
The webmention form on my site will show the status url when you use it to send a webmention which is why mine is human readable
#
oodani
that's fair
#
oodani
how 'bout using the accept header to choose between human-friendly html and machine-friendly json? :o
#
aaronpk
tho tbh unless you have a consuming use case for the JSON I would just skip that for now
#
oodani
fair enough!
#
oodani
hmm, i just made a nullable boolean for "valid", but there's actually at least four states, since it could be 'pending', 'valid', 'invalid', or 'deleted', huh?
snarfed, [eddie], voxpelli, DenSchub, sebsel and [gerwitz] joined the channel
#
sebsel
moving servers is way more work than I thought :(
#
sebsel
Indieweb is hard.
#
Loqi
it'll be okay
#
sebsel
thanks Loqi
#
Loqi
you're welcome, sebsel
barpthewire, gryphon13, [kevinmarks], pstuifzand, snarfed, karckz and [eddie] joined the channel
#
Zegnat
Ugh, homebrew doing a new repackage of PHP has broken my dev setup.
#
Zegnat
One day I will switch to linux so all of this makes sense again
[snarfed] joined the channel
#
[snarfed]
then you'll have two problems πŸ˜₯
#
Zegnat
[snarfed], two problems?
barpthewire and [eddie] joined the channel
#
aaronpk
Thinking about improving the error messages in Quill now that Micropub.rocks exists and micro.blog is telling people they can use Quill to post to their site
#
GWG
aaronpk, as a contributor to a Micropub server, I would love what you propose
#
aaronpk
Micropub.rocks didn't exist when I made Quill, and Quill was basically serving that purpose when I started it
#
aaronpk
So the errors are intentionally written to mean something to the developer of a Micropub server and not meant to be user facing
#
aaronpk
I'd want to change the errors in Quill to say something that makes sense to a user and also provides enough info or a link that they can send to the developer of the server they're using. Probably tying into Micropub.rocks in some way, like saying "this thing went wrong here, try debugging at Micropub.rocks/x"
#
[eddie]
Yeah, I think one of the things I want to accomplish with Indigenous when it goes to the App Store, is that is provides friendly user-facing errors and if someone downloads it without Micropub support, that it can generally and simply explain Micropub and direct them to some potential Micropub servers (Micro.blog, Wordpress, Known, etc)
#
[eddie]
And then, like you said, to provide errors info that can be passed along to the Micropub server developer
#
eli_oat[m]
πŸ™ŒπŸ™ŒπŸ™Œ
leg joined the channel
#
Loqi
eddie has 28 karma in this channel (49 overall)
eli_oat, [pfefferle] and [cleverdevil] joined the channel
#
[cleverdevil]
I'm currently working on checking punypub against micropub.rocks πŸ™‚
#
[cleverdevil]
I'm also considering merging punyview into punypub... I can't decide.
#
[cleverdevil]
(Also: [aaronpk] I've tried signing into micropub.rocks and haven't received an email yet... its been a few minutes... might be something up with email delivery?)
#
[cleverdevil]
And right when I send that message, it comes in.
#
[cleverdevil]
nvm πŸ™‚
#
[cleverdevil]
Welp, it looks like punyauth/punypub/punymedia mostly pass the Micropub.rocks tests for what I claim to have implemented so far.
#
[cleverdevil]
No (update|delete|undelete) implemented yet.
#
[cleverdevil]
But, media endpoint upload and discovery works, as do all of the JSON and formencoded publishing requirements.
eli_oat and [eddie] joined the channel
#
[eddie]
Wow awesome job, cleverdevil!
cweiske joined the channel
#
[cleverdevil]
Right now, punyview’s rendering of content is... sad. But, hey it’s a start.
eli_oat and [kevinmarks] joined the channel
#
GWG
I am thinking of moving my secondary server to my house
#
GWG
Is that too much owning my own data?
eli_oat joined the channel
#
aaronpk
As long as you're up for the additional admin task of having your own hardware
#
cweiske
do you still own your money if it at your bank?
#
cweiske
s/it/it is/
#
GWG
I've never even been to my bank
#
GWG
But I already have the server and am administrating three more.
#
GWG
Just thinking of consolidating
#
GWG
This would move my IRC bouncer, my feed reader and my development site into the house
#
GWG
All things that have an audience of one.
KartikPrabhu and [cleverdevil] joined the channel
#
[cleverdevil]
So, [aaronpk], I am fairly confident that the 802 test for Micropub.rocks is broken.
#
[cleverdevil]
In other news, punypub/punyauth/punymedia now pass every other test in Micropub.rocks πŸ™‚
#
sknebel
which one is 802?
#
sknebel
ah, the access_token one
#
[cleverdevil]
```802: Does not store access token property
#
[cleverdevil]
This test will ensure your endpoint does not store the access token in the post. It does this by creating a post while providing the access token in the post body, then querying the endpoint for the source properties of the post to ensure the access token is not returned as part of the content. In order to pass this test, you will also have to support the Source Query test.```
#
sknebel
I thought it was broken once too, but in my case it was a bug on my end
#
[cleverdevil]
Pretty sure that the body of the response doesn't include the access token πŸ™‚
#
sknebel
but it should be "content":"Testing accepting access token", without the "value":?
#
sknebel
or am I forgetting a case that allows this? (not looked at MP recently)
#
[cleverdevil]
Not really sure. Based upon the description, I think that I return should constitute a valid response.
#
sknebel
the test doesn't check for absence of the access_token, it checks if the response matches one it expects
#
sknebel
I don't think that's a valid response, its either html in an object or flat
#
sknebel
"If the source of the post was written as HTML content, then the endpoint must return the content property as an object containing an html property. Otherwise, the endpoint must return a string value for the content property, and the client will treat the value as plain text. "
#
[cleverdevil]
Yup, that did the trick,.
#
[cleverdevil]
Thanks @sknebel πŸ™‚
#
[cleverdevil]
sknebel++ for help figuring out my bug
#
Loqi
sknebel has 32 karma in this channel (91 overall)
#
Loqi
[sknebel] #66 802 (Does not store access token property) fails correct response
#
aaronpk
glad you got that sorted
#
sknebel
it happening twice suggests the wording/feedback could be improved
#
sknebel
and/or another test before it, that catches our specific mistake
#
aaronpk
"content":[{"value":"foo"}] wouldn't have made much sense as a response anyway
#
aaronpk
did the source query test not cover that case?
#
[cleverdevil]
Now I pass 100%!
#
sknebel
congrats
#
aaronpk
congrats!
#
aaronpk
how did you pass 603?
#
aaronpk
that should have checked for the same content value
#
[cleverdevil]
(I need to shorten my slugs...)
#
Loqi
aaronpk: lol
#
[cleverdevil]
Gotta go run and pick up the kid, I'll be tinkering more later this evening πŸ™‚
[kevinmarks] joined the channel
#
[kevinmarks]
There's always xoxo to turn the json into HTML
#
[cleverdevil]
What is xoxo?
#
Loqi
XOXO is an annual conference in Portland, Oregon https://indieweb.org/XOXO
#
[cleverdevil]
πŸ€·β€β™‚οΈ
#
aaronpk
hm yeah even http://microformats.org/wiki/xoxo doesn't tell me how that is relevant
#
Loqi
XOXO 1.0: Extensible Open XHTML Outlines
#
[kevinmarks]
Its generic json to HTML and back code
#
aaronpk
doesn't see any mention of JSON on that page :shrug:
#
[kevinmarks]
Well, it predated json
#
Loqi
[microformats] xoxo: Code to transform back and forth between JSON and HTML outlines
KartikPrabhu joined the channel
#
Loqi
[microformats] xoxo: Code to transform back and forth between JSON and HTML outlines
#
Loqi
ok, I added "https://github.com/microformats/xoxo" to the "See Also" section of /XOXO