Open dshanske opened 5 years ago
Use case (that triggered this): I would like certain channels to post to specific categories (not tag) on my blog, destination isn't the right solution (as they're not separate sites) - and this would allow my micropub client to decide what to do with all the information.
Another use case: channel name as a tag (micropub category) on the post.
The specific use-case that @RosemaryOrchard highlighted is an interesting one. Mainly because a capable reader (or a Microsub client) could store certain properties that are to be 'expected' of a particular channel. I think this might be the wrong place to discuss this because it should be something that Microsub could store in relation to the channels.
For example, if I had a channel called “Tech” and it's usually a whole feed of people who I follow in tech with some filters in it, I'd probably want to store those 'additional' Micropub properties to said channel (like to use the tags 'tech' and the channel 'tech' so it's not in my main feed). In another channel that's mainly my pop culture or TV updates, I'd probably opt to make the posts unlisted and moved into another channel as well).
(Originally published at: https://jacky.wtf/2022/7/4ebj)
Proposing a set of Micropub properties passed when a Microsub client posts using Micropub. Passing the channel uid and name would be a recommended, but not required practice in the Microsub spec.
Brainstorming here how the Properties would look.