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.
Kotak donasi ke saya sudah tersedia lewat Trakteer / Saweria.
## Donation Box
You are welcome to send me donation if wanted.
- Liberapay: Coming Soon
- Lightning (BTC): humidprocess01@walletofsatoshi.com
- Saweria: [@yonle](https://saweria.co/yonle)
- Trakteer: [@yonle](https://trakteer.id/yonle)
NOTE: Donation sent into either any of these link is a separate donation to me, but not for lecturify.net team.
Don't think i would like to use Amethyst now.
App startup basically took 15 MB of bandwidth every single time from a single bouncer. Unminimizing the app after in background took 4 MB of bandwidth every time.
Months ago, I fixed bostr for Apple users. Specifically for client that use CFNetwork (Damus is one of them) and in web with Safari.
Now that it seems like the syndrome is still there except the client NEVER EMITTED THEIR USER AGENT,
I don't give a fuck.
This websocket compression bug that Apple hasn't fixed for more than 3 years is just another loser in my eyes.
If Firefox, Chrome, and other Websocket lib could deal with it, Why Apple couldn't?
ping - ping - pong.
if i got error,
that means you're dead
## what's new
- wipe zombie socket with pingpong detection
## upgrading
```
go install github.com/Yonle/bostr2@v1.0.4
```
then restart your currently running bouncer.
**Full Changelog**:
Not even a week i am away from nostr, Someone already tries to use one of our services on "unfair" level.
Last night i noticed that my server is lagging and bostr2 is using 600 MB.
Once checked, there are atleast 2 host opening more than 3 sockets to our bouncer.
So now, Implemented the limit in bostr2.