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.
[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
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
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
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)
[Rose]Do media endpoints have different auth keys to micropub? I'm getting {"error":"forbidden","error_description":"User is not permitted to upload files"}
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]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
[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.
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