No I was deploying regular conduit. Now I am trying conduwuit and when I try and connect it says it doesn’t support sliding sync. I cannot seems to find it referenced in the config file either.

EDIT: nvm I just read it is not implemented yet on conduwuit. 🥲 kind of a dealbreaker because I am trying to get element x working for group calling.

Its a joke, in that clip he says “two steps ahead, I am always two steps ahead” it was viral for a while.

https://media1.tenor.com/m/y7YaTci5Z4gAAAAd/two-steps-ahead-nikocado.gif

I would love to see what futo would come uo with in this department

Thats the route I was potentially looking at.

Lemmy wouldn’t let me post it 😭

https://media4.giphy.com/media/okLCopqw6ElCDnIhuS/giphy.gif?cid=6c09b952f50sg86gimzwzek5coa6ecqatmww8m12ta0kfltv&ep=v1_internal_gif_by_id&rid=giphy.gif&ct=g

I had read somewhere that matrix can see integration data like sticker packs. So while they cannot read the content of your encrypted messages they can see what stickers you are sending and reacting with.

I did not look extensively into a giphy scraper. I used different terminology that probably confused the search engine 🤦 couldn’t think of the word. Thank you I will look into it.

To my knowledge element x isn’t feature complete. Idk if joining rooms is implemented. You could try getting the regular element client to join rooms then go back and see if they appear in element x.

I use dendrite for my private server, it doesn’t support element x due to sliding sync. I’m gonna try to spin up conduit today at some point and will get back to you when I try out element x.

Do you have federation turned on in your config file

Yeah it seems they fixed it in 1.6.24 but fdroid is on version 1.6.20 😩

EDIT: Sorry wrong post response. I am trying out ntfy to see if it fixed it. It seems like it may have based on the few hours I have tested. I am gonna be running matrix conduit later tonight and test schildi next and element x.

I just installed ntfy and am going to give that a go for a while and report back!

So sorry my bad!

The device that struggles with push notifications is a pixel 8 with GrapheneOS. Element was installed through f droid.

Also another problem that I have been facing is I cannot multitask while in a call otherwise it cuts my microphone. I have to stay in app to be able to talk with the person I am in the call with.

Notifications work just fine on my desktop running arch.

I will update the post with this information.

In cloudflare I had my digital ocean dns record set to proxied when it needed to be “dns only”

That and I formatted my dendrite.yaml to have more spaces in the turn section than it should have. Now it’s all up and running!

Oh ok cool! I had just seen another forum where they mentioned it and became concerned.

Thanks again!

Holy. Fuck. You just did it. You absolute madlad. It works no issues!!!

Thank you!!

Just barely fixed that! Thanks! I have another issue thst I fommented about though:

Progress has been made!

So I got it working with the domain name. The turn testing tools now respond with relay and pin point the vps server! Nice!

However when I put the info into the matrix dendrite.yaml it still crashes. The logs say

“Invalid config file: yaml: line 210: did not find expected key”

“Invalid config file: yaml: line 206: did not find expected " - " indicator”

Line 210 and 206 refer to the turn section which is formatted:

turn: turn_user_lifetime: “5m” turn_uris: - turn:turn.exampledomain.com?transport=udp - turn:turn.exampledomain.com?transport=tcp

turn_username: user
turn_password: password
    

Progress has been made!

So I got it working with the domain name. The turn testing tools now respond with relay and pin point the vps server! Nice!

However when I put the info into the matrix dendrite.yaml it still crashes. The logs say

“Invalid config file: yaml: line 210: did not find expected key”

“Invalid config file: yaml: line 206: did not find expected " - " indicator”

Line 210 and 206 refer to the turn section which is formatted:

turn: turn_user_lifetime: “5m” turn_uris: - turn:turn.exampledomain.com?transport=udp - turn:turn.exampledomain.com?transport=tcp

turn_username: user
turn_password: password

EDIT: line 206 seems to be

• turn:turn.exampledomain.com?transport=tcp

And line 210 is uncommented description so I don’t know what that is about

I did fill that out, anytime I do matrix crashes and I think the logs say something along the lines of not being able to find the turn server. I just tried it now with the vps ip and port and it still caused matrix to crash.

The turn tesying tools don’t work with the URI at all its only the ip and port they work with.

When I use the dig A command it gives me different ips than the vps ip.

Sorry I jusy recently updated my comment. I was able to get it to say “relay” when using the regular public ip and port for my vps. It doesn’t work if I use the domain I created for it though “turn.domainexample.com”

The domain name should be pointed to the vps public ip type A

Paid subscription? No I only have the cloudflare domain and the vps subscription. Do I need the subscription to get this working? 😮‍💨

Or is there another solution?

So I checked and I do not think it can connect.

I have a cloudflare domain I am using and I am only using cloudflare tunnels for the matrix dendrite server not the coturn vps server. I am using cloudflare to setup dns record for coturn on my purchased domain. Is that still an issue?

EDIT:

so i just tried it with the regular vps ip address instead of the domain I set in the dns records and the test tools you linked say it is working that way.