Sender | Message | Time |
---|---|---|
7 Feb 2025 | ||
* It also seems element x is only allowing for one sided conversations. Whoever starts the call is the only one able to talk. The recipient of the call cannot use video or voice chat. | 00:00:25 | |
01:59:15 | ||
In reply to @simulationfarmer:matrix.smellysavior.com I cannot tell if this is an issue with ntfy or an issue with Dendrite. When I first installed ntfy it had an error for not configuring the base url. Which I fixed when reinstalling it and creating a config file. Now ntfy has no indication as to why it wouldn't work in the logs. I have troubleshooted the notifications in both Element and Element X (Hell even Schildichat and Schildichat Next) and they all pass each test. It's almost as if Element isn't running in the background when closed. I have changed the app setting to be unoptimized for battery (did the same for ntfy) and no dice. Anytime I close the apps and re open them it is as if they crashed and restart. There is nothing indicicative in the logs for the containers (ntfy, dendrite, and sliding sync) that tells me something is wrong. This is occurring on two pixel 8s running GrapheneOS. I changed the notification settings to be constant, overide do not disturb, turn on vibration, etc. I even went as far to turn off exploit protection that did nothing. Notifications just stay inconsistent. I found this github issue that seems to be the problem I am having but I don't know if the "ip_range_whitelist" value is applicable to dendrite or if it's only applicable to synapse: https://github.com/element-hq/element-android/issues/7069 | 02:19:54 | |
I am curious If self hosting element call would fix this separate issue. | 02:29:02 | |
could the web socket connection be getting blocked by a firewall? | 04:51:06 | |
(if im getting this right element call and push notifications both use web sockets) | 04:52:43 | |
In reply to @bones_was_here:xonotic.orgPardon my ignorance but how woukd I go about diagnosing that? 😅 | 05:48:30 | |
* Pardon my ignorance but how would I go about diagnosing that? 😅 | 05:50:07 | |
* I cannot tell if this is an issue with ntfy or an issue with Dendrite. When I first installed ntfy it had an error for not configuring the base url. Which I fixed when reinstalling it and creating a config file. Now ntfy has no indication as to why it wouldn't work in the logs. I have troubleshot the notifications in both Element and Element X (Hell even Schildichat and Schildichat Next) and they all pass each test. It's almost as if Element isn't running in the background when closed. I have changed the app setting to be unoptimized for battery (did the same for ntfy) and no dice. Anytime I close the apps and re open them it is as if they crashed and restart. There is nothing indicicative in the logs for the containers (ntfy, dendrite, and sliding sync) that tells me something is wrong. This is occurring on two pixel 8s running GrapheneOS. I changed the notification settings to be constant, overide do not disturb, turn on vibration, etc. I even went as far to turn off exploit protection that did nothing. Notifications just stay inconsistent. I found this github issue that seems to be the problem I am having but I don't know if the "ip_range_whitelist" value is applicable to dendrite or if it's only applicable to synapse: https://github.com/element-hq/element-android/issues/7069 | 05:54:55 | |
11:31:50 | ||
11:42:16 | ||
Do dendrites have worker mechanisms like synapses? | 14:19:51 | |
no it uses multiple cores already | 14:20:23 | |
go is very simple to run concurrently, you just basically go func() and are done | 14:42:08 | |
turn off firewall(s) and see if it works :P | 16:01:01 | |
Lol my bad 😂😅 I do not think it is firewall because it seems the issue persists. I did decide to make a throwaway Matrix account to see if my ntfy setup works. ntfy seems to work on the official matrix server. Calls went through no problem. I then was wondering if it was my coturn server on my vps, but there isn't really anything in the logs that shows me it is the problem. Calls go through just fine on seperate networks. I am starting to wonder if it is a Dendrite config I have screwed up. | 18:12:31 | |
Has anyone recently evaluated if current dendrite is more performance than current synapse? | 18:12:44 | |
* Lol my bad 😂😅 I do not think it is firewall because it seems the issue persists with it off. I did decide to make a throwaway Matrix account to see if my ntfy setup works. ntfy seems to work on the official matrix server. Calls went through no problem. I then was wondering if it was my coturn server on my vps, but there isn't really anything in the logs that shows me it is the problem. Calls go through just fine on seperate networks. I am starting to wonder if it is a Dendrite config I have screwed up. | 18:13:36 | |
18:36:41 | ||
18:54:19 | ||
19:13:22 | ||
19:26:27 | ||
21:06:57 | ||
21:07:13 | ||
23:11:18 | ||
23:18:56 | ||
23:20:02 | ||
8 Feb 2025 | ||
01:20:21 | ||
In actual testing, dendrite joined a group of more than 10,000 people, and its response speed was much slower than conduwuit. | 01:31:57 | |
05:25:37 |