Nostr Web Client

to other clients it would look like regular accounts. If other clients don’t support subaccount listing then thats fine, you can still discover the posts using existing techniques

Vitor Pamplona 2y ago

What you are telling me is that you don't see how not supporting subaccounts breaks these clients user experience. That's fine, but I am telling you, it will suck for them. It will become very confusing if this becomes highly used.

I am saying this because the average Amethyst user has 2+ independent accounts logged into in the same phone. So, I know people will use this if you develop it. The difference is that with Amethyst they are different personnas. They generally don't share the same name or picture. So, It doesn't break the user experience. It's a clean separation.

But they are not different, it will be very confusing for those not implementing it.

Reply to this note

Please Login to reply.

Discussion

jb55 2y ago

I never said they had to share the same profile

Vitor Pamplona 2y ago

Correct. But you also didn't say they must be different. If the default is going to be the same, then it will break the UX. Otherwise it can work.

jb55 2y ago

I really don’t know what you’re on about. This doesn’t affect your client at all

:P 2y ago

🍿

Vitor Pamplona 2y ago

Like I said, it depends a lot on how you implement.

You can make it backwards compatible by just implementing in a way that they look like fully different accounts or completely break backward compatibility by making these accounts look similar.

I still think implementing communities is way easier than any of this, but I gave up trying to convince you so. :)

atyh 2y ago

Do both. From a user end, they both support each other.

Though nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ‘s idea grants the individual more control, and lets us build our own community.