Nostr Web Client

Proposing the o'block standard for nostr clients.

For an international community time conversion is, and always has been, a major headache. In my opinion nostr is perfectly placed to introduce the o'block standard to it's users. If it is for meetings, starting time of a stream, a Zapathon or anything else, o'block is always the same time for everyone.

Thus I'm proposing that app developers add a block height counter to their apps. Perhaps including the users local time just below. Doesn't require it's own NIP, simple enough to add and it puts everyone on the same time.

Written at 815,134 o'block

I'll be live on ZapStream around 815,142 o'block

Today's #Zapathon will commence at 815,172 o'block

$boost for visibility.

mIX 2y ago

It would kinda work for a general "block time estimate", but it would end up messy since blocks are ~10 min apart. If someone makes 5 posts in 10 min they're all going to show from the block. I'm thinking this roughly works only if each client showed the current block time too.

Honestly this is a BTC'er specific request and lots of people won't like it or find it useful. A block clock of some type would be required to know what the current block is.

I guess some clients could have the option to enable or disable?

I think I'd rather see the poster's time offset from mine, so I know if they're three hours ahead or working from the other side of the world. But that's probably not a great idea in some ways. hah.

Reply to this note

Please Login to reply.

Discussion

TheGrinder 2y ago

Agree with you on using it on a more precise time scaling but for most events it could be used as a good standard. I announce my streams and the Zapathon every week in this format and generally works out most of the time. If a block is a few minutes behind I simply start my stream a few minutes later. Make no difference.