Timeline, feed, and reporting workflow do not alert user to already-applied labels

[rahaeli]

Note: I have redacted the screenshots in this report to remove the username and the actual content being labeled; I have the unredacted versions available if that would be helpful to the developer who picks this issue up. Just ask and I'll send them.

Describe the bug

When a post or an account has been labeled by multiple labelers (including but not limited to the official Bluesky moderation service), the display of the post on the timeline/feed view only shows one of the labels. The additional services' labels are only visible if the end user clicks through to the individual post view.

Example feed view display of a post that has been labeled as "racial intolerance" from Aegis.blue and "Intolerance" by the Bluesky mod service:

It isn't until you click on the post itself that you see both labels:

Someone (it's me, I'm someone) who's reading their timeline or a feed will encounter the post as being labeled by the third party labeler, and if they think it warrants reporting to the Bluesky mod service (or even to another third-party labeler they subscribe to), can enter the reporting workflow straight from that feed view and report the post even though it's already been actioned by the labeler they're reporting to. This will result in duplicate reporting of content that's already been actioned and add to the number of unactionable reports the labeler service receives.

To reduce unactionable reports, the reporting workflow should alert the end user that the service they're reporting the post to has already labeled the post and display the labels that service has already applied.

To Reproduce

Steps to reproduce the behavior:

1. Find a post that has been labeled by multiple labeler services you are subscribed to displayed on a feed view.
2. Enter the reporting workflow and choose to direct the report to a moderation service that has already applied one of the labels on the post.
3. No indication will display on any subsequent screen of the reporting workflow that the moderation service has already labeled the post.

Expected behavior

The final screen of the reporting workflow, where a reporter can select additional services to report to and provide more information, should include a list of all labels already applied to the post by any moderation service the end user subscribes to, as well as somehow distinguishing services that have already taken action on the content in the checklist to add additional services to direct the report to.

Because there can be reasons for a post that's already been labeled by a service to be reported to the service again (if, for instance, the end user believes other labels issued by the service should apply to the post, or if the end user believes the official Bluesky moderation service should remove the post or account entirely rather than labeling the content), the reporting workflow should not prevent already-labeled content from being reported to the service again. However, having a list of the labels already applied to the content will reduce reports where the end user is satisfied with the labels already applied.

The most appropriate screen for displaying the extant labels on the post or account is the final screen of the reporting workflow, ie this one:

The existing behavior can also result in deliberate duplicate reports to the Bluesky moderation service even when that's the only service the end user is subscribed to, but the interaction of multiple labelers and the feed view only showing one of them has made me make several inadvertent duplicate reports that I wouldn't have made if I'd noticed the Bluesky moderation service had already issued a label on the post, so it is driving at least some unnecessary duplication of effort.

Details

Verified the behavior exists on:

Web: Build version: 1.85.0; Bundle info: 42477d8 (prod); Bundle date: 24060517; Platform: web

Mobile client: iOS version 1.85