#aaronpkbefore amazon registered the .bot TLD, I set it up so that if you're on my home wifi and go to bar.bot you get my cocktail robot drink menu :D :D ... DNS is fun!
#[tantek]presumably without https though right (barbot)
#aaronpki don't have a cert for that but i sure could!
#[tb]This just made me realize that I don't even use the Yubikey OTP for everything because everything I have it hooked up to uses FIDO2
#[Jean_Philippe_]I would like to implement a micropub server (for my own needs and fun), and I have a question: how can we make a difference between a Note and an Article ? I am using Hugo as a generator for my site and Notes and Articles are different files
#[Jean_Philippe_]the protocol descries these post types as h-entry
#[Jean_Philippe_]the protocol describes these post types as h-entry
#[Jean_Philippe_]ok thank you, I’ll dive into that direction
fauno, KartikPrabhu, gxt, jonnybarnes, [pfefferle] and [tb] joined the channel
#[tb]Phew, spent some time getting all my OpenGraph and Twitter Card meta in order yesterday. Pretty happy with the results as it led me to add automatic derivative creation to my photo model so I could spit out optimized images for og:image, twitter:image, etc.
#hirusi[m]so I'm a little confused about mp-syndicate-to. when I'm sending a publishing request to the micropub server from a micropub client, it can be a string (single target), or an array (multiple targets), is it?
#hirusi[m]for url form encoded requests, currently I send just mp-syndicate-to for a single target and multiple mp-syndicate-to[] key values for multiple targets, but should it always just be mp-syndicate-to[]
#hirusi[m]Reading this makes me think my current behaviour is correct -- no [] for a single target, but add [] for multiple targets
#[tb]So from my understanding from the spec, clients can pass either single-value properties or "arrays" (via `property-name[]`) when making multipart or form encoded requests
#[tb]And then again, the server can interpret multiple values how it sees fit
#[tb]I think what I'm going to do going forward is have my Mf2 JSON -> internal Post model conversion be canonical for my backend and just put an additional transform in to convert form-encoded to Mf2 JSON first for those requests
#hirusi[m]This is a mp- prefix so I thought asking the Indieweb community might be more apt
[pfefferle], [KevinMarks] and [grantcodes] joined the channel
#[grantcodes]Depends what language you're using but a lot of frameworks have ways to handle form data, so converting form encoded requests to match mf2 json isn't too difficult. Generally take the `h` value and make sure everything else is an array and dump it into `properties`
#[tb]Speaking of Micropub... for the `mp-slug` extension, is this something you would also pass in a request to create a post (is the property name in that case just `slug` or is it `mp-slug`?), in addition to the query endpoint extension to check the slug's availability?
#[grantcodes]all the `mp-*` are sent as properties with the `mp-` prefix included
#[tb]Do the `visibility` and `post-status` extensions just not have `mp-` in front of them because they're more stable then?
#[grantcodes]Nah it's a kind of confusing rule around what is prefixed and what isn't. `mp-` is meant to indicate it is some sort of command, rather than an explicit part of the post
#aaronpkthink about it like "are you going to store this value with the post?" if yes, then no mp- prefix, if no, then mp- prefix
#aaronpk"visibility" is a property of the post, it needs to be stored along with the post so your server can know what the visibility is
#aaronpk"mp-syndicate-to" is a command, and you don't end up storing that value, you store some other value that is the result of that command
#aaronpk"mp-slug" is in a bit of a grey area because you may store that value verbatim, but it's really more of a suggestion from the client to the server and the server might ignore it or change the value depending on its own rules
#Loqiaaronpk has 69 karma in this channel over the last year (245 in all channels)