nyconyco

You will be soon able to evaluate Nayego as well: https://nayego.net/ you can subscribe if you want to see the preview.

Nayego is an open source and open standard team chat, that is federated/distributed/decentralised.

Yes, you are right, thanks for noticing and reporting, the landing page is slow these days, because under load, you guessed ;-)

That is the MUC room lastest messages logs. When you disconnect+reconnect fast you have them all the time.

With Nayego, we are working on that. https://nayego.net/ you can subscribe if you want to see the preview.

Oh Mircosfot's strategy is the weirdest: OCS, Lync, Skype, Skype for Business, Teams, Yammer... People are just lost.

Nayego is trying to hard build a HipChat-like client+server that is open source and based on XMPP. https://nayego.net/ you can subscribe if you want to see a preview.

We'll be trying to fix that by offering the XMPP "Team Chat" client that is much needed... https://nayego.net/ you can subscribe if you want to see the preview.

We are trying to fix the shameful situation: https://nayego.net/ you can subscribe if you want to see the preview, but it's work in progress.

Maybe you want to see the preview of our work in progress? https://nayego.net/ Open Source, real Open Standards, mature technology, decentralised/federated/distributed, and a great UX.

Fit for orgs with external partners, providers, customers, freelances, remote and home office workers...

That is right, I "exchange" screenshots against feedback, on a live interaction...

Yes, it runs on XMPP and SIP and WebRTC, and obviously HTTPS (because what does not?).

I understand.

A complete and comprehensive UX is not seen in a few screenshots...

Hey all here,

So I observe that lots of team chat users seem lost and don't what to do anymore.

The problem with alternative Open Source team chats attempts is that they are just another silo, or walled garden. Instances do not talk to each other. A private island cannot join continent. Even within the same organisations plenty of incompatible team chats are used competitively, fragmenting the workforces.

We propose to fix all that with Nayego: https://nayego.net/ Nayego is an open source team chat under development, that has a world-class UX, and that is federated/decentralised/federated like email.

Nayego wishes to address the organisations that are open and extended, where teams are working together with other internal teams, and with partners, customers, providers, but also freelancers, and remote and home office workers.

Nayego is and will remain free/open source and open standard (XMPP, SIP, WebRTC). If you wish to register to the preview, please go to: https://nayego.net/ We will do our best.

I used this timer: "Scrum Chatter", so that we have an equivalent time to speak... https://play.google.com/store/apps/details?id=ca.rmen.androi...

Hi everyone!

We are proud of this first beta before 2.1.0.

It contains very useful stuff:

* Push notifs:

  * XEP-0357, and a very new standalone open source push notification server, MongoosePush

  * Amazon SNS (Simple Notification Service)

* Full text search for MAM (Message Archive Management, XEP-0313)

* Continuous Load Testing

* Pipelining for faster reconnections

* Erlang distribution over TLS

Plus contributions by @astro, @aszlig!

The "MongooseIM Platform" welcomes a new server-side component: MongoosePush. It is in Elixir, it is open source.

Still a very strong focus on code quality and performance, mobile features, and this time a new component (Push) in Elixir!

I could point to this: https://stackoverflow.com/questions/31080970/erlang-hot-code...

It is worse, actually, because it uses GTK, and is only available on Linux and Windows (not macOS, although there have been attempts).

Most of the "big names" who provide modern and contemporary desktop IM apps deliver on the 3 platforms (Linux, macOS, and Windows), and use mostly web "technologies" (sometimes "pure browser", and sometimes with electron-like desktop "packaging")... so as a consequence, it is very native, indeed, but it is a generally consistent and continuous UX (user experience) between mobile/tablet and desktop/laptop.

One cannot not say something is "so open that..." ;-)

But indeed, XMPP is open, very open.

And indeed the major clients usually rely on the old era's ways of thinking messaging... They a far from contemporary, not only talking of features, but also the UX (User eXperience) and the general philosophy.

I would recommend the reading of XEP-0387: XMPP Compliance Suites 2017 (and its successors): https://xmpp.org/extensions/xep-0387.html

But I insist, this one is quite good, honestly: https://www.erlang-solutions.com/blog/21-xmpp-use-cases-and-...

Yes and no. The only production-ready of such a requirement is "MUC light". Basically, it is a very simplified version of MUC, that does not rely on user's presence. It exists in the MongooseIM server, in Smack library for Android and in XMPPFramework library for iOS, as well as in Mangosta iOS and Mangosta Android, two free/libre/opensource clients soon to be released. So it is ok to develop a solution based on this approach.

The "open extensions" is available here: https://mongooseim.readthedocs.io/en/latest/open-extensions/... We call this "open extension" because it was not accepted by the XSF, but it is very close to an open standard.

Swift implements - like Gajim discussed above - a very old and outdated UX, and thus cannot be relevant these days.

I speak harsh words, and I am sorry for this, but I was expecting much from Swift at its birth, but that was not delivered over time.

Indeed Gajim is quite stuck in the past, and I regret to say this as it hurts me, since I used to be a hardcore fan.

Conversations indeed is very decent.

MongooseIM (and ejabberd) are too big and complex to allow full hot code reloading. Moreover this feature is quite rarely used in any Erlang software.

Hi all,

MongooseIM, the massively scalable XMPP/Jabber server, written in Erlang, under GPLv2, is available in version 2.0.1.

What's new?

=> For DevOps/SysAdmins

Cassandra DB support for MAM (XEP-0313: Message Archive Management)

Simplified MAM configuration

ODBC/RDBMS backend for MUC light

MUC hibernation, for memory saving

=> For client developers

SSE (Server-Sent Events), as an addition to our client-side REST API, for server to client real-time push

XEP-0363: HTTP File Upload

Improvements to XEP-0016: Privacy Lists and XEP-0191: Blocking Command

=> Raw versions of the changelog

https://github.com/esl/MongooseIM/releases/tag/2.0.1

=> What's coming next?

Mangosta Android and Mangosta iOS: opensource mobile clients, with focus on social microblogging and group chats (just a humble techno demo, only available as source code, no intention to go on AppStore/PlayStore)

An opensource push notification server written in Elixir

An opensource ICE/STUN/TURN server written in Elixir

=> Links

https://github.com/esl/MongooseIM/

https://twitter.com/MongooseIM/

The documentation: https://mongooseim.readthedocs.io/

Any comment?

Telegram is still 2nd gen, as Group Chat is secondary feature, no message correction, but has reply