GM #nostr stay humble 🤙

Yo nostr:npub1qnm52v9xahnty3e3h9mt3eu0k3y75c05plcsu0vxngcrp38dey0sqwn5hz what gives?

🤣😂

nostr:npub1qnm52v9xahnty3e3h9mt3eu0k3y75c05plcsu0vxngcrp38dey0sqwn5hz a realistic honey badger, in bed looking at his phone

Cool. If there’s a way to do it by just tagging it, not necessarily in a DM, that’d be cool.

Still figuring out how to use this bot, but I just paid it 100 sats and got this via DMs 😂

Makes sense, thanks

Update: this baby finally showed up this week. #synthstr nostr:note16pjrt3qtskndz5algc8y75lwqj7rfe0gqvjv8zdp0ke6ufw5p5ks5qz9au

Thanks! This explains why pro tuners have an entire set of tuning forks. Though I imagine you could use a specially calibrated electronic tuner?

GM ☕️

I’ve always wanted to learn how. For someone generally knowledgeable about music and tuning other instruments, is there a steep learning curve?

Smart contract engineers in disbelief

nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8, it’s been a particularly rough couple weeks for me personally and at work. This reply, completely out of context, truly resonates 😂🧡🤙

Chile

🤝 ⚡️

Gm doggo

Of course not every stat on your dashboard would be available for historical values… but:

Timeseries by blockheight, and timeseries by UTC month/day/hour would be amazing.

I have done some of this for internal corporate use, DM me if you need data engineering help.

Timeseries

YES

True. But for certain types of content, I could see value in hashing some data into a block that proves it was posted at some relative (blockheight) point in time