poVoq

joined 3 years ago
MODERATOR OF
[–] poVoq@slrpnk.net 2 points 3 hours ago

Snikket makes it quite easy, but the extra complexity of hosting from home is probably better avoided for total beginners.

[–] poVoq@slrpnk.net 1 points 3 hours ago

Yes, Matrix is a bit ahead with SFU calls (after depending on Jitsi Meet for a long time, which uses xmpp under the hood). But for most usecases it doesn't matter so much. On a modern internet connection a SFU basically only starts being useful in calls with ten or more participants. For corporate board meeting calls maybe, but your family call is also fine without.

[–] poVoq@slrpnk.net 14 points 3 hours ago (1 children)

There is no way sending free healthcare to foreign countries might backfire with the local population in the US, right?

[–] poVoq@slrpnk.net 1 points 4 hours ago

This might be interestng for some xmpp webclients, but there is also the work in progress: https://github.com/conversejs/libomemo.js

[–] poVoq@slrpnk.net 4 points 5 hours ago

For now voice and video calls in xmpp only lightly touch the server and are mostly p2p. This comes with some scaling issues but for small groups of around 5 people it works fine.

Movim is a bit special, for other clients it doesn't matter much.

[–] poVoq@slrpnk.net 1 points 5 hours ago

Any place you can bring a shipping container to can also be served by a water tanker truck capable of delivering 40,000 liters per trip.

If this was something you could fit on an offroad pickup truck, I might see some application in very remote drought stuck regions, but most of the time such regions have people with livelihoods depending on lifestock that also needs water, so 1000 liters a day is never going to cut it for them.

[–] poVoq@slrpnk.net 5 points 5 hours ago (2 children)

Movim specifically works a bit better with ejabberd, who also provide easy to use containers.

Prosody is more of a Lego set to build your own server, so I don't think they even provided official container images for a long time. There is https://snikket.org/ though which is an opinionated distribution of Prosody with easy to use containers. Sadly Snikket doesn't play so well with Movim out of the box.

In general it is probably easier to start out with a rented VPS. You can move to your own server later on when you got the basics down. Since XMPP servers are quite lightweight they run fine on low end VPS that can be rented for as little as 1€/month.

[–] poVoq@slrpnk.net 1 points 15 hours ago (3 children)

What would you need apps for? PWAs and pinned browser tabs work just the same. And also you can just use any other xmpp app with your Movim account.

[–] poVoq@slrpnk.net 5 points 15 hours ago

Due to the architecture of Movim with parts of it running on the server a "proper" app wouldn't make much sense. On the plus side this also means it is very lightweight in the browser, unlike JS heavy browser apps or Electron wrappers.

But since Movim is fully XMPP standard compliant, you can use a native XMPP Android app like Monocles Chat with the same account and have most features included in it as well.

[–] poVoq@slrpnk.net 5 points 15 hours ago (1 children)

You would be surprised how performant php7 and later has gotten 🤷

[–] poVoq@slrpnk.net 3 points 20 hours ago (1 children)

1000 liters per day is very little...

[–] poVoq@slrpnk.net 16 points 20 hours ago (1 children)

a fun built-in paint program to draw stuff into the chat

The main purpose is actually to easily annotate image uploads 😅

 

Quite nice to see some networks being supported that are lesser known in the west. Apparently there is a sizable number of Chinese XMPP users these days.

 

They recently added NVenc support in addition to the previous CUDA accelerated transcription runner. I didn't have time to test it again yet, but my NVenc setup inside the main Peertube container works great since the 8.x upgrade so this should be also useful.

 

Backwards compatible group chats (MUC) and e2ee is still work in progress though.

 

The recording of the talk should be available soon.

view more: next ›