prosody-modules
fe8222112cf4
mod_minimix/README.md
Software / code / prosody-modules
File
mod_minimix/README.md @ 6199:fe8222112cf4
mod_conversejs: Serve base app at /
This makes things slightly less awkward for the browser to figure out which
URLs belong to a PWA. The app's "start URL" was previously without the '/' and
therefore was not considered within the scope of the PWA. Now the canonical
app URL will always have a '/'.
Prosody/mod_http should take care of redirecting existing links without the
trailing / to the new URL.
If you have an installation at https://prosody/conversejs then it is now at
https://prosody/conversejs/ (the first URL will now redirect to the second
URL if you use it).
The alternative would be to make the PWA scope include the parent, i.e.
the whole of https://prosody/ in this case. This might get messy if other
PWAs are provided by the same site or Prosody installation, however.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 11 Feb 2025 13:18:38 +0000 |
| parent | 6003:fe081789f7b5 |
line wrap: on
line source
# Account based MUC joining Normally when joining a MUC groupchat, it is each individual client that joins. This means their presence in the group is tied to the session, which can be short-lived or unstable, especially in the case of mobile clients. This has a few problems. For one, for every message to the groupchat, a copy is sent to each joined client. This means that at the account level, each message would pass by once for each client that is joined, making it difficult to archive these messages in the users personal archive. A potentially better approach would be that the user account itself is the entity that joins the groupchat. Since the account is an entity that lives in the server itself, and the server tends to be online on a good connection most of the time, this may improve the experience and simplify some problems. This is one of the essential changes in the MIX architecture, which is being designed to replace MUC. `mod_minimix` is an experiment meant to determine if things can be improved without replacing the entire MUC standard. It works by pretending to each client that nothing is different and that they are joining MUCs directly, but behind the scenes, it arranges it such that only the account itself joins each groupchat. Which sessions have joined which groups are kept track of. Groupchat messages are then forked to those sessions, similar to how normal chat messages work. ## Known issues - You can never leave. - You will never see anyone leave. - Being kicked is not handled. ## Unknown issues - Probably many. ## TODO - Integrate with bookmarks - tracking outgoing presence - leaving rooms - nickname management - bookmark sync # Compatibility Briefly tested with Prosody trunk (as of this writing).
