If you read the thread at
maybe you'll realize that your goals and aspirations are much better served by the AT Protocol than by Nostr.quoting nevent1q…0lyrYes, although I think they're abandoning that nomenclature because it makes no sense. The AppView layer doesn't need standardization or interoperability, it can do anything it wants, so it doesn't make sense for it to be described in the protocol.
I've seen they calling it just "app". But, while in Nostr an "app" is a client-side software that runs on your computer, there it is a "platform", an old-style "web2.0" service, like Twitter, that has a backend part and a frontend part.
Bluesky took to their heart jack (npub1sg6…f63m)'s idea that eventually Twitter would be an app on their protocol, so they designed it in such a way that 90% of the actual Twitter codebase could be reused and the Twitter frontend could be basically unchanged.
I'm curious about why you prefer Nostr over ATProto, if you ever thought about that.