I configured one client to connect ONLY that relay,
And then suddenly another client that i use went weird and goes nuts.
Really?
Yonle
_@waltuh.cyou
npub1x3az...g4el
a sleepy, lazy little programmer from Indonesia thats now in the early year of college that creates stuffs.
nostopus is my most beloved character in nostr
note: posts here don’t fully reflect how i interact elsewhere. this is just my personal noise space where i post thoughts, vents, and nonsense.
A client just made an arrival and then messes with my client relay listing.
Sometimes synchronization is just an "no-no".
"N U T"


What did i just done that made the arrival of you guys.


No idea. I will just leave it here.

Well, this is nuts.


xsync for concurrent map...
meanwhile, i struggled with concurrent read/write map operation when i was writing bostr2. i resolved it by reconstructing the code to use channels for solving the problem with concurrents.


Looks i know what's happening with my khatru being nuts with memory usage now.
Appearently query filtering IP rate limiter is the one who use the memory a lot. I could tell how is that happening.


Will launch pprof on khatru and see what's wrong with it.
Yep khatru got resource leak here.


our khatru relay, although has been configured to run with postgresql,
yet there seems still have some resources leak. memory usage never shrunks here.
Compare the memory usage of my bouncer and the khatru relay that is running for hours.


Initial usage was below 100 MB, and then slowly goes up to more than 100 MB.
The memory usage looks fishy.


Time to sleep.
bostr2 - version v1.0.2 stable released.
a #nostr relay bouncer to save your bandwidth when using #nostr.
This is a minor update.
# KA BOOM!!
# IT'S MODULES BUMPING!!!!
## what's new
- bump modules to latest version
- [nhooyr.io just got a new home](https://coder.com/blog/websocket), so i need to change it's home address in my code obviously.
## upgrading
this is an minor update. you could stick with v1.0.1 as things basically worked exactly the same.
```
go install github.com/Yonle/bostr2@v1.0.2
```
then restart your currently running bouncer.
**Full Changelog**: 
GitHub
Release v1.0.2 · Yonle/bostr2
KA BOOM!!
IT'S MODULES BUMPING!!!!
what's new
bump modules to latest version
nhooyr.io just got a new home, so i need to change it's home address ...
GitHub
Comparing v1.0.1...v1.0.2 · Yonle/bostr2
bostr next generation. Contribute to Yonle/bostr2 development by creating an account on GitHub.
bostr2 is actually using nhooyr's websocket module for it's websocket backbone.
How is it?
For normal user, It feels the same.
For advanced user, It's great.
For developer, It's great to code.
nhooyr.io/websocket got it's new home to coder.com
The coder github organization is also known for code-server, Which is an VSCode server.

Coder
A New Home for nhooyr/websocket - Blog - Coder
Coder adopted nhooyr/websocket and will continue to maintain it as an open-source library in our own GitHub organization.
Making an durable server software in the first place is really a good thing to do.
Because you never know what will happen next.
So you torture your own server by your own first and ensure there's no random crashes out of nowhere.
And this is exactly what i did to my own code.