https://github.com/Yonle/bandwidth-hero-proxy
Recent Changes:
- Add cluster support
- Separate event functions
- Bump Dependencies
Recent Changes:
- Add cluster support
- Separate event functions
- Bump Dependencies
GitHub
GitHub - Yonle/bandwidth-hero-proxy: Fork of bandwidth-hero-proxy with additional fixups.
Fork of bandwidth-hero-proxy with additional fixups. - Yonle/bandwidth-hero-proxy
To my fellow that play / fan of Blue Archive:
Open your browser, and type https://cunny.school . That domain will redirect you to the official Nexon's Blue Archive website.
That's it.
I am not affiliated, interested, or even playing the game. The information that i give above is from an 4chan user.
Anyways, Have a nice day everyone.
That's it.
I am not affiliated, interested, or even playing the game. The information that i give above is from an 4chan user.
Anyways, Have a nice day everyone.
This media is not supported in your browser
VIEW IN TELEGRAM
Alright. Reencoding from GIF / APNG to Webp works.
A random Telegram user PMs me out of nowhere, sending link to their Tiktok.
And to give some attention, the TikTok has "yonle*" on it, as it is like they are asking me to give my current Telegram username (@yonle) to them.
And to give some attention, the TikTok has "yonle*" on it, as it is like they are asking me to give my current Telegram username (@yonle) to them.
Yonle: Notes and Other
A random Telegram user PMs me out of nowhere, sending link to their Tiktok. And to give some attention, the TikTok has "yonle*" on it, as it is like they are asking me to give my current Telegram username (@yonle) to them.
3 days, got 3 random users PMing me.
If not, The message that i receive is just a single "Hola".
Meh.
If not, The message that i receive is just a single "Hola".
Meh.
Alright. Things goes well with my bandwidth-hero-proxy fork.
At first, I thought that the memory is never cleaned, But turns out sometime it is cleaned and then RAM usage drops to 9%.
And that was interesting way of NodeJS / V8 handle memory.
When idle after usage, Memory usage was 22%.
Well. I guess i could sleep for this one
At first, I thought that the memory is never cleaned, But turns out sometime it is cleaned and then RAM usage drops to 9%.
And that was interesting way of NodeJS / V8 handle memory.
When idle after usage, Memory usage was 22%.
Well. I guess i could sleep for this one
Well. For ytmous,
In nightly branch, The memory leak problem is ultimately decreased.
But i think i know what was causing it to happen.
In nightly branch, The memory leak problem is ultimately decreased.
But i think i know what was causing it to happen.
Yonle: Notes and Other
Well. For ytmous, In nightly branch, The memory leak problem is ultimately decreased. But i think i know what was causing it to happen.
You see those two codes that i marked?
Yeah. Seems like the event functions is recreated in the memory, too.
Yeah. Seems like the event functions is recreated in the memory, too.
I know how to fix it.
Just like how i did with bandwidth-hero-proxy, Separating the event functions.
However, For code like ytmous, It is not always an easy task to rewrite those big codes up.
Just like how i did with bandwidth-hero-proxy, Separating the event functions.
However, For code like ytmous, It is not always an easy task to rewrite those big codes up.
Not only that i need to separate those functions,
I also need to use my IQ to know what to put with those shortened function.
I also need to use my IQ to know what to put with those shortened function.