Support for Matrix.org?

[Julian Foad]

Johannes Ernst wrote, in another topic:

What I’d really like to see is a forum, but I’d really want the forum app to run on UBOS, and first somebody would have to package it up. Volunteers? ;-)

Julian Foad wrote:

Would Mattermost be suitable? It also supports IRC bridging via Matterbridge.

Neofytos Kolokotronis wrote:

There is also riot.im (based on matrix.org) if you want to look into that. It also has a bridge with IRC. It has a mobile client (also available on fdroid) and tracks history.

+1 for Matrix. (Riot is a Matrix client.) I have just been looking into that. Matrix seems to be a properly open solution for the domain of messaging in general. It bridges "to Slack, IRC, Gitter, and more", while keeping full message history. It is federated, whereas somebody said with Mattermost each server instance is itself a silo.

From an open-web point of view, it looks to me like Matrix is the Right Answer and we should be looking to support it, by packaging a Matrix server (there are a few different implementations to choose from) for UBOS and also use it as the project's communication system.

Here's the project's recent newsletter: The Matrix Autumn Special!

I'm new here, but from spending a few hours reading about Matrix, that's what it looks like to me. What do you think?

- Julian

[Johannes Ernst]

On Nov 18, 2016, at 9:54, Julian Foad <jul...@foad.me.uk> wrote:

Johannes Ernst wrote, in another topic:

What I’d really like to see is a forum, but I’d really want the forum app to run on UBOS, and first somebody would have to package it up. Volunteers? ;-)

Julian Foad wrote:

Would Mattermost be suitable? It also supports IRC bridging via Matterbridge.

We have Mattermost on UBOS. Not sure anybody is running it “in production” but it seems to work.

Don’t know anything about Matterbridge — any idea how to configure this?

Neofytos Kolokotronis wrote:

There is also riot.im (based on matrix.org) if you want to look into that. It also has a bridge with IRC. It has a mobile client (also available on fdroid) and tracks history.

+1 for Matrix. (Riot is a Matrix client.) I have just been looking into that. Matrix seems to be a properly open solution for the domain of messaging in general. It bridges "to Slack, IRC, Gitter, and more", while keeping full message history. It is federated, whereas somebody said with Mattermost each server instance is itself a silo.

From an open-web point of view, it looks to me like Matrix is the Right Answer and we should be looking to support it, by packaging a Matrix server (there are a few different implementations to choose from) for UBOS and also use it as the project's communication system.

Here's the project's recent newsletter: The Matrix Autumn Special!

I'm new here, but from spending a few hours reading about Matrix, that's what it looks like to me. What do you think?

- Julian

--
You received this message because you are subscribed to the Google Groups "UBOS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ubos-dev+u...@googlegroups.com.
To post to this group, send email to ubos...@googlegroups.com.
Visit this group at https://groups.google.com/group/ubos-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/ubos-dev/1e28eadc-6e04-4994-8aa6-4d67d2d62ef2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Julian Foad]

Johannes Ernst wrote:
> We have Mattermost on UBOS.

Yes, that's why I first suggested using Mattermost, but I don't have any
experience with it, I just installed it on UBOS and had a quick play
with it and then searched for information about whether it is a good way
to integrate IRC with mailing lists, and found that in principle it can
do that.

Then, continuing to research the subject, I discovered Matrix and formed
the opinion that Matrix looks like a better match for the open web
(IndieWeb) principles, by focusing on defining APIs and explicitly
encouraging the development of a diverse range of interoperable clients
and servers.

> > From an open-web point of view, it looks to me like Matrix is the
> > Right Answer and we should be looking to support it, by packaging a
> > Matrix server (there are a few different implementations to choose
> > from) for UBOS and also use it as the project's communication system.
> >
> > Here's the project's recent newsletter: The Matrix Autumn Special!

> > <https://matrix.org/blog/2016/11/12/the-matrix-autumn-special/>

At this point I am more interested in exploring Matrix.

I haven't looked at packaging for UBOS; maybe I will get a chance to get
involved at some point.

- Julian

[Johannes Ernst]

> On Nov 30, 2016, at 2:59, Julian Foad <jul...@foad.me.uk> wrote:
>> > From an open-web point of view, it looks to me like Matrix is the
>> > Right Answer and we should be looking to support it, by packaging a
>> > Matrix server (there are a few different implementations to choose
>> > from) for UBOS and also use it as the project's communication system.
>> >
>> > Here's the project's recent newsletter: The Matrix Autumn Special!
>> > <https://matrix.org/blog/2016/11/12/the-matrix-autumn-special/>
>
> At this point I am more interested in exploring Matrix.
>
> I haven't looked at packaging for UBOS; maybe I will get a chance to get involved at some point.

Sounds good to me. I currently don’t have any cycles to work on Matrix, but if you’d like to, I’be happy to answer questions!

Cheers.



Johannes.