Browser extensions really need to start allowing multiple accounts. It has been 2 years already... Let's go... No one is using just one account in Nostr.

Replies (47)

I use different VMs for different personas. Super annoying to have to consider upgrading my hardware just to handle more personas.
Choo Choo's avatar
Choo Choo 1 year ago
I’m not the most technically savvy person. Having multiple NOSTR accounts seems like a lot of work. What are the advantages which makes it worth it?
πŸ™Œ Lo hacen y tengo mΓ‘s de un perfil. Por lo menos, un par mΓ‘s: economΓ­a/negocios y literatura πŸ˜‰
banjo's avatar
banjo 1 year ago
Sure...why not? I'm more interested in the person. The person is the content, not the other way around. We all have interests, and those outside interests are what make relationships deeper. Having two accounts seems counterproductive...
dankswoops's avatar
dankswoops 1 year ago
NostrKeyring already solves this issue but needs someone to contribute to implement sign event. If you implement it, ill pay you a lot of sats. The repo is on to website. https://www.NostrKeyring.com
dankswoops's avatar
dankswoops 1 year ago
ESBuild compiles nostr-tools into nostr-tools.js. Background.js imports this file but you could cut the middle man and put tools inside background.js and compile it together. I'm unable to find proper documentation on how the logic of signEvent works. I'm pretty sure I'm implementing this function wrong and that's all I need help with. I'm happy to put $100 of btc on it. To get the test environment setup, npm i, npm run build, put the extension into firefox using manifest json at about:debugging#/runtime/this-firefox Then create a user profile, log into that user to pass the keys to background.js and now you should be able to edit bg.js, test a nip-07 signEvent login. to retest: change the code, refresh the extension, log out then in of the user, and try to signEvent. That's all you need to know dev on it.
One feed* just doesn't make any sense Look at reddit- the most common alternate accounts are either throwaways or novelty accounts. Nostr has plenty of both. These don't serve the purpose of splitting interests as much as specifying a "role" or "personality," or maintaining privacy. Look at @PABLOF7z - He has two accounts. One is personal about climbing and the other represents the "developer/influencer Pablo". Is this beneficial for him as a user? Probably Is it ideal? I would argue not for me, and likely not for others. Can't speak for Pablo but I think Nostr can offer more flexibility that would defeat this inherently bastardized, single-feed structure. Nostr says "discovery is a manual feature" and to that I say "feeds are the garbage can for discovery". I leverage my feed to discover often, so it is not inherently a problem of feeds themselves. The problem is single-feed silos. So we can manually segregate feeds with a tool like Listr which integrates with Amethyst. But this process is pretty much the same as it was 3 years ago. Unless another client is offering better list curation. I haven't seen anything change in this regard. There is a bounty out for CRUD lists in amethyst and I really hope someone can pick up that lead. Not here to complain, just my two cents. The resolution would be native list management in my eyes. Splitting the user between tools does not feel intuitive with an app like amethyst. Just about everything else is miles ahead. Our feeds should be able to designate their own relays in my opinion. Let us filter by relay first, then by users, then by content.
You can run multiple profiles with firefox. That has been a thing for I think 20 years or more. You may have to launch it with a command-line parameter, but you used to be able to have it ask which profile you want as it starts up.
huch?! in alby you have multiple since day one. what are you missing? there is a bit of a storage limit by the browser above 5ish but that should be mostly not a problem, is it?
Do I need to create a separate wallet/new Alby account to have a separate nostr account? I am very confused about this. Anyway, the switch should be easier. The extension icon should always show the active npub. It is quite hard to know which account I am giving permissions to.
Yes, I think they're tied to separate Lightning accounts, but anything else would make it even more confusing I guess. @bumi By the way, there's a small UI bug: when you switch accounts, it doesn't immediately update the npub that you can copy from the nostr icon...
I think the main confusion is because the extension always needs some sort of lightning "wallet" and that then can have a local key that is used for nostr. (and keys are only locally stored and a wallet is always some remote wallet) this means you can add the same wallet to the extension and use this same wallet with different keys. you don't need to create a different alby accounts or different wallets. @RÒu Cao ⚑ I will pass it on.
Man... adding the same account multiple times is so weird. The account is added, but lots of error messages show up and there is no visual confirmation that you are adding the same stuff again. You just see a copy if the account in the menu. Also, it's very confusing when Alby creates a random nsec when loading an existing account. I would leave it empty.
yeah, that automatic account creation feature i'm not a fan either, it's confusing at first when you reinstall
↑