[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.
#tantek.comedited /media_fragment (+1087) "add why, how to, indieweb examples sections, merge in previous indieweb examples / how to content" (view diff)
#[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
#aaronpkquery 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
#[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?
#aaronpkthe "current page" does not include the hash according to the URL spec
#aaronpki 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.
#aaronpkdo 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.
#aaronpki like the full edit UI, but I think I would use it as a backup UI of sorts
#aaronpklike 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.
#aaronpkmy "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.
#aaronpkbut 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.
#[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.
#aaronpkso 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.
#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
#tantekbarryf, there is no "fixed" set of post types, or rather, they are a slowly growing set
#tantekbased 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.
#tantekfor any particular post type, you have to check the properties it is using to see how stable they are considered
#tantekIIRC this is not the first time this has happened
#sknebeldoes 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.
#aaronpkthere isnt really anything actionable that comes from documenting them
#tanteksknebel: 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
#tantekaaronpk there is. changing of perceptions, then possibly more redundancy
#tantekas you would have to do with anything that becomes unreliable enough
#tantekhow unreliable you're willing to put up with is personal and/or use-case specific obv
#tanteke.g. I can't post a note to my server vs. I can't show my boarding pass
#tantekanother purpose of documenting such instances is to show history and possibly trends over time
#tantekwhich 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
#sknebelI 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).
#aaronpkthat makes sense. criticism would be more appropriate for how a company handled an outage
#tantek.comedited /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)
#tantek.comedited /Webmention (+261) "try a short user-relevant summary, spec has advanced to REC, but still worth submitting implementation reports" (view diff)