#kisik21So... is there something close to a canonical syntax for indieweb/micropub-extensions#4 (aka Query for Post List) filters? I'm definitely gonna need it for my project and I really want to have something that will be useful outside of my code, meaning at least one other implementation (preferably client) supports it.
#kisik21Please !tell me if you have an answer and I'm disconnecting for now because I need some sleep
[xavierroy], [chrisaldrich], gRegorLove_, BenLubar_, strugee, [Rose], [tantek], [aaronpk], [sebsel], cowglow, sonniesedge, Guest74108, grantcodes[m], plindner[m], astrojuanlu[m], jgmac1106[m], zoglesby, voss[m], Rixon, myfreeweb, ketudb[m], jamietanna|wwwjv, [jgmac1106], [frank], [Ignacio] and [jeremycherfas] joined the channel
#ZegnatThat feeling whenever your blog is down! … I might spent hack day tomorrow working on that problem on my end
#jackyI've opted to keep a "local" test copy of my site just for this (largely for big breaking changes)
[grantcodes] joined the channel
#[grantcodes]kisik21: re micropub query filters I think Eddie and I probably have the most experimental features implemented and think they are documented in that GitHub thread
#kisik21@grantcodes: so basically whichever implementation I choose becomes canonical because my implementation will act as a tie breaker?
#jackyI'm aiming to add some over the coming weeks
#jackykisik21: eh, I think it's more of a numbers game
#jackywhichever implementation has the higher # of people implementing it
#kisik21I'm a little bit confused over post types though. I want my implementation to be post-type agnostic because it bitten me in the butt in my previous engine. It severely restricted what I can post because supporting new stuff was requiring me to add new post types and I want to get rid of it
#kisik21because it makes for overly long permalinks
#LoqiIt looks like we don't have a page for "URLs How" yet. Would you like to create it? (Or just say "URLs How is ____", a sentence describing the term)
#vilhalmerI'm finally implementing activitypub, and I'm wondering if anyone has experience with http signatures as used by mastodon's implementation; specifically any guidelines on how to verify that the key given in the signature should actually be trusted
#vilhalmerI'm validating the signatures successfully but that doesn't necessarily imply they came from the right person at all
#kisik21Should all GET requests to Micropub endpoints require a token? Maybe there's something I missed?
#Loqikisik21: [eddie] left you a message 6 minutes ago: also Micro.blog supports *some* Micropub query filters so that’s pretty big
#vilhalmer(the obvious one would be verifying that the key is on the same domain that the message originated from, but this may not always be true afaict)
#kisik21eddie: where are these documented exactly? I mean, which ones are supported?
#aaronpkvilhalmer: you might try asking in #social on the W3C irc server, there's a lot more people there who have implemented it
[calumryan], [tantek] and KartikPrabhu joined the channel
#[Rose]Do media endpoints have different auth keys to micropub? I'm getting {"error":"forbidden","error_description":"User is not permitted to upload files"}
#kisik21Your token probably lacks a "media" scope. Check your Micropub/media endpoint documentation for details on scopes...
#Loqi[manton] Support for q=source (and editing and deleting posts) has been deployed on Micro.blog. It uses the MF2-style JSON as described on the wiki for the response. Thanks y'all!
#[eddie]Essentially it doesn’t filter posts currently, it just responds with a paginated list of posts
#[eddie]Yeah filtering is still HIGHLY experimental and there is no consensus
#[eddie]post-type is pretty commonly accepted among the few that even have Micropub Post List Query, but again any of that can change based on lack of implementations. Feel free to experiment on your site and provide your input on #4!
#LoqiPost Type Discovery specifies an algorithm for consuming code to determine the type of a post by its content properties and their values rather than an explicit “post type” property, thus better matched to modern post creation UIs that allow combining text, media, etc in a variety of ways without burdening users with any notion of what kind of post they are creating https://indieweb.org/PTD
#[eddie]That is how we can refer to post types while remaining flexible posts
#kisik21Why do we even need post types? It's the content that matters. One may wrap a presentation around post types maybe, but is there anything else?
#ZegnatNot really. It is more a conventon than anything else. A way to say “a post with properties X and Y can be called Z”
#[tantek]kisik21, right, no system should actually require explicit post types. They're mostly there for interop with pre-existing systems that are dependent on explicit post types in their data model.
#[tantek]it's the content *and* UI that matters, and that UI can depend on any combination of properties that makes sense
#aaronpkkisik21: I also moved away from a post type based storage to a generic storage where I can style different properties of posts appropriately
#jackyI'm thinking about some interactions with my social reader (more in planning re-implementation)
#jackyif I wanted to response to a post in the reader, I think I'd want to opt for a bit of parsing to insure the intended action occurs. like I don't know if it's safe to assume everyone has implemented salmention or what not
#jackylike if I see Bobby liking a post of Carol, I'm essentially looking at Carol's post