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

The server seems to be offline for me right now sadly

Thanks for giving my little chat application some more publicity :)
It makes me happy that so many Haiku users enjoy using it.
Unfortunately you're right about the server,seems still offline currently,but usually the admin is fast to bring it back offline.
You notice that it's a private hobby project,not a commercial Big Tech service,but I really prefer it that way,even if that means downtimes from time to time.

Edit: It works now.

No problem I'm also working on fixing my forum but at this point I think I should use something else

I really like this forum software.
It's something unique that not everybody uses.
Also,it's clean and lightweight,unlike Discourse.
While I like the many features that Discourse has to offer,I greatly dislike its JS-bloat.
Good luck getting it to work in a slightly outdated browser,even in the latest Basilisk it needs some workaround.
Sure there are many more forum softwares,but not so many good ones.
You can mostly divide them into three categories:
1. Proprietary and insanely expensive
2. Open-source and modern,but with JS-bloat that makes it feel slow and painful
3. Open-source and fast,but the user interface looks like it hasn't been updated in the last 20 years
I was also trying to find a suitable forum software when I wanted to replace the old XenForo thing,but I didn't find something for years,so I closed the forum down.
Only recently I found a solution with Inyoka (that offers much more than just forum) and gave my old site a relaunch.

Inyoka I've never heard of that forum software before, I'm going to check it out

I'm having a problem with BeAIM: when I minimize the Buddy List window and wait, it is no longer possible to bring the window back.
When launching from Terminal I noticed it always happens after the following messages:

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 16 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 17 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 18 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 19 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 1A 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 1B 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 1C 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 1D 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 1E 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 1F 00 0A 00 01   00 16 00 00 00 00 00 00       *....... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 20 00 0A 00 01   00 16 00 00 00 00 00 00       *.. .... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 21 00 0A 00 01   00 16 00 00 00 00 00 00       *..!.... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 22 00 0A 00 01   00 16 00 00 00 00 00 00       *..".... ........
--------------]

Sending N😲p...
[OUTGOING PACKET (16 bytes)]
2A 02 00 23 00 0A 00 01   00 16 00 00 00 00 00 00       *..#.... ........
--------------]

The system is Haiku x86, there is one active user in the Buddy List (it is probably necessary to tigger the bug, not sure, needs more testing).

Thank you very much for reporting the bug.
I tried to reproduce it on two of my computers (one x86 and one x86_64),but it doesn't happen here.
On my main account,I had 3-4 active contacts,on my test account it was only one.
The messages shown in the Terminal are completely unrelated to this problem,they're network packets,more specifically ping packets that make sure you don't get disconnected for inactivity.
Are you using the latest version of BeAIM? (1.7.1)
Can you please show a screenshot of your Preferences->General window?
The settings there (especially about the deskbar entry and the tray icon) might or might not influence the behaviour of the bug.
I tried a few different settings with my main account,but knowing your configuration allows for more specific testing against that exact configuration.

I included this message from the Terminal because I was convinced it's a pattern when it happened two times in the row. Now it happened for the third time and there were 0 buddies in online state.
It also happens in a specific moment all the time: when the outgoing packet that reads "*..#" is sent.
Yes, I'm on the 1.7.1 version.
Here a my Preferences for BeAIM:



It used to be possible to bring the window back by clicking the icon in Deskbar, but now it doesn't appear there, regardless of the relevant checkbox in Preferences.