Support multiple owner npubs?

[dergigi]

I'm not sure if it's currently possible, but this would be great for teams & projects.

Example: RHR would whitelist these 3 npubs:

• npub10uthwp4ddc9w5adfuv69m8la4enkwma07fymuetmt93htcww6wgs55xdlq
• npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0q9y6hjy
• npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx

...you get the idea.

[aaccioly]

We get this request frequently, the last time that I spoke with @barrydeen the consensus was not to mix concerns, i.e., Haven should be a personal relay. He is working on a separate whitelisting capable relay at https://github.com/bitvora/sw2

[barrydeen]

Yeah I think the better implementation would be to use bitvora/team-relay for situations like that, haven is intended to be used to store hyper sensitive personal data like ecash and drafts which don't quite fit

Perhaps I'll add blossom to that relay soon

[dergigi]

Sounds good. Will give team-relay a spin once it's ready. Thank you.

[dergigi]

Not saying I want to change your mind, but just as an additional comment / additional context: I run many bots and accounts, e.g. for my various projects, websites, and books, and they are all "me" in some sense, not part of a team or org. It's all my stuff, and I want it all on my relay.

Right now I'd have to set up a HAVEN for each npub, and as it stands that would be 8 different instances of HAVEN.

That's why I created this issue.

[dergigi]

A non-nostr example of this would be e.g. successful YouTube creators that branch out into multiple channels/accounts, so that they don't "pollute" their main with stuff that's irrelevant to their original audience. Some YouTube creators have 3/4/5 different channels, all active.

They'd have to spin up 5 different things right now, but I guess the "teams" version would fix that.

Again, thanks for all the work you do and apologies for the wall of text, but I thought maybe the additional context is useful in some way.

[flox1an]

Right now I'd have to set up a HAVEN for each npub, and as it stands that would be 8 different instances of HAVEN.

@dergigi I also use multiple npubs and have the same issue. I have created a branch with support for multiple owner npubs. Should work but no guaranties: https://github.com/flox1an/haven/tree/feat/multiple-owners

The sw2 relay is very bare bones right now and not really an alternative.

[aaccioly]

This looks very cool. You may want to make a post about it on Nostr as several other people are likely looking for something like "multi npub Haven".
I'll keep this issue open for now so that folks can find it as well.

[barrydeen]

Alright i'll cave, I don't think we want to start forking it's probably better to just add it as config and @flox1an made a pretty good, simple implementation for it. If you PR it i'll merge it in

[aaccioly]

Hi, I noticed this has been open for a long time. I'm now fully focused on v2, which feels like the perfect opportunity to work on fun and not necessarily backwards compatible changes, including support for multiple keys in Haven. @flox1an, I’d love to know if you’re still interested in contributing your changes upstream; it would be great to collaborate on this.

[dergigi]

I don't have much to contribute except for saying that I'm still very much interested in that feature!

[flox1an]

I have rebased to the latest version and created a PR: #93

[dadofsambonzuki]

I don't have much to contribute except for saying that I'm still very much interested in that feature!

#metoo