Post

Luca LaValva
@lavalva.dev

Are there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience

Boris
@bmann.ca

The customer has the data in their account and can seamlessly move between apps. So they compete on product and feature set and preferred UI. Semble, Margin, and other bookmarking apps all have some shared lexicon usage. A bunch of event apps use the @lexicon.community event lexicon.

0 reposts1 like

Luca LaValva
@lavalva.dev

lexicon.community is super cool. Am I wrong in thinking we should deprecate most app-driven lexicons (even `app.bsky`) in favor of separately governed efforts like this? bsky.app/profile/lava...

Luca LaValva@lavalva.dev

Yeah, I think my worry is that if you're using another app's lexicon you will always and forever feel like the "other" app. Twitter-style apps on this network are sort of locked into being labeled as bluesky alternatives, while long form content apps are all on the same standard.site playing field

Boris
@bmann.ca

No, lexicons are the jungle! We do want product teams to make their own decisions and compete. Lexicons don’t have moats and can be re-used and remixed. On the other hand, we formed @lexicon.community to start the path of seeing what community collab looks like, exploring early governance

Luca LaValva
@lavalva.dev

I'm definitely not advocating for a single source of truth! Just trying to reason about whether it makes sense for apps to own their lexicons My gut says there can be more innovation in the tweet space if bluesky forfeits full control, and same for any other app that created its own standard