21–30 of 101 posts
Wow, awesome. Will you add IRC?
I was considering adding IRC but I thought that almost no one uses it these days (sadly!) Ideally yes, I'd like to implement it. It's a stable protocol that's not going to change, so there's not much cost in maintaining it. What are you using IRC for?
Hi, 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, ev…
Will stay at the window for updates :)
When I get to work tomorrow I’ll be trying this out (knowing it’s in beta) for XMPP / Jabber, if it doesn’t already support OTR encryption - that’d be a killer feature. A big problem I see is that a lot of places want to or do run internal XMPP/Jabber because they have engineers working that don’t want to / can’t run ‘enterprise’ rubbish like Skype or those of us that are sick of JavaScript heavy SaaS apps like slack - but then you’ll have a few managers or project managers that still run Windows likely for excel or out of habit etc... and they have to use Pidgin - which while it works across a lot of IM systems - is very awkward and ugly as anything, so it gives the better protocols a bad name, on Mac there’s Adium which is a pretty decent multi-IM client but has stagnated somewhat. So a clean, easy to use, stable and well performing chat client that supports XMPP/Jabber with MUC and OTR would be an absolute killer.
Hi, 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, ev…
- 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.
Wow, awesome. Will you add IRC?
I was considering adding IRC but I thought that almost no one uses it these days (sadly!) Ideally yes, I'd like to implement it. It's a stable protocol that's not going to change, so there's not much cost in maintaining it. What are you using IRC for?
My company uses Slack, and I hate the iOS app, Windows app and the Linux app. It's bloated and slow!
I paid for the Mailbird app, and I'd pay for a fast and efficient Slack app too.