#dev 2018-02-23

2018-02-23 UTC
#
Loqi
[bkeepers] #316 404 when clicking link to install GitHub App
#
j12t_
KartikPrabhu: I'm playing with mf2py. Are the nosetests supposed to work out of the box? They seem to access foo.com and bar.org
#
[cleverdevil]
Is there a tool out there in indieweb-dev-land that looks at a website and attempts to guess an mf2 structure for it?
#
[cleverdevil]
Sort of like an Instapaper-web-service?
#
KartikPrabhu
j12t: I have no idea about the tests
#
[cleverdevil]
[snarfed] well, XRay assumes that the target site is already marked up with microformats2
#
j12t
KartikPrabhu: Ah :-) I figured something like it
#
KartikPrabhu
j12t: if you want to help write/edit the tests things that would be great. I don't know how that part works at all
#
j12t
KartikPrabhu: I'm new to this code, not sure how helpful I can be any time soon on it
#
KartikPrabhu
sure, no worries
#
KartikPrabhu
eventually it would be good to use some standard testing suite
#
KartikPrabhu
not sure what happened on that front
#
snarfed
start with running the existing tests :P
#
KartikPrabhu
ha sure :P
[kevinmarks] and snarfed joined the channel
#
oodani
am i correct in believing that there's currently no way for an e-* property in microformats2 to control which formats it exposes and what it provides for each format? for instance, my site's using markdown - there's no way to expose the un-rendered markdown source as a format in e-content?
#
KartikPrabhu
oodani: microformats only cares about the final HTML so no
#
KartikPrabhu
what's your use-case for exposing the markdown?
#
oodani
it's a more accurate text representation of the content than is returned by textContent, and also, i'd like micropub clients to be able to pull that markdown when i update posts, rather than only the rendered html
#
KartikPrabhu
the micropub one makes sense, but other than that I am not sure anyone wants to consume the markdown for your posts
#
oodani
that's fair. hmm.
#
KartikPrabhu
aaronpk: ^ is there a way currently to expose markdown for micropub editing ?
#
KartikPrabhu
oodani: also I don't know of any mircopub editor that uses markdown (?)
#
oodani
yeah, i know. one of the nice things about markdown is it still works pretty well without editor support
#
oodani
although for longer entries i usually write in vim + marked.app or stackedit :p
#
KartikPrabhu
right, but then there is no use-case for it to be in microformats
[eddie] joined the channel
#
[eddie]
That would be part of the Micropub source endpoint: https://www.w3.org/TR/micropub/#source-content
#
[eddie]
Your endpoint can return whatever text content it wants in the content attribute. Whatever gets returned from source would be available in the Micropub editor.
#
KartikPrabhu
one use-case I can see is if you use markdown to edit but store your posts as html+mf2
#
oodani
ah. the source content doesn't need to match the entry's "real" content?
#
[eddie]
Nope, it matches the “editing” form of your content
#
KartikPrabhu
oh ok that makes sense
#
[eddie]
For people that edit HTML (like tantek) it would be HTML, for people who edit in markdown (like me) it returns markdown
#
KartikPrabhu
is way behind on micrpub spec
#
oodani
and yeah, there's no micropub clients that support markdown yet, but there's also no way to express explicitly' that an e-content value is markdown yet :o seems like editors will probably start adding that support if markdown e-content starts popping up in the wild
#
oodani
sounds like tweaking my source endpoint will probably do the trick in any case. currently it's literally just parsing the requested page with mf2py, so it's identical to the output format :p
gobengo, snarfed and renem joined the channel
#
@bengo
@scott_gruber @w3c @grabaperch Nice! Are you using https://webmention.io/ to receive the mentions, or coding a perch plugin? The more implementations, the better!
(twtr.io/1awU43GyBZL)
radicaledward101 and snarfed joined the channel
#
aaronpk
Looks like that question was covered
#
aaronpk
The query is meant to return the "editable" version of your content, whatever that means to you. If you return text, clients will treat it as text, butthat can be markdown text if you're willing to edit markdown like you edit plain text, which is what markdown is by design so it should be fine
#
KartikPrabhu
was behind on new micropub stuf
[xavierroy] joined the channel
#
j12t
Speaking of testing ... I just came across this behavior of the mf2py library: https://github.com/kartikprabhu/mf2py/issues/60. It would be very nice to have test cases for things like that, nicely annotated with explanations why this is the correct (or not correct) behavior for the library. Just saying ...
#
Loqi
[jernst] #60 Repeated fields
#
KartikPrabhu
j12t: just replied to your issue. I suspect it is because mf2py does not handle a mixture of mf1 and mf2 cleverly yet
#
KartikPrabhu
but your example does not seem to be too bad for consuming
#
j12t
Ah. Happy to provide HTML, but where to put it? We should be turning this into automated test cases over time.
#
KartikPrabhu
j12t: you can put it in the github issue for now so I can see why it is doing that
#
j12t
(Personal pet peeve: I hate doing things twice). So I put the files here: https://github.com/jernst/mf2py/tree/master/test/future-examples
#
j12t
Ideally, if all that changed was the theme, the uf content should not change IMHO.
#
KartikPrabhu
j12t: wordpress themese do weird stuff
#
j12t
Well, assuming that the two themes show the same post(s) etc.
#
KartikPrabhu
wordpress themes can change classes so they can insert different microformats
#
j12t
Why would they want to? It seems to me the microformats represent the semantics of the displayed content, and those are the same regardless of whether the theme is colorful or boring.
#
KartikPrabhu
I am not sure why they "want" to, but I have seen them do that
tantek joined the channel
#
j12t
On this subject ... some thoughts on automated testing. Blogged here: https://upon2020.com/blog/2018/02/automated-testing-for-the-indie-web/
#
KartikPrabhu
sounds complicated
#
snarfed
testing++
#
Loqi
testing has 4 karma in this channel (23 overall)
#
aaronpk
I keep getting tempted to write a test suite for the Microformats for all the different kinds of posts on my site so I don't inadvertently break something when I make changes to my html
#
aaronpk
Thankfully it sounds way easier to do on my site than this blog post describes for wordpress 😂
KartikPrabhu, gobengo and [kevinmarks] joined the channel
#
[kevinmarks]
We have a test suite already, so we should make sure we are using it
#
Loqi
[microformats] tests: Microformats test suite
cweiske, loicm, schmarty, petermolnar, grantcodes, chimo and jeremycherfas joined the channel
#
sknebel
yeah, although the infrastructure around it isn't great, and it hasn't been updated in a while it seems
#
sknebel
(and I personally am not a fan of the structure by type)
myfreeweb, plindner, eli_oat[m], zoglesby, grantcodes, schmarty and mindB joined the channel
[kevinmarks] joined the channel
#
[kevinmarks]
Fixing the infrastructure is a good idea.
barpthewire joined the channel
#
sknebel
Biggest thing for that probably would be making sure all parsers have either conversion tools, or a standardized way of doing testing over HTTP or a command line interface or ...
#
sknebel
And of course reviewing what kind of tests are missing/incorrect
leg joined the channel