Someone had set the date wrong 😉 and boooooooooooo to you not making it 😭
Discussion
It’s nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpramhxue69uhkummnw3ez6un9d3shjtnyv4ex26mjdaehxtndv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7mze2ar's vibe codings fault
Lies. Edit the event.
How do you even edit this? 🤣
Scroll all the way to the bottom.
Did he figure it out lmao
It is set for the 22nd. Composes as the 21st. 🤷🏻♂️
Are you shitting me? nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424
Dates and timezones are hard apparently.
For the app? Or for nostr:nprofile1qqs9kqvr4dkruv3t7n2pc6e6a7v9v2s5fprmwjv4gde8c4fe5y29v0sprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wseplqlz? 🤪
For the app. NIPs want them in UTC or Unix time and humans want them in local timezones. I struggled with this a lot. I had it working I thought. Maybe it's broken still or maybe the Arizona timezone is just hard. Zzz now. I'll try and look tomorrow.
Well, we never change our clocks here, so maybe it’s that?
I’d say the timestamp is stored in UTC then the application / business logic needs to understand what the user’s local time zone is and convert it to whatever local time it is based on that user’s setting. It’s not really a Nostr thing, though, an application thing
It’s been a while since I’ve looked at the spec, but I’d say probably make most sense to store this in the metadata / profile event if you were to do it only using Nostr otherwise a db to support application specific logic
Thank you, nostr:nprofile1qy28wumn8ghj7cnzvgh8xctww3hhxtnvdakqz9thwden5te0v4jx2m3wdehhxarj9ekxzmnyqqsymxft68sj7auxvv6vu07lugpqx7vmlmacfdldtng3z2grg52hkkstwet4m! Now nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq37amnwvaz7tmwdaehgu3dwfjkccte9ejx2un9ddex7umn9ekk2tcqyqlhwrt96wnkf2w9edgr4cfruchvwkv26q6asdhz4qg08pm6w3djg3c8m4j has more on his to-do list 😉
PRs welcome 🤗