Post

Also, while you're at it, it would be very helpful to have a protocol write up that can be pointed at. That is, here's the lexicon, here's how it works with ozone, here's what verifier org DIDs look like. If y'all were to do this quickly, we could have something to point at when people yell.

0 reposts25 likes

I can think of some cool ways to implement this — default appview labeler forcibly auto-subscribes you to other labelers (verification issuers) that all have the ability to issue the same type of "verified" label that the app displays as a check — but as it stands, seems pretty messy for federation!

I imagine Bluesky will also want to keep a pretty tight leash on the verification issuers... Any feature like this inevitably turns into a status symbol and is therefore incredibly ripe for shenanigans.

I think it's more that the verified symbol draws more attention than a normal account. Don't think they can force priority on other people's custom feed

I can confirm that as a feed creator, I'd never prioritize verified accounts over non-verified in the Game Dev feed. It could absolutely impact the Game News feed, where it would make more sense for verified news orgs to get preference over non-verified sources.

The bsky team runs the Discover feed as the only algorithm they’re in control of. Everything else is user created.