deleted by creator

Setting up Element Call on my instance was difficult on its own, I understand why Synapse doesn’t come with it out of the box, essentially you spin up Matrix’s JWT service for authenticating clients and it if approved forwards the connection to the Livekit ports which must be opened on your firewall (ie port forwarded), otherwise people will not be able to connect to calls.

Big PITA and in my experience, on my home network, can conflict with games with VOIP chats so don’t follow the default 50000:55000 port range Livekit recommends or you’ll run into issues like I did, each person consumes 2 ports so adjust the range to your need.

Edit: I don’t suggest running Element Call standalone, it has issues of its own, once you get Livekit and JWT running and follow This guide you should have your element call support in Synapse now, pro-tip for those running synapse behind docker and get confused on the whole ./well-known part of the documentation you can edit your ./well-known in your homeserver.yaml file like such:

serve_server_wellknown: true

extra_well_known_client_content:
  optional: client
  "org.matrix.msc4143.rtc_foci": [
      {
          "type": "livekit",
          "livekit_service_url": "https://livekit-jwt.your.domain/"
      }
  ]

Element and Element Call, although no streaming audio support on the horizon anytime soon.

I stand corrected, apologies.

deleted by creator

You don’t necessarily have to host another Jellyfin instance, I would find a server somewhere in-between the middle of your current Europe server and your Asian homies and setup a reverse proxy there and point it to your current Jellyfin instance.

The only hassle with this is you’re going to need a way to expose your Eu Jellyfin to the new server, a VPN would prevent port forwarding 443, perhaps split tunneling?

Not the most elegant solution but at least this way you can make an attempt at optimizing the connection.

Edit - (if you wanted to go the second Jellyfin instance route): Could also copy your current database to the second server, host a second Jellyfin instance and have something like sshfs or sftp sharing the directory to your media library, reverse proxy it as something like asia-jellyfin.your.domain and keep it separated from your Eu server.

This software is more meant to be ran in a server environment, it’s suppose to be a replacement to subscription based photo/video cloud storage. I would not recommend you run this on a desktop you use daily as it’ll consume resources in the background slowing your desktop down, this is kinda why NAS storage systems exist.

Once you get a grasp on the BASH shell I would suggest playing around with docker and docker compose in a headless environment (headless = no desktop environment, shell only) as there are loads of applications you can self-host over your network.

Pretty sure Bibliogram was inspired by Nitter before it became deprecated. Hope to see this flourish.

Yup, it works 90% of the time. Happens on all devices so I suspect Searx is just running into an error of some sort. Too lazy to investigate.

I host my own SearXNG via docker compose, reverse proxied it via Traefik, added a few security headers, restricted access to my country to help prevent abuse.

Use it daily, the only complaint I really have is it occasionally doesn’t search when you type in the address bar of a browser. What I mean is I’ll type a search query and instead of redirecting to the query (searx.yourdomain.tld/search?q=test) it’ll just redirect to the homepage of my SearXNG instance (searx.yourdomain.tld) forcing me to retype my query. Annoying but not the end of the world.

Some specific drivers are a little fiddly if you have nvidia graphics

Nit-picking here but Nvidia drivers for Debian are ridiculously easy to install? Doc page

• Prerequisites

deb http://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security/ trixie-security contrib non-free main non-free-firmware
sudo apt update

• Install the driver (Trixie)

sudo apt install nvidia-kernel-dkms nvidia-driver

• Have an RTX capable GPU?

sudo apt install libnvoptix1

Edit: For an Nvidia Optimus Laptop just install envycontrol and set your Nvidia GPU as your primary GPU.

sudo envycontrol -s nvidia --force-comp --coolbits 24

Done, easy peasy.

sad times

I don’t use Home Assistant personally as I also use Apple products, if you read into Homebridge it’s a piece of software that turns smart devices that are not HomeKit enabled devices into HomeKit enabled devices, and enables new functionality to devices that are already HomeKit enabled. Definitely worth considering.

This was significantly cheaper than converting all my Apple products into android products.

To quickly spin it up I would suggest reading into Docker and Docker compose, docker takes applications and containerizes them and lets them run over your network.

Finamp certainly needs some work but it’s far better than the native Jellyfin application, at least for iOS/iPadOS, I can now listen to music in the background.

Hell the Finamp contributors took my suggestion on a way to sort playlists and actually implemented it so I gotta say much props to them.

Thought you had to pay for that? Recently I’ve been eyeing Go Away as a potential alternative.

I just geo-restrict my server to my country, certain services I’ll run an ip-blacklist and only whitelist the known few networks.

Works okay I suppose, kills the need for a WAF, haven’t had any issues with it.

Tried to setup a personal matrix server last night, got it to federate, next step is Matrix’s Element Call, spent too many hours trying to block the /_synapse endpoint with Traefik because it is recommended by Matrix, no luck unfortunately.

All this in hopes I can add a Music Bot to my instance or something similar.

This was a while ago so the details are fuzzy, I gave it Traefiks docker labels on port :5380 but that didn’t seem to work then I read an a bug report saying give Traefik :8053 so I tried that and again didn’t work so I went back to :5380 and all of a sudden it reverse proxied but my login wouldn’t work even though it worked when going to the LAN IP+Port didn’t find much in terms of troubleshooting and documentation so I eventually gave up on it.

I have had terrible experiences with recursive DNS resolvers, PiHole+Unbound worked for maybe an hour then would completely kill my internet access, the same essentially went with OpenSense, I had hope for Technitium but alas didn’t feel the need to spend hours troubleshooting something that PiHole alone did with ease.

If only reverse proxying Technitium wasn’t a pain in the ass to do I would actually use it. Maybe one day they’ll fix the login issues until then PiHole works.

This just in:

Looks like someone took the liberty of uploading copyrighted shows and 3D printable gun parts to his file server.