#dev 2017-02-28

2017-02-28 UTC
mindB, ben_thatmustbeme, singpolyma and [chrisaldrich] joined the channel
#
www.boffosocko.com
edited /annotation (+439) "W3C Recommendations; formatting"
(view diff)
[chrisaldrich], [jeremycherfas], [kevinmarks], tantek, cweiske, gk-1wm-su, plindner, mindB, martymcguire[m] and StoBrendo joined the channel
#
jonnybarnes.uk
edited /HTTPS (-34) "/* Maintenance tax and site fragility */"
(view diff)
#
jonnybarnes.uk
edited /Nginx (+361) "/* Using PHP with nginx */"
(view diff)
plindner and mindB joined the channel
#
petermolnar.net
edited /Nginx (+352) "adding path-info aware PHP location block which makes things like Owncloud and Baikal happy"
(view diff)
singpolyma and marcthiele joined the channel
mindB joined the channel
tantek joined the channel
#
eddiehinkle.com
edited /User:Eddiehinkle.com (+1447) "/* Eddie Hinkle */"
(view diff)
#
eddiehinkle.com
created /Template:eddiehinkle.com (+148) "Add template for eddiehinkle.com"
(view diff)
#
eddiehinkle.com
edited /Jekyll (+66) "Add eddiehinkle.com as Jekyll site example"
(view diff)
#
eddiehinkle.com
edited /projects (+66) "/* Jekyll */"
(view diff)
#
eddiehinkle.com
edited /User:Eddiehinkle.com (+741) "Fix TOC link and add current technology stack"
(view diff)
#
eddiehinkle.com
edited /User:Eddiehinkle.com (+29) "Fix page hierarchy"
(view diff)
[eddie], [chrisaldrich], [kevinmarks] and KevinMarks joined the channel
#
[barryf]
aaronpk: I was just trying Quill's editing with a like on my site and it didn't quite work for me. I assumed the like-of value should be an array whereas Quill's response was a string.
[barryf] joined the channel
#
aaronpk
which direction didn't work?
#
aaronpk
when quill is reading your site or when it sends it?
#
[barryf]
When it sends it.
#
[barryf]
I expected an array but received a string.
#
aaronpk
ah gotcha. let me check something
#
aaronpk
yep quill should be sending an array :)
#
aaronpk
this is why i need to finish the client tests in micropub.rocks :)
#
aaronpk
try now :)
#
[barryf]
Ha, no problem! Happy to help test ?
#
[barryf]
Bingo. That did it.
#
aaronpk
awesome
plindner, martymcguire[m] and mindB joined the channel
#
aaronparecki.com
edited /Ghost (+1212) "/* Issues */ continued discussion about microformats2"
(view diff)
#
loqi.me
created /mediafragment (+27) "prompted by tantek and dfn added by tantek"
(view diff)
#
aaronparecki.com
created /Template:schmarty (+145) "schmarty template to match /schmarty"
(view diff)
#
aaronparecki.com
edited /media_fragment (+482) "more details about media fragment support"
(view diff)
#
aaronpk
[barryf] can I ask you a couple questions about your micropublish client/
[cleverdevil] joined the channel
#
martymcgui.re
edited /Template:schmarty (-4) "fix nested User:User link"
(view diff)
#
tantek.com
edited /media_fragment (+1087) "add why, how to, indieweb examples sections, merge in previous indieweb examples / how to content"
(view diff)
#
aaronparecki.com
edited /media_fragment (+49) "/* Implementations */"
(view diff)
#
tantek
ok now that time based fragments are implemented and supported by multiple sites / implementations, let's go for space
#
tantek
what is an image fragment?
#
Loqi
It looks like we don't have a page for "image fragment" yet. Would you like to create it?
#
aaronpk
what is an image map?
#
Loqi
It looks like we don't have a page for "image map" yet. Would you like to create it?
#
tantek
they're not the same right?
#
aaronpk
they're kind of the inverse of each other?
#
aaronpk
if you receive a webmention from an image fragment URL, you could render it as an image map
#
aaronpk
!tell cweiske any chance you can add micropub query support to shpub? https://github.com/cweiske/shpub/issues/2
#
Loqi
Ok, I'll tell them that when I see them next
#
GWG
Afternoon
[keithjgrant] joined the channel
#
[keithjgrant]
What's the best practice regarding hashes & query params in a URL? Say, as an in-reply-to value... Do they need to be left intact?
#
Loqi
[keithjgrant]: voxpelli left you a message 6 days, 2 hours ago: I don't have an authorization endpoint at voxpelli.com since my identity setup there isn't supported by IndieAuth.com – instead I have a separate discovery page + sometimes manually enter my identity URL (rarely supported)
barpthewire joined the channel
#
aaronpk
query params are part of the URL and may result in a different page on the server, e.g. default wordpress URL scheme is like example.com/index.php?p=100 or something. hashes identify content within the page, so you can include the hash if the thing you're mentioning is a specific part of the page
#
aaronpk
e.g. media fragments
#
[keithjgrant]
Yeah, that makes sense about query params.
#
[keithjgrant]
I'm thinking for my chrome extension. User wants to reply to the "current page"... do I trim off the hash? If there's one of those marketing/tracking query params on the url, will it do odd things to the Webmention if sent?
#
aaronpk
the "current page" does not include the hash according to the URL spec
#
aaronpk
hash is within the page
#
aaronpk
but you could also probably blacklist a few of the common query params like utm_*
#
[keithjgrant]
that's a good approach, I like that
#
aaronparecki.com
edited /Ghost (+478) "add positive example of indieweb support"
(view diff)
[barryf] joined the channel
#
[barryf]
aaronpk: Sorry, went offline for dinner. Happy to answer any questions if you’re around.
#
aaronpk
hey thanks
#
aaronpk
i was curious why you used the "query all posts" option vs "query specific properties" for editing
#
[barryf]
Well I think it seemed easier at the time given the number of properties I would be requesting. I suppose it’s a bit like using SELECT * vs SELECT column1, column2.
#
aaronpk
interesting, okay
#
aaronpk
do you have only the one editing interface?
#
[barryf]
Yes, just the one. I considered following what I had built for new posts and using post type discovery to determine which interface to display, but I thought that may be limiting.
#
aaronpk
interesting!
#
aaronpk
i just did that exact approach with Quill
#
aaronpk
(to avoid building a generic editing interface)
#
[barryf]
I’d certainly consider that approach though. Oh, OK.
#
[barryf]
Hmm, maybe I should reconsider!
#
aaronpk
i like the full edit UI, but I think I would use it as a backup UI of sorts
#
aaronpk
like it's kind of weird to edit a bookmark post and see a field to add a "like-of" property
#
[barryf]
You’re right. It’s not as user-friendly for sure. Maybe, as you say, offer the “kitchen sink” option as a fallback.
#
aaronpk
my "kitchen sink" fallback right now is I have to edit the file on disk by hand. which means I can't really do it from my phone, and I would much rather use an interface like this.
#
aaronpk
but my typical edits don't actually need that level of control, which is why my inline p3k editor doesn't even support editing post content, just a few properties
#
[barryf]
I started out with grand plans to support any nested Microformats 2 structure, but realised I was effectively building a poor JSON editor.
#
aaronpk
ha! interesting point
#
[barryf]
Your client tests have reminded me I need to add photo and media endpoint support so that’s next on my list. I’ll maybe then try your post type approach.
#
aaronpk
so if you built post-type-specific editing into micropublish, do you think the "query for specific properties" method would be useful?
#
[barryf]
Sure. It makes more sense than returning unnecessary extra data.
#
tantek
huh, like e.g. editing an RSVP?
#
aaronpk
an RSVP, a bookmark, a like, whatever
#
aaronpk
all the posts that have their own create interface here https://media.aaronpk.com/Screen-Shot-2017-02-28-12-33-28.png
#
[barryf]
This may be a silly question, but are the properties for post types now generally fixed?
[aaronpk] joined the channel
#
aaronpk
well they're based on the h-entry and other microformats2 vocabularies
#
aaronpk
so they are as stable as those specs
#
aaronpk
and now that http://microformats.org/wiki/h-entry has a specific "change control" section I feel better about the stability of those specific properties
#
Loqi
[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML/H...
cweiske joined the channel
#
tantek
barryf, there is no "fixed" set of post types, or rather, they are a slowly growing set
#
tantek
based on real world examples of posting behavior, identifying patterns of posts that would/could benefit from being treated as a different type, brainstorming, proposals, experiments, etc.
#
tantek
for any particular post type, you have to check the properties it is using to see how stable they are considered
#
tantek
what are post types
#
Loqi
Post Types was a session at IndieWebCamp Brighton 2016 https://indieweb.org/Post_Types
#
tantek
that could probably be made more generic with a see also
#
tantek
I'll fix up wiki refs
#
[barryf]
Thanks tantek. That makes sense.
#
tantek.com
edited /Post_Types (-3) "update redir to something more generic than a session"
(view diff)
#
tantek.com
edited /posts (+138) "/* Kinds of Posts */ Related Sessions"
(view diff)
#
tantek.com
edited /Amazon_S3 (+136) "Criticism Downtime"
(view diff)
#
tantek.com
edited /downtime (+13) "see also outage"
(view diff)
#
tantek.com
edited /outage (+32) "dfn fix, see also"
(view diff)
#
vanderven.se martijn
edited /multilingual_blogging (+93) "/* Indieweb Examples */ prompted by sebsel."
(view diff)
#
tantek.com
edited /Amazon_S3 (+54) "/* Criticism */ Outage"
(view diff)
#
tantek
if anyone has any data / posts / news re: S3 outage, please add links etc. to https://indieweb.org/Amazon_S3#Outages
#
tantek
IIRC this is not the first time this has happened
#
sknebel
does it really make sense to list every instance of a service having (in thas case even regionally limited) outages as "criticism" of said service? To me that's mostly noise, because everything is going to have downtime somewhere sometime.
#
aaronparecki.com
edited /Amazon_S3 (+120) "/* Criticism */ links"
(view diff)
#
aaronpk
yea i kind of agree
#
aaronpk
there isnt really anything actionable that comes from documenting them
#
tantek
sknebel: when there is a common (mis)understanding that services "just work" without any problems ever (i.e. endough to depend on without redundancy) then it's worth documenting instances that dispute that common wisdom
#
tantek
aaronpk there is. changing of perceptions, then possibly more redundancy
#
tantek
as you would have to do with anything that becomes unreliable enough
#
tantek
how unreliable you're willing to put up with is personal and/or use-case specific obv
#
tantek
e.g. I can't post a note to my server vs. I can't show my boarding pass
#
tantek
another purpose of documenting such instances is to show history and possibly trends over time
#
tantek
which you don't / won't know until you've taken the time to document specific instances - before you know such patterns exist
KartikPrabhu joined the channel
#
sknebel
I guess then the basic documentation shouldn't be under "criticism", because I'd like those sections to tell me something interesting about the specific service, not "global truths" (which "stuff breaks occasionally" is for me).
#
aaronpk
that makes sense. criticism would be more appropriate for how a company handled an outage
#
tantek
yes that makes sense
#
tantek
feel free to edit, remove criticism as a heading, just have "Outages" as a == heading
#
aaronparecki.com
edited /Twitter (-3) "/* Criticism */ move Downtime to a section outside of Criticism"
(view diff)
#
aaronparecki.com
edited /Instagram (-2) "/* Criticism */ move Downtime to a section outside of Criticism"
(view diff)
#
aaronparecki.com
edited /GitHub (-2) "/* Criticism */ move Downtime to a section outside of Criticism"
(view diff)
#
aaronparecki.com
edited /Tumblr (-2) "/* Criticisms */ move Downtime to a section outside of Criticism"
(view diff)
#
www.svenknebel.de
edited /Amazon_S3 (-18) "extra /* Outages */ section"
(view diff)
#
aaronparecki.com
edited /Flickr (-2) "move Downtime to a section outside of Criticism"
(view diff)
#
aaronparecki.com
edited /Lanyrd (+16) "move Downtime to a section outside of Criticism"
(view diff)
#
aaronpk
better
#
aaronpk
now downtime is presented in a more factual way
#
tantek
s/factual/objective
KevinMarks joined the channel
#
tantek.com
edited /Falcon (+612) "add explicit Features section for user-level features, and IndieWeb Friendly section with subsections for Standards Support, and other specific best practices"
(view diff)
gRegorLove and KevinMarks_ joined the channel
#
tantek.com
edited /Strava (+157) "Downtime"
(view diff)
#
tantek.com
edited /Amazon_S3 (+74) "/* Outages */ note sites apparently impacted as observed, Strava"
(view diff)
#
loqi.me
edited /tinbox (+277) "tantek added "consider updating various projects indieweb support/compat sections to IndieWeb Friendly section with subsections similar to [[Falcon#IndieWeb_Friendly]], e.g. [[GNU_social#IndieWeb_Compatibility]] (how should we archive past services S"
(view diff)
#
tantek.com
edited /Webmention (+261) "try a short user-relevant summary, spec has advanced to REC, but still worth submitting implementation reports"
(view diff)
KevinMarks joined the channel
#
tantek.com
edited /expand_a_page (+219) "note Features, etc. sections on some pages"
(view diff)
#
tantek
what is an image fragment?
#
Loqi
It looks like we don't have a page for "image fragment" yet. Would you like to create it?
#
tantek.com
edited /area-tag (+146) "move all how to to brainstorming because this is all still being figured out (nothing working yet)"
(view diff)
#
tantek
media fragment << [[area-tag]]
#
loqi.me
edited /media_fragment (+15) "tantek added "[[area-tag]]" to "See Also""
(view diff)
#
Loqi
ok, I added "[[area-tag]]" to the "See Also" section of /media fragment
#
tantek.com
edited /media_fragment (+219) "Brainstorming Spatial for area tags"
(view diff)
tantek and KevinMarks_ joined the channel
#
@vipickering
@vipickering Yahoo! Basic Webmention support is working \o/ \o/ \o/
(twitter.com/_/status/836721810012061697)
#
tantek
Yahoo supports Webmentions? Wow! ;)