Pro tip, if you never untie your tie, you never have to tie your tie again

Considering defaulting to prepared statements on the database for the relay. I spent a lot of time trying to dynamically construct queries client side and will prob keep that as a backup for compatibility but it’s really just the same 10 over and over again.

My face when they pass my burrito to the new guy to finish rolling (calling 911)

Thought I solved my custom async Otel metric bug on the relay, but might have made worse 🤣 Time to call it a night

🌮

Why would you put a space in a perfectly good file/directory name??? - me a 🐍case maxi

test metric

I hate tracking down OpenTelemetry modules and instantiating the classes so much that I made a #Python package for it.

GitHub

GitHub - UTXOnly/OTel-metric-base: Python Metrics class for OpenTelemetry metrics

Python Metrics class for OpenTelemetry metrics. Contribute to UTXOnly/OTel-metric-base development by creating an account on GitHub.

Release time! Nostpy relay now supports Web of Trust and Tor. Join the relay below: wss://relay.nostpy.lol ws://pemgkkqjqjde7y2emc2hpxocexugbixp42o4zymznil6zfegx5nfp4id.onion Or host a relay yourself!

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

#dev #relay