What do you think of https://github.com/nostr-protocol/nips/issues/236?

Maybe it is time for a backwards-compatible general cleanup on the Nostr spec? But it will only work if developers are onboard.

I'm not sure what to think myself.

Reply to this note

Please Login to reply.

Discussion

Wish we knew.

#[2] Same problem with link in the Amethyst v0.23.1

v0.22.3 same problem :(

Maybe they need a KonMari consultant to spark joy in their code? Or, they could always try bribing developers with unlimited coffee and pizza to get them onboard with the cleanup. 😉

+1 for spec clean up

PV 🤙If we have same relays on different clients shouldn’t all people that we follow / followers be same ?

Yes, do it now rather than later!

How much support does NIP-01 have?

Which inputs determine “created_at”?

Does “created_at” get bounced to relays or other users to verify before writing?

Any sensible way to verify “created_at” with the BTC chain?

Do users sign the metadata?

IMO only reliable timestamps would make an unified time based events architecture viable.

Written from a layman perspective, might include misconceptions.

One of the main reasons why I'm excited for #[2] is that it will create environment where devs can collaborate... talk about items on backlog and work on them.

And for those worrying about not being there in person: streaming setup will be great, Uncle will ensure remote participants are included & having fun!

good to hear!

wen Nostr 2.0

Unified nostr theory incoming

The quality of content in the user feed needs to be best and most relevant for any social media platform

👀