BeAim is an old school Aol messenger Its currently working on haiku OS Its open source as well heres the source code to it at codeberg.org You can also contact me on BeAIM my Username is whitepaperkat dont worry I wont bite

I removed the BeAIM folder from /boot/home/config/settings and uninstalled the application. Then I downloaded the latest version from codeberg and installed it with HaikuDepot. The Terminal output is not freezing on that "*..#" point anymore, but the Buddy list window is still not possible to Show all at some point. The Preferences->General checkboxes are all in a checked state now as is in default installation.
EDIT: edited to say it's stopping pinging the server at that *..# point again.

Thanks for debugging this with me,unfortunately I still can't reproduce the problem here.
First of all,your settings look totally fine,I use the same.
It's also interesting to know that it always happens when the Terminal shows "*..#".
I opened BeAIM on both my 64bit nightly and 32bit nightly computer,hide the window and watched the Terminal.
A good while after "*..#" was already over,I tried opening the window again and it opened without any issues.
Another idea for testing: What happens if you let the BeAIM window open and do nothing until the "*..#" message in the Terminal?
Does it continue to work as usual,or does the window become unresponsive or even crash?
Also,what Haiku version do you use,Beta or Nightly,which hrev?

I have since eliminated the possibility that this is somehow related to the timing of that *..# message - it happened once way before *..# was even reached and went slightly above it few times. I'm using hrev59041 Nightly and I'm beggining to think this could be related to my unstable Wi-Fi connection. If I login with working Internet connection and then in network preferences disable my Wi-Fi, that seems to trigger it.
And to answer your question; if I leave the window non-minimized there is never any problem - the application is responsive and I can message myself and I get server response - that means the connectivity is not lost.

Testing unreliable connections brought up another bug that I'll need to fix soon,but it didn't trigger this one.
I tried it again on my two desktop computers and additionally a laptop with Wifi.
On each of them,I logged into BeAIM,hide the window,disconnected the internet using network preferences and waited a few minutes.
While the internet was disabled and after I re-connected the internet,I could always open the BeAIM window without any problems.
The new bug that I found is that BeAIM acts like it was never disconnected,I can still write messages and it looks like everything is working,but it isn't,since the connection to the server is closed and doesn't automatically get reconnected.
Normally,BeAIM should notice that and show a warning that the connection is broken.