Let's add a facet to indicate where the mentions are in the update posts from ListSky. eg. in this post, the account should be a mention:
➕ Added Cthonyxa, @cthonyxa.bsky.social to list: List Trek
Posts can have facets, indicating rich parts of the text.
There are a couple of types of facet, including mention.
Documentation here suggests that it should be reasonably straightforward to indicate which parts of a post should be facets.
Proposed modification
ATConnection.PostAsync should be able to identify facets alongside the post. Update the method to allow the composition of messages with easily identifiable facets.
FacetIndex indicates the start and end bytes of the facet.
Clever points
The documented example also illustrates identification of the facets with regexes. This is clever, and we should do it. Modify the method to use regexes to identify the facets by adapting the python regexes into .NET regexes.
Bonus points
Let's also compose the mention of the list as a link - so that people can follow it back to the list itself.
This is another supported type of facet, as indicated in the documentation.
Feature request
Let's add a facet to indicate where the mentions are in the update posts from ListSky. eg. in this post, the account should be a mention:
Proposed modification
ATConnection.PostAsync
should be able to identify facets alongside the post. Update the method to allow the composition of messages with easily identifiable facets.FishyFlip supports this:
ATProtoRepo.CreatePostAsync
supports the provision of aFacet[]
alongside the text.FacetIndex
indicates the start and end bytes of the facet.Clever points
The documented example also illustrates identification of the facets with regexes. This is clever, and we should do it. Modify the method to use regexes to identify the facets by adapting the python regexes into .NET regexes.
Bonus points
Let's also compose the mention of the list as a link - so that people can follow it back to the list itself.
This is another supported type of facet, as indicated in the documentation.