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

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

My git fiasco may have been a big L this morning but the new tor support for the relay is working great 🙏🏻

Nothing like wrestling with a good old rebase and merge conflicts to remind yourself that you don't actually know how to use git as well as you think you do. On a totally related note, new nostpy release dropping later today 🎉

Spam testing is going well 😏 #WoT

Can anyone recommend some good developer resources for web of trust? #asknostr

Based subway ad campaign

Created a #nostr slack channel at work. Let’s see if there is a fellow nostrich or 2 out there… or are that early?

Getting live hurricane updates from family in the Sarasota area. They obviously lost power at this point but cell service is still working which is encouraging to hear 🙏🏻. Gonna be a long night.

Guilty

Made some more progress in the memory leak investigation for the metadata updater. Apparently the process below is the culprit: python3.12 -c from multiprocessing.spawn import spawn_main; spawn_main(tracker_fd=14, pipe_handle=16) --multiprocessing-fork I fully expect that process to use a lot of memory while the script is running but it holds onto it after the run has finished. Oddly enough, the same exact script returns to sane memory levels immediately after runs when instrumented with a continuous profile. Any Python folks out there have any ideas why this process won't let go of the memory if it isn't profiled? I've tried manual garbage collection in the script but it doesn't affect this at all. #asknostr #python

Chores be damned, it's DVM fiddlin' time