Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coracle Social is nagging me to sign a kind 15 event #318

Closed
vicariousdrama opened this issue Mar 25, 2024 · 3 comments
Closed

Coracle Social is nagging me to sign a kind 15 event #318

vicariousdrama opened this issue Mar 25, 2024 · 3 comments

Comments

@vicariousdrama
Copy link

I don't know what a kind 15 event is, but the application is persistently requesting that I sign a kind 15 event, for which I'm denying

image

The details are a lot of event ids.

@staab
Copy link
Collaborator

staab commented Mar 25, 2024

Kind 15 is for read status: nostr-protocol/nips#933

The only way to make this kind of bookkeeping state interoperable is to publish it as nostr events, which triggers this kind of opaque dialog. That basically makes it impossible to micromanage permissions, so for now at least users will just have to trust Coracle to do the right thing.

Long-term, maybe the right thing to do would be to keep track of what signing requests have been rejected and not ask again.

@vicariousdrama
Copy link
Author

ok. I'll refocus efforts on the NIP07 extension makers to add some support like Deny in addition to the cancel and confirm choices that Alby presents. I haven't yet looked at how nos2x handles requests but its been a thorn to not be able to always ignore such requests when they come in.

@staab
Copy link
Collaborator

staab commented Jun 28, 2024

I've temporarily disabled kind 15, so this one is closed until I figure out what I'm going to do about read receipts.

@staab staab closed this as completed Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants