Michael Pisman

Hi, I have the same issue. Have you found the solution? Hardware: RPI CM4 (no wifi/ no mmc) + RPI IO Board, Samsung EVO 980, pci-m.2 adapter that is tested....

Hi, I am also want to create some custom extensions for my project. Any updates on this? @mhamern could you elaborate how managed to implement it for your project?

> @mike-pisman Hi, after no response to my issue, I implemented my own very lightweight component and service. > > As for questions asked in the issue > > 1....

Could some eli5 what needs to be done? The documentation is lacking in this aspect. What should I put into the fields `well_known_client_name` and `well_known_sliding_sync_proxy`? Do I still need to...

Ok, I figured it out, was not hard at all and it fixed issue with android version of element client not connecting. @genofire, thanks for clarifying. I'm going to add...

Checking out the element-x, and getting errors on IOS and Android client. The `.well-known/matrix/client` returns the correct address of sliding sync ```JSON { "m.homeserver": { "base_url":"matrix.myurl.cc:443" }, "org.matrix.msc3575.proxy": { "url":"matrix.myurl.cc:8009"...

Indeed, any update on this?

I'm not an expert, but I don't think there is a more efficient way(if that's what you're looking for), unless you keep a list of document IDs manually: you can...

Hi, I am getting the same error on 2 servers, while the third one managed to start the pod: ``` [2023-08-10T02:11:01.133568146+00:00 INFO io_engine:io-engine.rs:179] Engine responsible for managing I/Os version 1.0.0,...

I have allocated 8 cores, 16 GB of RAM, and 64 GB of space, on all 3 servers. I will try to add more cores - 32, and will get...