-
Notifications
You must be signed in to change notification settings - Fork 198
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
Performance issues #422
Comments
If I only use the filter like |
I think on v2 we switched to pure JavaScript decryption, while before we were using the browser native libraries. |
However, how to deal with the problem of slow reception |
You can rewrite the logic using browser libraries (or copy the old code from v1) in your app. I think you should be using NIP-17 for DMs though, it is much better and hopefully everybody will be moving to it soon. |
nip-44? |
I use version v2.0+for message sending and receiving, which is very slow, and the filtering conditions for receiving messages do not take effect in the new version.
`
async function execSendMessageAndReturn({ message, from, to, sk, kind = 4 }) {
}
`
const filter = {
since: event.created_at - 50,
kinds: [4],
'#e': [event.id],
'#p': [p]
}; This code does not take effect in the new version.
The text was updated successfully, but these errors were encountered: