WHO TF IS DAN !?!?!?

Don't ever underestimate the power of taking a break when stumped on a task I just wasted <REDACTED> hours troubleshooting an issue while testing deploying Nostpy relay as a ECS fargate cluster and the whole time it was the health check for the load balancer target group that literally took me 3 minutes to fix 🥴

Zap_server now supports fetching invoices from your tor node via a Wireguard VPN tunnel, doing this over tor was taking a very long time creating a bad user experience for people zapping you. Also now creates kind 9735 zap receipt notes and broadcasts this to all relays in the zap request. See the doc added below to create a Wireguard VPN tunnel between your clearnet zap_server and tor node for MUCH faster invoice fetching:

GitHub

GitHub - UTXOnly/zap_server: An LNURL server to fetch invoices from a tor hosted Bitcoin lightning node, specifically made for NOSTR zaps

An LNURL server to fetch invoices from a tor hosted Bitcoin lightning node, specifically made for NOSTR zaps - UTXOnly/zap_server

#relay #lnurl #zaps

Pretty sure I just donated sats to the bitcoin burn fund due to a lightning mishap....again 🙃

Def stealing this “Wanna get juicy?” line to invite people out drinking.

PV, get outside and lock your uncle in a bathroom

Writing zap_server to fetch invoices via tor was a mistake, was taking like 8+ seconds to return an invoice. Saw a number of invoices getting generated but not paid and plenty of failed ones too. I am still going to leave the capability in the project for those that want/need it but just tested using a Wireguard VPN tunnel instead and not surprised but it returns an invoice in a fraction of a second from the same tor node.

Going away this week and accidentally booked 2 tickets to my destination on different dates and no trip home. I think it maybe time to put the hash oil pen away for a bit

Catching up on all the voicemails and notifications I’ve been ignoring for months and found this gem 🤣

You know I keep that MF thang on me..🦌🔫

Bug squashing and slashing lines of code left and right today 🤙🏼

Happy to report Pizza Hut is alive and well in Portugal This is living 🤙🏽

Are snails bugs? IDK I’m eating em

Gm

Are there any restaurants that do t serve bacalhau in Lisbon? If so please LMK and I will be sure to avoid those places.

I've got espetada, lapas, carne de vinha d’alhos, and frens 🫂 on my mind...

Nostpy v0.8 released! 🎉🥳 Were moving now, and I am very interested in continuing to work with other relay/client devs to improve relay search functionality. Holla if you're trying to hack on this.

GitHub

GitHub - UTXOnly/nostpy-relay: A nostr relay backed by a postgresql database, run with docker-compose

A nostr relay backed by a postgresql database, run with docker-compose - UTXOnly/nostpy-relay

NIP 50 search is working on Nostpy for searching content and tags fields, should have added this a long time ago

Is there a list of clients that support NIP-50? I have come across a few that seem to be building the query client side rather than sending something like: { "search": "orange" }. Testing some search functionality on my relay, it's working from the command line client I made but want to test with real clients before releasing.

New focus for next release of Nostpy, supporting NIP-50 search capability for kind 30402 classified listings by searching tags column Feel free to join in if you have any ideas/suggestions! Working on this here:

GitHub

[FR] Support for NIP-50 (search capability) for both content and tags · Issue #37 · UTXOnly/nostpy-relay

Background NIP-50 enables clients to add a search filter included in their REQ queries. The spec only requires searching content field and the rest...

Trying to open up the discussion to other relay and client devs here: https://coracle.social/groups/naddr1qvzqqqyx7cpzp4q7xsdz6p636akhnafg9yru265l572nerhyqzhxeuu8waej8nfaqqgnxvfn8ymnjd3kxs6ngwpjxvergdgz3jre7/notes