Replying to Avatar Garbage nsec

I'm for anything that weeds out this "why not?" type of interop that just dials up the cognitive load for end users. The kind where the end user has to open a post in12 clients and then assemble a serial killer hunting pin-board with strings and polaroid photos to figure out what the original poster's intent might have been.

But I do think there is incentive.

In an embed context (my lexicon represents something non-core in your app) there are incentives both ways, you get your stuff embedded, I get that added info for my users, win win.

In a piggyback context (one app clearly just riffing of another) there's incentive to piggy back, and there's incentive to be piggy-backed off of, so also win win.

In most other contexts, probably no. So very context dependent.
Avatar
Nuh 9mo ago

Being able to embed stuff has nothing to do with interoperability or lexicons it just means open APIs for extensions/widgets.

Unix apps can be piped together with a common stdin/stdout interfaces... but they don't have to publish specs on how do they behave.

Reply to this note

Please Login to reply.

Discussion

Avatar
Garbage nsec 9mo ago

>Being able to embed stuff has nothing to do with interoperability or lexicons

What do you mean, sure it does. Example these comments are embedded bsky.app posts (via the bsky.app lexocon) on the whtwnd.com long-form client (which has it's own longform lexocon). And that's a win win, both sides have said.

That's