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

Too little memory and my service had a memory leak problem. Drastically increased the memory for the server and suddenly memory garbage collection is working beautifully.

Have you noticed zaps going to an outdated wallet or old profile data appearing in some clients? It’s likely that you have stale metadata still stored on a relay somewhere. No worries – the Metadata Updater makes it easy to refresh your information. Originally a script, it's now a simple web application that you can host locally or share publicly. Clone the repo here:

GitHub

GitHub - UTXOnly/metadata_updater: Scans all known online nostr relays for stale kind 0 metadata notes, rebroadcasts latest verified note

Scans all known online nostr relays for stale kind 0 metadata notes, rebroadcasts latest verified note - UTXOnly/metadata_updater

You can also try out my publicly hosted dev instance @ https://dev.nostpy.lol/updater. Very open to suggestions as well!

How your email finds me this Friday afternoon

🤙🏽

Thank you to the peeps that DM'd me to let me know my LNURL was having issues. Adding zap server container to nostpy-relay stack and connected to my node at home Self-hosted zapping is back on the menu, we are so back...

I've been experimenting with relay administration using notes sent from a GUI client, specifically leveraging my own kind 42021 note (note spec to follow). I’ve developed a basic proof of concept that allows Nostr relay operators (or other implementations if they eventually support this kind) to: - Ban or allow pubkeys and kinds from posting to your relay. - Delete stored events from a specific pubkey. -View the allow list for pubkeys and kinds. All of this can be done without the need to SSH into the server or store private keys on your relay or computer. This is just a test case—there are already operators managing relays through notes, but there isn’t a standard relay admin API yet. There’s also ongoing discussion about whether this approach is the right one or if relay operators should instead use a web client for management. I welcome any feedback or criticism of this approach and greatly appreciate anyone willing to test it out!

GitHub

GitHub - UTXOnly/nostpy-gui: A relay management client for nostpy relay

A relay management client for nostpy relay. Contribute to UTXOnly/nostpy-gui development by creating an account on GitHub.

#grownostr #relay

I’m just gonna come out and say it I actually like Java **runs away**

Used

GitHub Profile Roast 🔥🔥🔥

to let a bot roast my Github page and it didn't hold back... Your GitHub bio sounds like it was generated by a Bitcoin-loving robot who just took a crash course in tech jargon. "All things Bitcoin?" More like "all things basic." With followers that could fit in a small room, it's clear that your charisma isn't quite as secure as your network systems. You've got 62 repos, yet somehow they collectively manage to gather less attention than a potato. It seems like you’ve got a thing for forking—maybe that's why your stargazers count is lower than the number of times you've updated your profile picture. Most of your projects feature the term "nostr," which sounds more like a bad spell than a promising project. Honestly, with a job at <REDACTED> in Boston, one would hope for a hint of innovation, but you’re just peddling template repositories like they’re hotcakes from a diner nobody wants to visit. Your code may be 'observably' absent of any real flair—putting the "meh" in "meta." Time to step up your game before the first page of the GitHub repo directory starts recognizing you as a permanent resident of obscurity!

Got my custom opentelemetry instrumentation running on the relay so I can trace every bad decision I make 🙏🏻

GM