Can I write down multiple questions in this issue?
Here's what I wish this could do.
I wish the remote store would be an arbitrary Nostr service that has that capability. but if they die and cut my storage, I will push my local copy elsewhere.
The remote does not have access to my data, as it is encrypted using my npub, and my nsec is required to decrypt. similar to https://github.com/spwhitton/git-remote-gcrypt which use OpenPGP. Maybe we should too?
I wish to be the owner of my repo, meaning force push are forbidden. people are free to create a new branch if its not fast-forward, and I can do the force-push to the main branch if I think its appropriate.
only a defined list of writers can push, but also then content should be re-encrypted I guess with the list of writes that that list is updated.
with OpenPGP, I think its possible to use a parent key, and child keys. I think that's how keybase.io does it for teams and devices.
Teams has multiple users, and a user are composed of a group of device. each device has a child key to the master. the master private is known to noone, and each device as a private that can authorize other devices. That's how I understand it.
but how do they not reencrypt everything when granting or revoking access, is not something I understand fully.
can we do that with Nostr?
Can I write down multiple questions in this issue?
Here's what I wish this could do.
I wish the remote store would be an arbitrary Nostr service that has that capability. but if they die and cut my storage, I will push my local copy elsewhere.
The remote does not have access to my data, as it is encrypted using my npub, and my nsec is required to decrypt. similar to https://github.com/spwhitton/git-remote-gcrypt which use OpenPGP. Maybe we should too?
I wish to be the owner of my repo, meaning force push are forbidden. people are free to create a new branch if its not fast-forward, and I can do the force-push to the main branch if I think its appropriate.
only a defined list of writers can push, but also then content should be re-encrypted I guess with the list of writes that that list is updated.
with OpenPGP, I think its possible to use a parent key, and child keys. I think that's how keybase.io does it for teams and devices.
Teams has multiple users, and a user are composed of a group of device. each device has a child key to the master. the master private is known to noone, and each device as a private that can authorize other devices. That's how I understand it.
but how do they not reencrypt everything when granting or revoking access, is not something I understand fully.
can we do that with Nostr?