If you get a chance to go to the listening room in Nashville, don’t miss it. Wow!!!

what’s the coolest thing you’ve learnt so far this month?

I actually went to church growing up. Still had other kids trying to save my soul growing up.

If I could do anything I wanted I’d start a breakfast food truck.

If we ever meet in person and there’s a kitchen, I will make you breakfast.

You should open one called Breakfast For Lunch, because who doesn't want to eat breakfast for lunch? It's genius!

Powerball winner bought a new $47 million LA mansion after his $2 billion win, per NYP.

Referencing an external clock such as a block height does not solve the underlying issue.

Looking at the NIP0, the note id is also derived from the timestamp. The client can insert any timestamp, but it cannot publish the same note with different timestamps and the same id. This solves the consistency among relays issue, but does not solve the problem of a client faking the timestamp.

What could kind of solve this, is if all relays provided "received_at" field, which works similarly to created, except that it would be created on the relay. That would be a relay specific publish timestamp.

If you needed a global one, you cannot have an absolutely reliable one, but you can have a good enough one, if you just took the earliest received_at timestamp accessible on the relays you have access to. That one may change though depending on which relays you fetch the note from.

Mexico city?

But who will build the... oh

I would support an ad model that

1)pays me sats to display the ad in my feed, 2)which is opt-in by default (i.e.- the default setting for the platform is "No Ads," and 3)where enough ad blocks mark an ad as spam and permanemtly remove it (that is, once a certain # of npubs block an ad, it is treated by servers as malicious).