I'd like the ability to tag blog posts to organise them better in my repo.
I'd also like to use these tags to federate blogs into one eg. Tim, Jake, and Will are part of the same organisation Frontpage and they all have their own whtwnd blog records. Their blogs consist of both personal stuff as well as posts authored about their organisation eg. a technical writeup of a feature they created. I want them to be able to distinguish these posts to include in Frontpage blog, but I don't want to show their personal posts there because they're not relevant to the organisation.
Tags allow me to filter records to show only the relevant posts on the organisation blog.
Alternatives considered
One way to implement my specific use case is to add an "authors" field to the post entry. While this would work it comes at the cost of the original author not being able to own their own canonical post. It also doesn't for general organisation or discovery of posts.
I think this would look good as a separate proposal, some kind of additionalAuthors field, I'll probably create another proposal for this.
K-Nksm
commented
1 day ago
This proposal basically amounts to copying the "outline tags" property from the app.bsky.feed.post type
https://github.com/bluesky-social/atproto/blob/87a1f24262e0e644b6cf31cc7a0446d9127ffa94/lexicons/app/bsky/feed/post.json#L51-L56
Why do I want this?
I'd like the ability to tag blog posts to organise them better in my repo.
I'd also like to use these tags to federate blogs into one eg. Tim, Jake, and Will are part of the same organisation Frontpage and they all have their own whtwnd blog records. Their blogs consist of both personal stuff as well as posts authored about their organisation eg. a technical writeup of a feature they created. I want them to be able to distinguish these posts to include in Frontpage blog, but I don't want to show their personal posts there because they're not relevant to the organisation.
Tags allow me to filter records to show only the relevant posts on the organisation blog.
Alternatives considered
One way to implement my specific use case is to add an "authors" field to the post entry. While this would work it comes at the cost of the original author not being able to own their own canonical post. It also doesn't for general organisation or discovery of posts.
I think this would look good as a separate proposal, some kind of
additionalAuthorsfield, I'll probably create another proposal for this.