#[2]

Send me $1k in btc, I’ll send you $2k back

Look at egress costs at your various hops. Consider geolocating data by using a CDN if you’re not already.

Things move fast on damus.

#[0]

Did you find the end of nostr?

Intending to keep these on an application-specific relay, but it’s always possible the events get xposted to public relays; in that case I’d like to ensure the events aren’t problematic

Nostr devs: is the Tags array the right place to add app-specific metadata related to an event?

If so, is there a tag type for this? In the nips I see type “e”, “p”, “r”, and “g”. Is it reasonable to just use a new one?

If not, where should we encode application-specific metadata? Is it preferred to use a custom kind and e.g. json encode data in the content field?

Where are you?

#[0]

Keep your eyes peeled for future announcements from #[3] or #[2] , we’ll be looking for beta testers soon!

LFG!

pvgm ☕️ 🌞

All keys already exist, they just have to be discovered. Presumably the “new npubs created” metric is more so a “first time seeing this npub publish an event”

Always have been

Yesterday I asked it to “write a function in go that creates a lightning invoice in LND using the SDK” and it was beyond satisfactory. 🤯

Let it rip

Can you ELI5 how LightningTipBot and Alby tie into an Umbrel stack running at home? Alby looks like a browser extension so I’m confused how it fits in for a damus user 🤔

PS thanks for the heads up on custodial BW

RIP 🪦

All it needs is a zoom account and deep fakes

Just gave ChatGPT the coding question $dayjob used to use for software engineers. Not a leetcode brain teaser, more of a implementation question that touches in data structures and concurrency.

It generated code that was well above satisfactory, including comments describing why it’s safe for concurrent usage. 🫠

777777 squad deep tonight