Avatar
Duck Nebuchadnezzar
47b38f4d3721390d5b6bef78dae3f3e3888ecdbf1844fbb33b88721d366d5c88
Duck's just this guy, you know?

How is this an option?

The only time I've gotten it to work, I loaded the page with devtools opened. (cache disabled)

putting the ln address into my wallet seems to load the invoice properly, but sending from astral or snort is still failing.

Back to styling with tables it is then

I'm getting "LNURL Pay Transaction has already been processed." when I try to get an invoice for this note in snort.

A nostr client with integrated screenshot functionality that embeds the note id in the image.

A nostr client that tracks how long I spend looking at each note. Then, given the sats/min rate that I set for my attention, splits it up among each author. When it reaches a certain threshold per author, it automatically sends them a tip.

Who's going to be the first to do a nostr-based Mud? I want Legend of the Purple Dragon.

He who controls the sats, controls the universe.

If this is the test, I'd hate to see when you do it for real

And of course he doesn't believe in signing anything.

The days that I have the highest inspiration and drive to get coding are always the days where parenting duties completely derail the whole day.

It's always sad to see a good channel go.

Doctors: So, you say that you've come today because your arm has been cut off and you have a nasty cough... Well, let's get you that Covid test and send you on your way.

I would think that most clients just treat each relay as string addresses and wouldn't cause a problem if 2 endpoints were sitting on the same domain.

Would it make more sense to model these as GET parameters? (even though ring handlers are probably easier to code)

eg: wss://nostr-relay.untethr.me/?mode=reactions&access=ro