Open qazmlp opened 2 weeks ago
Yes! Funny, this actually already exists, someone else made it. Haven't figured out how to search for labelers in the app, I'll try on web soon.
Alternatively, it'd be nice if self labels were visible to end users somehow. I'll ask the team about that.
Yes! Funny, this actually already exists, someone else made it. Haven't figured out how to search for labelers in the app, I'll try on web soon.
I've seen only the labeller for the bridge accounts, but couldn't find the reverse. Do you have the link on hand?
Ah, right, I don't know if they have it for both directions.
I think there was something related to relative verification/claims ("@x of @y") that went into the direction of auto-surfaced badges, but more as a sketch in GitHub comments than a direct proposal.
I'm not sure "free-floating" ones can be done safely with a service like this, especially if some technical know-how is required to get them (because that would make them seem much more valid).
I ended up building this, on a lark: https://bsky.app/profile/self-labeler.snarfed.org , https://github.com/snarfed/self-labeler . Unfortunately the labels aren't showing up in bsky.app, and I haven't figured out why yet: https://github.com/snarfed/self-labeler/issues/1
(Related to discussion in #827.)
It would be very helpful to be able to see when a Bluesky user has bridged their account to ActivityPub at a glance (rather than checking the social proof). Additionally, users may want to recognise bridged accounts even after custom usernames eventually become possible on Bluesky.
The most straightforward way to do this, in my eyes, would be to create a separate[^1] labeller account for all remote networks combined[^2] that provides label definitions anyone can subscribe to in the Bluesky app.
What I'd ideally like to see
bridged-to-NETWORK
labels that are 'Show' by default and applied to native accounts bridged to other networks.bridged-from-NETWORK
labels that are 'Off' by default and applied to Bridgy-Fed-managed bridge accounts that are not native to Bluesky.(Do these have to be namespaced?)
I'd prefer a short label title with more information in its description.
[^1]: Making an account a labeller largely hides the option to follow it, which would disrupt the opt-in. [^2]: The number of labellers one user can subscribe to at once is pretty limited. I hit the cap a while ago, also after they increased it.