Since this is a selfhosting sub can you actually explain how you're hosting it?
stratself
joined 11 months ago
Hi, ntfy/another unified push backend is the third party. As in: it doesn't just go between you and your server
Android notifications are notoriously difficult to get right. May I ask how is Nextcloud Talk currently implementing notifications? Is it through ntfy, a background service, or Google's Firebase? Have you allowed background usage for both the push app and the chat app?
I use Matrix with Continuwuity and Element X, and it's doable most of the time except for small bugs. If you disable federation, the resource usage should be minimal too. But it also requires a third party for push service which can be unreliable.
On the XMPP side, there is also Snikket which you could look into. It offers both a server (running modified Prosody) and a mobile client (modified Conversations). XMPP can run as an efficient background service on Android, so it'll receive in-band notifications.
Regardless of options, one of the main problem I'm aware of is that Android variants tend to overkill various background app, leading to missed notifications. I think it's better to debug on that aspect as well
I don't think geoblocking would be a great fit for Matrix, since you'd be contacted by servers from all over the world. It's more suitable for something like a static website
There are various technical alternatives (ActivityPub-based stuff like PixelFed/Loops/Mastodon/GotoSocial/Sharkey/Akkoma/something else on the Fediverse)
But would you take the plunge of self-discovering different content, which might as well be none of your topics of interests? Would you be acquainted of vastly different UI/UX such as the lack of recommendations, a million client frontends, and the technicality of federation? And lastly, will you find it a place with communities to socialize and content to enjoy from in the long run?
I think trying out on a public instance would be a good way to answer those questions. PixelFed most closely resembles Insta, but the other ones can do too. Then you can consider selfhosting your own
How on earth do you have 54 release candidates, each of them adding significant feature, and not bumping your versions? Wouldn't it be nicer to just put them on the main branch and cut a semver release every now and then? At least that'll save on the frequency of posts here
When you say "on each device" you mean this configuration would refer to the services running on that device right? Not that every client device needs to have this set up?
The device that runs multiple services will set that up, yes. Not the client.
All my web services use apache or lighttd. Do I use caddy just for this or do I have to figure out how to move each of them to use this web server?
Apache and lighttpd can both do the same thing that Caddy does (multiplex many services via subdomain names on port 80). Caddy is just simpler and hence recommended.
You can move all services to use Caddy, takes some learning but overall better. Alternatively, if you already set up apache/lighttpd for each of your services, you can put Caddy in front and do something like
http://service1.devicename.lan/ {
tls off
reverse_proxy localhost:<port-that-apache-listens-on>
}
Also does it work for non-web services, like ssh or samba? (Which wasn't in my original question, I only thought of it now.)
No. Also, those should be running on their dedicated ports anyways
Use Caddy on each device, with tls turned off. Basically
http://service1.devicename.lan/ {
tls off
reverse_proxy localhost:8000
}
http://service2.devicename.lan/ {
tls off
reverse_proxy localhost:8096
}
What kind of network are you on? If you use public wifi/corporate network, then some of them might block XMPP ports (namely :5222/tcp and :5223/tcp) and has other very restrictive firewalls
You will need to create the address (or alias) using your newmatrix.org account. Check the space's settings and see if that could be done
You're probably interested in creating a firewall on openwrt that blocks all traffic from/to certain IPs
view more: next ›
yeah, it's consuming. I believe a big part of this is due to Matrix's HTTP sync-polling being more expensive than simply maintaining a TCP stream (which is what XMPP does)
In fact, since XMPP syncs in the background so well, I use Conversations as a UnifiedPush backend for Matrix. You can find another article here as well