I always thought the Pubky people were right about that. Just trust the server, don’t trust every single post. But maybe there is a middle ground where people can sign every individual post if it’s something important. Like selective verification

Also, the app developer should be the one that owns the lexicon functionality. AtProto has that right. They are the ones that want to use the lexicon. So let them support it for their users. Meanwhile, the expectation of NIP functionality is forced onto relays. Insane because Nostr relays were supposed to be dumb.

It’s very different from NIPs. For one, lexicons have no pretense that there is or will be interoperability. They assume that there isn’t, in fact. But lexicons do assume that at least one developer is using them (it’s under their namespace). NIPs are the opposite. They assume interoperability, but in reality zero apps are using them. There is only hell if we impose it upon ourselves. Basically, it’s all about expectations and ownership. Nostr does both terribly.

AtProto Lexicons kinda solve it. Ironically in a more decentralized way. https://atproto.com/guides/lexicon

The Second Coming of Jack is prophesied to happen soon. Developers, always ask yourself, “is this where I want to be when Jack comes back?”

Just chill and wait for the next empire to announce they’re your boss now lol. Low key relaxing

Yeah, AtProto is a great architecture for it

Letterboxd does it how I describe it (they use TMDB) and it works for millions of users

Thinking about user reviews of things. The world has basically settled on a few databases / API’s for everything. Books, openlibrary. Movies, TMDB. Etc. There’s common IDs for most of these objects. Even businesses are incorporated with ID’s, right? We only need clients to easily let users’ browse and find the objects they want to speak about. Then you have your social graph recommendation / curation engine.

You just kick the can down the road. Now you’re determining which servers issuing badges are reliable and which aren’t. But it’s not a bad idea for certain use cases.

another one to test maybe

Is the site that had the example name still up somewhere? I think it’s helpful to see what the names look like and what they can potentially do