The boomers were an absolute disaster of a generation.

Stood for nothing, fell for everything.

If you’re a boomer who’s mad at this sentiment spare me.

I don’t want to hear a word from anyone who’s mess I have to clean up.

Please share the best starting point Or site to learn more about nostrdb.

I believe It's not possible to access Twitter API without paying an absurd amount to Elon Musk. Other platforms don't even offer an API at all.

Outside our little group here no one knows and no one has any chance to know all the things being created on Nostr, and I'm sure there are many folks that would be very interested if they knew.

We need more people writing about specific Nostr initiatives, such as the groups subprotocol, the git subprotocol, the community relays, the bunkers, the decentralized app store, the multisig signers, the highlighting, the photo sharing, the very private secure messaging subprotocols, the outbox model, the bluetooth offline inter-device protocol, the decentralized wiki and other stuff.

If you know how to write 3 words without asking an AI to generate text for you please do it.

Along with android, search, and zaps on target for the notedeck beta release… giftwrap support in nostrdb is finally on my radar. Having giftwrap support in the local relay means it will treat unwrapped events like normal events (with no signature). This will enable you to query these notes like any other note in nostrdb.

Private thread replies? Easy. Private likes ? Easy. Private anything? Soon.

Interesting, good to know 😉

WHAT IS YOUR FAVORITE INTERNET BROWSER?

I have spent several weeks trying to replace the Blink API wrapper of npub.cash with a Cashu native alternative and its been a wild ride.

While Cashu mints do support WebSockets for realtime updates, it turned out that WebSockets are pretty difficult to work with, when you are trying to keep them and the subscriptions alive for long periods (in my case days).

But there is a second issue: You see Cashu mints enfore rather strict rate limits on their users. This is important as Cashu is account-less and preventing spam attacks is difficult. Usually this is no issue, as regular users interacting with a mint do not hit these limits. But npub.cash is a funnel. Instead of every user using their own IP to hit the mint, with npub.cash every user "proxies" through the services server.

Turns out this second issue is much bigger than the first one and WebSockets do not solve this. So I decided to build a scheduler that make sure that all mint communication happens as frequent as possible, but never to frequent. This module also solves the first issue, as it allows to queue polling tasks in a lower priority making sure the service stays up to date about payment activity.

If the server restarts it wont hit the mint with a gazillion subs at once, it will make sure they are evenly spread out through low priority calls, while always making sure there is "rate" left for calls that need to be instant.

I built this module externally, so theoretically I could publish it as npm package for structured and timed mint communication. Please let me know if you could use something like this (because as of right now I don't think most Cashu applications would benefit from this, npub.cash is not your usual Cashu application).

After doing some testing I think it is ready to put into an experimental version of npub.cash. I hope to release this on reckless-npub.cash by the end of the week.

ssh doesn't work when there is an infinite loop in a process somewhere eating all the CPU and memory.