Skip Navigation

Posts
19
Comments
564
Joined
2 yr. ago

  • Really?

    Well, thats first.

  • Love this... Will take a spin for my OpenAstra

  • TubeArchivist rules

  • If that's hard, good luck with synapse then.

  • Continuwuity... Don't use synapse, too bloated.

  • Continuwuity was never discontinued, the note was for Conduwuit, I forgot to remove it after updated the article.

  • Yes need to fix that wording its a leftover, done.

  • I also installed tuwunnel after conduwuit death. Moved to Continuwuity because of the community vs corporate sponsorship.

    I don't keep an eye on who is ahead, but I want to be sure I don't have to migrate in the future so I don't care for development speed, rather continued support and what if tuwunnel company money runs out?

  • Yes both element and elementx and actually any matrix client. That's the beauty of having standards

    But its a pain because all clients from matrix. Org will push you to matrix. Org and need manual taps&clicks to select a different server when you sign up the first time. A bit annoying IMHO and maybe even fraudolent.

  • That is undisclosed but check the github page, last time I did, it was a one person job and he clearly wrote he got corporate money t do that

  • Tuwunnel is a corporate-sponsored successor to Conduwuit.

    I prefer Continuwuity which is a non for profit successor to Conduwuit.

    Beside this, they are probably mostly the same

  • Forget about synapse and the "official" method. Install Continuwuity a matrix server written in rust, much much more efficient than synapse.

    I took some notes while installing it here https://wiki.gardiol.org/doku.php?id=matrix%3Aconduwuit

    I didn't use docker but directly installation is very easy, it's a single executable.

  • Set a custom private DNS with your dns

  • DOH goes over port 443 using https, impossible to block (unless you want to blacklist all possible URLs that might serve DNS) so cannot be redirected at network level, like with classic DNS, and uses SSL encryption so cannot be "sniffed" and redirected.

    In other words: say goodbye to ad blockers based on DNS like pihole or adguard

    While it seems good for your privacy, it's a dream for Google and such, where PiHoles and such DNS blockers will be useless...

  • For now yes but the very specifics of DNS over https make that impossible if enforced one day.

  • I removed health checks because o think they don't work properly with podman how I use it, but I might be wrong.

    Anyway, glad it helped! That's the spirit why I wrote it.

  • Actually I am behind CGNAT so when away I connect to my VPS that has a nginx pointing to a wireguard endpoint to the internal server. Wireguard is also managed by opnSense but that's a choice, not mandatory.

    When home, my VPS ip gets rerouted on port 443 (and 80, mandatory for let's encrypt) to the internal ip of my server.

  • Going the split DNS way is doable but had other issues (android devices bypassing local DNS for example or DNS over HTTPS issues)

    I set up my opnSense to redorect all internal traffic to the external IP on port 443 to my internal server ip.

    Works fine, it's transparent, and doesn't mess with DNS.

  • I run TA with success since many months. It's fast and responsive, so I guess it's an issue with your setup?

    The metadata bridge to jellyfin alfo works pretty nice, I have no complaints...

    You can check my notes at https://wiki.gardiol.org/doku.php?id=services%3Atubearchivist

    But be advised I am on rootless podman with docker compose