[Python] Slack channel pythonita

[Nicola Larosa]

> Nicola Larosa ha scritto:
>> Anche nella mia ditta stiamo valutando, finora positivamente,
>> Matrix e Riot, dopo aver scartato Mattermost per motivi
>> parzialmente analoghi a Slack.

Carlo Miron wrote:
> Interessante. Puoi/vuoi elaborare?

Non l'ho ancora provato, ecco la valutazione di un collega (citato col
suo permesso):

> * Mattermost is highly dependent on one only company that has an
>   enterprise version. There is no active community. (So for example,
>   if the company behind it is acquired or closed, Mattermost will be
>   surely dead and unmaintained).
> * Mattermost is a silo: cannot be connected/interoperated with
>   anything. Matrix has well-defined spec and APIs, anybody can make
>   clients and libraries to connect to it (examples: there's one for
>   Telepathy, another for libpurple/Pidgin, a Python module, a
>   JavaScript module...). Because there's an API, it's possible to
>   implement bridges to other networks with Matrix. For example there's
>   a working bridge for Slack, IRC, and a couple of services more
> * Matrix is a real community project.
> * Mattermost only has the web UI. Forget about “native” clients: they
>   are the web UI wrapped in Chrom{e,ium}: in Android it uses the
>   system WebView, in Windows and Unix it uses Electron (which is
>   Chromium). Nothing prevents doing the same with the Matrix web
>   client — and if you use Epiphany, you can just save it as a webapp
>   and be done.
> * The Android and iOS clients (Riot, previously known as Vector) are
>   native.
> * Mattermost does not support LDAP. Matrix does.
> * Matrix is very active. There are constant updates, bug fixes and
>   security fixes.
> * Usability problems in Matrix:
>   * Desktop and email Notification of new messages. 
>   * Not easy to go to the first unreaded message 
>   * Threaded messages

-- 
Nicola 'tekNico' Larosa <https://www.tekNico.net/>