The problem is not AWS going down. The problem is panicked developers putting in fixes at 2 AM that turn out to cause problems two days later.

@ZapTok Trying this out. On desktop I see this on every page:

Today marks DAY TWENTY-NINE of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we are highlighting one Nostr developer each day, and sending a zap of 100,000 sats to that developer. Today we are zapping @Cameri🐦‍🔥 .... creator of the NoStream relay.... Thanks @Cameri🐦‍🔥 ... Your 100k zap is sent! -- Please help us with the “30 Days, 30 Devs” initiative... simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!

@YakiHonne @REDKAZ⚡️| YakiHonne great work on the newest release of yakihonne.

Today marks DAY TWENTY-FOUR of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we are highlighting one Nostr developer each day, and sending a zap of 100,000 sats to that developer. Today we are zapping @Cesar Dias , developer of

nosotros.app

A decentralized social network based on nostr protocol

Thanks @Cesar Dias Your 100k zap is sent! -- Please help us with the “30 Days, 30 Devs” initiative... simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!

@fmar Having trouble zapping you. Are you self-hosting your own node possibly with not great connectivity?

@brugeman we were able to zap you 21 sats, but not 100,000 sats... are you running your own node and do you have enough inbound liquidity for big zaps??