exu

2b

Oh cool, I somehow missed that in the docs

Yes, but AFAIK that’s only for local multicast discovery. If you have a server listening for connections somewhere, those aren’t password protected and anyone can connect to them unless you restrict the accepted keys.

I’ve never heard of this, but looks pretty cool. I use Yggdrasil in my homelab and on the surface this looks pretty similar in that both are decentralized mesh VPNs. The goals are somewhat different though and I think that shows in some choices the projects made.

Just reading through the docs of AWL it looks pretty good. They use libp2p for transport encryption and NAT traversal. libp2p itself is a spinoff from the IPFS project and pretty widely used. Compared to that Yggdrasil does not have any NAT traversal built in, instead every node is capable of relaying traffic and it will find the best route through the network.

The bootstrapping in AWL relies on community nodes, though you can host your own. Yggdrasil similarly has public peers if you want to participate in the official network, but you can just not configure those and use one or two of your own publicly reachable servers to build a separate network. That’s how I have mine configured, with a VPS and another public server being the primary relay nodes.

In AWL you must explicitly allow other peers to connect to you. That’s pretty good, otherwise you could just reach any other server on the network. Yggdrasil has similar functionality in that you can specify which public keys can connect to the server, but defaults to allow any member so potentially less secure than AWL.

I’d be curious to know which ip ranges AWL uses for its address scheme. I could only find reference to 10.66.0.2 for the public test server. Yggdrasil used ipv6 addresses in the 0200::/7 range, that’s technically reserved by IETF but has been deprecated since 2004. With this you’re certain to not have conflicts, the usual ipv6 local range is fc00::/7

For other interesting projects also Nebula. It is completely self hosted but not decentralized. You need one or more special nodes called “lighthouses” which are used for the initial handshake between nodes. This has some advantages like ACLs for different nodes.

Another fully decentralized project I’ve looked at but never tried is EasyTier. I think last time I checked it did not have any ipv6 support

Imo the best app for Jellyfin i Finamp, make sure to use the beta release for the updated UI and general huge improvements. It’s been in the works for a while and works great as a daily driver.

Jellyfin can use a bunch of sources to get metadata for music, some by default others by installing a plugin, but it’s much more hit-and-miss than movies or series. That’s just due to how much more music there is and how relatively worse metadata for music generally is.
Personally, I add a few albums at a time and make sure the metadata is correct using kid3.

Maintainability is probably similar between the two options. Jellyfin obviously can handle other media as well so if you need something to watch movies that would result in less maintenance needed overall.

I used to run Navidrome for a bit, but soon after the Finamp beta started so I didn’t feel the need to go with the broader app selection of Subsonic.

Do note that njalla isn’t a real registrar like all others. With normal registrars you are the legal owner of a domain name and your registrar has to follow ICANN rules. If you rent through njalla they own the domain and can do whatever they want with it.

Do you think the rest of your life is enough time to finish Star Citizen or do you like it as it is now?

• Terraria
• Nier: Automata
• X4: Foundations
• Deep Rock Galactic
• Beat Saber
• Baldur’s Gate 3
• Stellaris
• Witcher 3

And I still have 2 games left to choose

Get a NUC or old laptop and install your distro of choice on it. Much less hassle than barely supported ARM boards with ancient kernels.

This is missing an Astolfo

Image

I think Amazon and Qobuz both offer some music for purchase.

Their reasoning is literally the second sentence on that page.

Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases if required for later cleanup work

Any 10.Y.Z release is cleanup and can include breaking changes. That’s been the case for 10.9 and 10.10 already btw.

This is the database rework that’s been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.

They’ve been putting ads on your home screen for years