I'm not sure since it's been a while since I tried it on my matrix.org account, but I'd say it took about as long as logging in on a new device.
Chewy7324
According to this issue hcaptcha is not fixed yet.
And I just read the dendrite github page. The federation and client-server API's are complete, but the AS API isn't and things like SSO aren't implemented.
[...] there are still some missing features (like SSO and Third-party ID APIs).
We are prioritising features that will benefit single-user homeservers first (e.g Receipts, E2E) rather than features that massive deployments may be interested in (OpenID, Guests, Admin APIs, AS API).
Never change a running system :D
Thanks for the link to playbook. Since I only need a few bridges I just used docker compose and set the services up manually. I'm probably going to set it up with nixos at some point (though I'm gonna have to figure out how well an IPv6-only matrix server works, since my ISP took my v4 away on favor of ds-lite).
I'll definitely set up the sliding sync proxy for the time being. It's such a big improvement (after the initial sync) that I don't want to wait for native support in conduit. Especially since conduit takes some time to support new features quickly.
Yes, synapse performs and scales well at this point. They had to optimize it for the large scale deployments (e.g. government, health care). Dendrite and conduit need less ram after joining large rooms. Conduit even idles around 100MB if it's only on few small rooms, which is pretty awesome.
I never actually used audio/video calling since I mainly use matrix for communities and sometimes bridging, so dendrite and even conduit worked well for me for a long time. Now that dendrite is baasically feature complete I'm curious when was the last time you used it? I remember having issues with bridges one or two years ago.
The new Element X is really awesome. Since it's now in public beta I'm going to setup dendrite + mautrix-signal/-whatsapp/-discord behind their new matrix 2.0 sliding sync proxy.
The only thing I'm going to have to figure out is whether it's possible to disable image compression for bridges, because the quality was pretty bad the last time I tried (not surprising after being compressed 3 times).
I recommend checking out dendrite instead of synapse since it is more lightweight.
YouTube supports 160kbps opus, which should be pretty much transparent to our ears. But the audio is reencoded in the uploaded video, which then gets reencoded by YT again.
These multiple lossy reencodes are probably why YouTube audio sounds worse then Spotiy. Artists upload there songs as lossless wav/flac, which the gets reencoded/compressed a single time.
The problem is that desert sand is pretty much useless for concrete since it is too round.
In some places entire beaches disappear overnight.
BitTorrent, a p2p file sharing protocol.
V2 refers the to BitTorrent Version 2, an improved version of BT.
Hybrid means a torrent which supports BT V1 and V2.
I agree that for most people tailscale isn't selfhosted (except for the few with headscale). But Tailscale is easy to set up and configure, so I get why people love it.
And regarding the "antithesis of selfhosting", I read on here constant recommendations for Cloudflare Tunnel, which might be a great service but also is the opposite of selfhosted.
Now I personally switched back to wireguard directly since I had battery life issues with ts. Using wg directly makes a few other things easier to set up in my network.
PS: A great feature of tailscale is it's ability to create tls certificates for it's domains, so bitwarden doesn't complain about an insecure connection. This I could solve with dns-01 challenges, but then my router blocked the domains because of some attack vector. Now I have to manually whitelist them. TS makes this simpler.