omekau on Nostr: No, there are no client admins. There are developers like the creator, Will @jb55, as ...

No, there are no client admins. There are developers like the creator, Will @jb55, as well as anyone else that wants to contribute to that GitHub site. For a public key to not be allowed onto Damus, that public key would need to be hardcoded into the applications software which would require a deployment of the new version and update through the App Store. The most they could do is on boot from the update check if the session has a certain npubxyz and then log out. Then when a user tries to enter their nsec, check if it’s a certain npubxyz and then log out. Which would be entirely obvious to the public that a user cannot access Damus. Then to prevent content being presented I would need to get more familiar with how the current “block” function operates but it would also require a code implementation and version deployment to all devices. Which would get caught.

Maybe there’s something I’m missing but in the absolute worst case scenario, just use another client (you can even fork Damus and host it yourself) and use another/your own relay.