Movim • Movim Blog

chevron_right

Create a jappix.com account on our XMPP server!

Timothée Jaussoin • pubsub.movim.eu / Movim • 2 December 2020 edit

https://upload.movim.eu/files/9d94237298995552fa13436420195fbca436dce7/oR5dAN4A6j9heD3pMDmVzOcd437aHXHCSysZGAje/Capture_d_%C3%A9cran_2020-12-02_09-07-46.png

In 2017, after some discussions with the #Jappix owner, the Movim team handled the administration of the jappix.com XMPP server and its 17.500 users.

Since that time, it was not possible to create a jappix.com account anymore (only the exisiting users were able to login).

A little upgrade of our registration form is now allowing you to register jappix.com accounts as well as the existing movim.eu ones.

And as expected, all the jappix.com #accounts can experience the same features as the movim.eu ones :)

Enjoy!

chevron_right

Create a jappix.com account on our XMPP server!

Timothée Jaussoin • pubsub.movim.eu / Movim • 2 December 2020 edit

In 2017, after some discussions with the #Jappix owner, the Movim team handled the administration of the jappix.com XMPP server and its 17.500 users.

Since that time, it was not possible to create a jappix.com account anymore (only the exisiting users were able to login).

A little upgrade of our registration form is now allowing you to register jappix.com accounts as well as the existing movim.eu ones.

And as expected, all the jappix.com #accounts can experience the same features as the movim.eu ones :)

Enjoy!

chevron_right

Create a jappix.com account on our XMPP server!

Timothée Jaussoin • pubsub.movim.eu / Movim • 2 December 2020 edit

In 2017, after some discussions with the #Jappix owner, the Movim team handled the administration of the jappix.com XMPP server and its 17.500 users.

Since that time, it was not possible to create a jappix.com account anymore (only the exisiting users were able to login).

A little upgrade of our registration form is now allowing you to register jappix.com accounts as well as the existing movim.eu ones.

And as expected, all the jappix.com #accounts can experience the same features as the movim.eu ones :)

Enjoy!

chevron_right

Reply to chat messages, a new Movim feature coming soon!

Timothée Jaussoin • pubsub.movim.eu / Movim • 1 November 2020 edit

A new useful #feature has been merged into Movim today. It will also be part of the upcoming 0.19 #release.

This change relies on the standard XEP-0201: Best Practices for Message Threads and allows you to #reply to a chat message using any XMPP account using Movim.

You could already find such feature on other chat platforms like #Telegram or #WhatsApp, the flow is also quite similar: on supported messages, click on the reply button and a little preview will appear next to the chat box input, fill in your message, publish, et voilà !

You can also navigate to the original message by clicking on the little preview (if this message is currently shown in the conversation).

Reply to chat messages feature

Enjoy :)

chevron_right

Reply to chat messages, a new Movim feature coming soon!

Timothée Jaussoin • pubsub.movim.eu / Movim • 1 November 2020 edit

A new useful #feature has been merged into Movim today. It will also be part of the upcoming 0.19 #release.

This change relies on the standard XEP-0201: Best Practices for Message Threads and allows you to #reply to a chat message using any XMPP account using Movim.

You could already find such feature on other chat platforms like #Telegram or #WhatsApp, the flow is also quite similar: on supported messages, click on the reply button and a little preview will appear next to the chat box input, fill in your message, publish, et voilà !

You can also navigate to the original message by clicking on the little preview (if this message is currently shown in the conversation).

Reply to chat messages feature

Enjoy :)

chevron_right

Reply to chat messages, a new Movim feature coming soon!

Timothée Jaussoin • pubsub.movim.eu / Movim • 1 November 2020 edit

A new useful #feature has been merged into Movim today. It will also be part of the upcoming 0.19 #release.

This change relies on the standard XEP-0201: Best Practices for Message Threads and allows you to #reply to a chat message using any XMPP account using Movim.

You could already find such feature on other chat platforms like #Telegram or #WhatsApp, the flow is also quite similar: on supported messages, click on the reply button and a little preview will appear next to the chat box input, fill in your message, publish, et voilà !

You can also navigate to the original message by clicking on the little preview (if this message is currently shown in the conversation).

Reply to chat messages feature

Enjoy :)

chevron_right

Movim just flattened the (connections) curve !

Timothée Jaussoin • pubsub.movim.eu / Movim • 21 October 2020 edit • 1 minute

A few days ago I discovered that the #Eloquent database library (the one that Movim is using for a few years now) had some events that could be caught by an event listener.

With this simple mechanism #Movim could be aware of when exactly a #SQL request is done during the execution time.

The Movim #architecture is based on several processes that talk to each others, and each connected session (each user connected to a specific XMPP account) is having its own sub-process. The main issue with this architecture is that all those processes relies on a common database (PostgreSQL or MySQL) and each process open an unique connection to the database. See How's Movim made? Part I - The Architecture to know more about this architecture.

When you start to have a lot of users connected on the same instance, this is opening lots of connections to the database. This is creating a congestion and can slow down the general performances.

This simple commit ask Eloquent to close the connection after a few seconds of inactivity. Eloquent is reconnecting automatically if a new SQL request is made after the disconnection. This allows to free-up the socket resources once "we don't really need it anymore".

And here is the result once this commit deployed on nl.movim.eu

The PostgreSQL connections curve

chevron_right

Movim just flattened the (connections) curve !

Timothée Jaussoin • pubsub.movim.eu / Movim • 21 October 2020 edit • 1 minute

A few days ago I discovered that the #Eloquent database library (the one that Movim is using for a few years now) had some events that could be caught by an event listener.

With this simple mechanism #Movim could be aware of when exactly a #SQL request is done during the execution time.

The Movim #architecture is based on several processes that talk to each others, and each connected session (each user connected to a specific XMPP account) is having its own sub-process. The main issue with this architecture is that all those processes relies on a common database (PostgreSQL or MySQL) and each process open an unique connection to the database. See How's Movim made? Part I - The Architecture to know more about this architecture.

When you start to have a lot of users connected on the same instance, this is opening lots of connections to the database. This is creating a congestion and can slow down the general performances.

This simple commit ask Eloquent to close the connection after a few seconds of inactivity. Eloquent is reconnecting automatically if a new SQL request is made after the disconnection. This allows to free-up the socket resources once "we don't really need it anymore".

And here is the result once this commit deployed on nl.movim.eu

The PostgreSQL connections curve

chevron_right

Movim just flattened the (connections) curve !

Timothée Jaussoin • pubsub.movim.eu / Movim • 21 October 2020 edit • 1 minute

A few days ago I discovered that the #Eloquent database library (the one that Movim is using for a few years now) had some events that could be caught by an event listener.

With this simple mechanism #Movim could be aware of when exactly a #SQL request is done during the execution time.

The Movim #architecture is based on several processes that talk to each others, and each connected session (each user connected to a specific XMPP account) is having its own sub-process. The main issue with this architecture is that all those processes relies on a common database (PostgreSQL or MySQL) and each process open an unique connection to the database. See How's Movim made? Part I - The Architecture to know more about this architecture.

When you start to have a lot of users connected on the same instance, this is opening lots of connections to the database. This is creating a congestion and can slow down the general performances.

This simple commit ask Eloquent to close the connection after a few seconds of inactivity. Eloquent is reconnecting automatically if a new SQL request is made after the disconnection. This allows to free-up the socket resources once "we don't really need it anymore".

And here is the result once this commit deployed on nl.movim.eu

The PostgreSQL connections curve