matrix.org (communication)

[yusf]

I'd be interested in an integrations server app for Cloudron, built on dimension.

[yusf]

@msbt Would you bump the version please? v1.0.5 is the latest release.

[msbt]

sure thing @yusf, there you go: https://git.cloudron.io/msbt/riot-app

[yusf]

What’s the process of getting this to the App Store?

[msbt]

well, riot alone won't do much good. as for matrix: I would want to wait for v1.0 and redo the repo (v0.99.3rc1 got released today).

[msbt]

@yusf before you ask, I've just pushed the 1.0.6 update

[yusf]

@msbt Lol, I was just going to!

[msbt]

Matrix is also updated to v0.99.3: https://git.cloudron.io/msbt/matrix-riot-app

[yusf]

Btw, there's an inofficial Matrix channel at #cloudron:matrix.org.

[yusf]

So since matrix.org’s development infrastructure got megaowned today i figured I’d put this here:

After Matrix has restored its major services, they noticed that the GPG keys used for signing packages where compromised.

The key IDs are:

AD0592FE47F0DF61 (synapse)
E019645248E8F4A1 (Riot/Web)

Please make sure to no longer use those keys.

[yusf]

@msbt Errors installing Matrix app anew:

sed: can't read homeserver.yaml: No such file or directory

When looking in /app/data only nginx and synapse folders show, and they are both empty.

Please look into it.

[msbt]

hey @yusf
I've pushed another update for the latest riot and matrix apps. I did not set up email and ignored the turn settings too, since quite a few things changed since they're heading towards v1.0 and I don't have too much time on my hands. But I tested it and login should work for Ldap users. Thanks for the info, didn't realize it wasn't working on fresh setups.

[yusf]

Thanks so much, will try soon.

[yusf]

Works good so far. Email is not important in this case but TURN is, so I’m eagerly awaiting that feature.

Thank you for fixing it.

I just reread an earlier post of yours. From this version of synapse an onwards, will there be forward compatibility? It’s my bad I didn’t read it properly and of course my fault for installing unfinished packages but since I’m pretty screwed if I can’t upgrade this package later I want to inquire if that’s the case and possibly beg you to keep future versions compatible with this version. I’d help with testing if that

[yusf]

Idea: Put index.html in /app/data so that it's editable.

[yusf]

Building app I get deprecation warnings:

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.

Is that on app or box level?

[msbt]

This message is on app-level but valid nonetheless. In a week (10th of June) there should be the release of v1.0 and I'll do a rebuild of the container with python 3 and hopefully audio/video support. I'll keep you posted.

[yusf]

That is great, thank you!

[msbt]

fyi, v1.0.0 got released earlier and I'm working on it. Everything is looking good so far, the only things that aren't working at the moment are videocalls (audio is working) and the integration server, not sure why. Will keep you posted and eventually push the "final" version so people can test it.

[yusf]

That’s exciting. Your work is much appreciated, @msbt .