nostr:nevent1qqsqqqrn565nly755zu2lfk8tm0dcm20dh6h2c6939nvm3x96je2skspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq3qgzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gsg2sllk

I think both have their charm. More importantly, I think there should be something that connects both worlds smoothly

what's the benefit to not signing publications?

You will be able to rotate delegated keys soon (it is how Pubky Noise works), but pure root-key rotation is a fake idea. It always requires a separate authoritative source/network. You can do social recovery things with shamir, or pre-announce other identities that you may rotate to, but all of it...

Yeah I mean the UX issue of, hey guard this key with your life kind of thing. I mean I didn't "join" nostr until I wrote and maintained my own signer (and still do). With multiple layers of indirection to my key. One my few podcasts back in '23 I talked about the issue of a life long key people ar...

It is easy to say you don't need key rotation... I did for long time.. I want people that make that claim try to provision keys to even experienced developers and see how often they lose it when they don't really care about it enough initially.

true key rotation is complex and requires things that nostr doesn't have, like a hard arrow of time. but the goal of key rotation is to replace a compromised key, and delegation can provide this

Try #Pubky

Yes, this is also interesting: https://openmeet.net/cross-app-authentication-atproto

probably for roomy is explain in a blog https://github.com/muni-town/roomy

> Where does a user comment on another user's post live exactly? Your data only ever lives in your own PDS. Even your “likes” are just “files” in your PDS. I don’t fully know about the last two questions but indexers are indeed a big thing.