📢 Wrote a new app to send notes LATER
If you're familiar with my psbt.io site, this is like that, but for nostr
(and yes, I reused the gorgeous UI)
Discussion
Yes!
Does it set created_at to the future date and send immediately or does it actually wait?
Nice and thanks for implementing signing with an extension rather than asking to paste nsec like most of these clients smh.
How did you solve created_at? It is part of the signature no?
YES, it's interesting; I'm writing a longer note about it now
there were two approaches to do this:
1) use NIP-26 to create a delegation token to sign the note at the exact time
this was my preferred option and I wrote a bunch of code to make this happen.
https://github.com/getAlby/lightning-browser-extension/pull/2063
https://github.com/nostr-protocol/nips/pull/222
Implemented NIP-26 on damus
But there are some important issues
a) lack of relay and clients support
very few clients support NIP-26, meaning that the scheduled note would go unnoticed by most people
and few relays support it, meaning that the note wouldn't even be served
b) lack of constraints to delegation token
the NIP right now supports only limiting the scope of the `created_at` and `kind` -- this is
way too broad, since that means someone with the delegation token can write anything in `content`,
create as many events as they wish, tag as many people as they'd like
I started introducing a PR for NIP-26 to limit the scope of the `content` to a specific value but 🤷♂️
and c) no revocation of the delegation token
solution 2) pre-sign all possible events
this is less than ideal but there is no potential for abuse (other than publishing all signed notes but
that would be an absurd attack since you can't tag anyone with it nor change the content)
of course, since time is seemingly infinite, you can't sign *all* possible events, so need to limit
the from and to of the period and the frequency at which events will be generated; nostrit.com provides some sane defaults and makes it configurable.
Overall, I like NIP-26 much better than this solution (and this solution forces me to store a lot of
pre-signed events that I'm purging when their created_at falls in the past); NIP-26 would make this much easier
but until we have better support in the protocol and in relays and apps, this is a solution.
kek genius
Testing nostrit.com! #[0] #[1]
Awesome!
#[3] if I could make a suggestion… #[4] has an awesome interface where you can DM from your Nostr client and then they send you an invoice. Would be awesome to incorporate that as well for nostrit.com
👀👀👀👀
Also, I may have totally fucked it up but I am trying to publish the #[2] on the next block from your service 😂
😂 that's awesome, do you happen to have the URL it gave you?
ah, I see what happened!
sorry about the mistake -- fixed and zapped back
#[0]
Nostr it 🤙
#[0]
Fantastic!
That is really wild. 🥂
Nice. I have dotcom for Nostit if you want to make Nost the verb, which rhymes with post.
Oh nice! 🙏
Genius!
Great!!! 🤙
But will relays accept an event with a created_at set too far in the past? And where will clients show this sort of events in their timeline?
no, they will not; typing up a long note explaining this part since it's quite interesting imo 😉
As author of NIP-22, I’m interesting to see what you’re doing 😎
The ones that enjoy chaos will 😂
Hehe, I’ve already used this to backdate notes and troll some ppl 😂
reminds me of forging SMTP envelopes when I was a kid to mess with friends 😂
I'm gonna admit I'm a nostr newb...
So you can have a separate app to post to nostr? Is so, how does that work.
#[1]
wen publish 🤌 🔥
Hmmm. I should use this.
#[0]
🔥
Can’t use extension to sign in on iOS
Could you add support for authentication with https://github.com/nostr-connect/nostrum?
Pre-filled fields are accurate 💯🤝
这个小哥开发的针对Nostr的定时发送帖子的应用程序工具
可以根据时间定时发送nostr帖子
也可以设置指定事件发生时，发布帖子
比如比特币区块形成、比特币价格、某个山寨币价格，
虽然付费但感觉真的很有用
#[0]
