What I found on Damus was that if other clients are causing an issue, or if Damus handles something in a way other clients dont support it is useful to document these friction points, and that a single client repo may not be the best place.
It is logical that devs and teams are focused on their app. So I figured it’s worth a try to document in one place things that are more complex than single app behavior.
It could be that integration lessons and patterns emerge, and all of nostr benefits from this knowledge.
I’m happy to get the documentation started, and continue maintaining it.
Who knows, maybe a FOSS enthusiast dev who enjoys fixing different apps working together appears out of the lurkwoodwork.
Worse case scenario nothing useful comes out, and devs continue doing their thing.
What do you think nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
