Why is iris.to always asking me to sign a timestamp? what is it used for?

Reply to this note

Please Login to reply.

Discussion

I was wondering the same thing

It's saving the notifications / dm thread last seen timestamp. I'll make it stop asking if user rejects.

is it worthing making a NIP for this? wondering if other clients are using the same `d` tag, would love to support this in snort and have notifications synced across clients.

Hmm, maybe some "commonly used d tags" NIP or other list would be useful.

I'm planning on doing pinned posts with d tag "profile/pinned"

that's 🔥 we currently only do mute lists but looking forward to have bookmarks and pinned notes too. lists have lots of possibilities imo.

Here's my "path" API that I'm using for it. I'll try to make the API a little better tomorrow and add it to iris-lib, or PR to nostr-tools if #[5] wants it.

I'll change the API to simpler path.authors(array | string).get(key) and .set(key, value)

Oh, and I'll make encrypted paths use hash(path + secret) so it's deterministic, instead of encrypt(path) which has a random component

Perfection!

ah I see. but it stores it locally, doesn't it?

so why does it need to be signed?

It's stored globally on Nostr as a nip33 replaceable-by-tag event

ahhh, ok. thanks for the clarification. didn’t know about that.