- THANK YOU! It's near impossible to find a client that isn't either run in a console (admittedly not the worst problem) or horribly bloated (what the hell are people thinking when the bundle a browser to show a single page!?).
- What do you think of adding Matrix (https://matrix.org)? The protocol is HTTP + JSON based and well documented.
- Have you thought about open sourcing? My guess is either you want to sell this eventually or your coding standards are quite high and you doubt people can contribute too much while meeting them. In the case of the latter, I'd still like for it to be around, even if your standards for PRs would be too high for me to meet.
Of course, the same problem can happen for a multi protocol client as well, but at least it's not inherently impossible to solve it there.
Matrix will definitely be implemented at some point. Not within the first 2 months unfortunately.
Yes, my standards are pretty high, but like I said before here, I do consider open sourcing it.
> I'm obsessed with performance. The entire application is about 4 MB, and it's never going to be more than 10 MB. In fact there are still many things to optimize. It's native, so you don't need to download a 100 MB browser just to use your IM client.
So having a lightweight client is definitely appealing to me. However Slack keeps adding features often and every one using Slack assumes the recipient runs the same version of Slack as his.
I wonder how can your unofficial client can deal with this problem the next time Slack releases the next update that is as big as adding threaded conversations for example.
I came across the new threaded conversations yesterday, and they can be implemented in one or two days.
I will definitely be trying this out.
However a question essential for our pending use is: any plans to support HipChat? That would pretty near seal the deal for my current group.
Eul's target audience is primarily professionals, so it's silly of me to forget about HipChat. I just had a look at its API, and yes, it will absolutely be supported. In fact, most likely this is going to be the next protocol implemented.
Should be done by mid-August.
If it's at all possible, we'd love to have a build compatible back to macOS 10.10. Right now, it can only run on 10.12 and we work in a large enterprise where updates are withheld for mostly software-compatibility reasons (a lot of media software relies on older systems).
Though I would think it would be similar to something like https://github.com/ocornut/imgui
Will stay at the window for updates :)
Thanks
eul is a very lightweight and fast native desktop client for Skype, Slack, Gmail, VK, FB, Jabber, Telegram, and Signal. Right now only the first four are supported, and the rest should be done by the end of August.
Why did I create this? To solve two big problems I see with the current IM solutions: there are too many of them, and the clients are ridiculously bloated for what they are built to do. For example, everyone knows what a huge resource hog the Skype client is. Even the Telegram client, which is supposed to be lightweight, is using 1.3 GB of RAM on my desktop right now.
I'm obsessed with performance. The entire application is about 4 MB, and it's never going to be more than 10 MB. In fact there are still many things to optimize. It's native, so you don't need to download a 100 MB browser just to use your IM client.
eul can display thousands of messages in one conversation without the constant page fetching. The scrolling is instant and smooth. You can jump to any message without waiting. I've tested it with 50 000 messages in one chat. No lags, instant scrolling to any point, instant search. That should be enough for most :)
This is a very early alpha release. A lot of essential features are still missing (for example, images and other attachments are not supported yet). Automatic updates will be released every day. There's a built in contact form, please use it to submit bugs and suggestions.
Looking forward to hearing your feedback :)
Thanks