Uhh, interesting! Thanks for sharing.

No, it isn’t.

EDIT: I quickly want to add that Jellyfin is still great software. Just please don’t expose it to the public web, use a VPN (Wireguard, Tailscale, Nebula, …) instead.

It’s been a while since that I set this up, so take this with a grain of salt. I have these two plugins installed:

• Chapter Segments Provider
• The older Intro Skipper

I’m honestly not sure if I even need both - maybe the Chapter Segments Provider is unnecessary, even though it’s official and newer. I don’t understand exactly how it works from the docs.

However, Intro Skipper gives you a new scheduled task named “Detect and Analyze Media Segments”. Use this to extract metadata about media segments from your library.

Now that the server knows about some media segments you need a client that can handle them. I’ve had success with the Android TV App (check the settings) and the Web interface should support them too.

I didn’t need to configure anything aside from that, as far as I can remember.

The media segments feature has been released as of 10.10.0 and it still needs a plugin. Still feels a bit clunky but works already on my Android TV box. I guess there will be more polish in future versions, now that the groundwork is done.

… Nebula…

You need more Excalidraw in your life.

I can recommend Restic with Wasabi S3 as cloud storage backend.

You’re right.

We’ve decided that IPFS is not yet ready for prime time. We’ll still link to files on IPFS from Anna’s Archive when possible, but we won’t host it ourselves anymore, nor do we recommend others to mirror using IPFS. Please see our Torrents page if you want to help preserve our collection.

I’d say ask the original developer directly. Getting your changes merged upstream should be the preferred option for you, the original dev and the users. If everything goes right, you both could figure out a way to do this, maybe by re-introducing your refactorings and fixes one by one in smaller pull requests. Maybe you could become a maintainer in the process and support the original dev long term so everybody wins.

If the original developer doesn’t respond or declines you could think about bringing your own fork forward. Think about the consequences though, the original dev might get frustrated by a competing fork and abandon the project completely. The users on the other hand might be confused or insecure about which version to choose. Your fork must offer a lot for them to jump ship and switch.

Generally I’d say open source is about working together, not against one another, so just shoot them a message and see where it goes.

I’d recommend Quad9 or Mullvad as both have a good record on privacy. DNS is also often unencrypted by default, so make sure to use DoT or DoH while you’re at it.

Having a solution that works for you is never a bad thing.

Now it comes down to what you want to archive: Do you want something that just works? Great, you’re done - now go on and do some other things that you like, that’s perfectly fine. Or do you want to learn more about servers, virtualization, linux, networking and selfhosting in general? Then there are a million ways to get started.

I’d suggest to setup a little lab, if you haven’t already. Install Proxmox on your server and run CasaOS inside a virtual machine. Now you’ve learned about hypervisors and virtual machines. Afterwards you could create a second virtual machine to play around - maybe install debian and get used to the linux cli. Install docker manually, run some apps using docker-compose. Now you’re already doing some stuff that CasaOS does under the hood.

The possibilities are endless, the rabbit hole is deep. It can be a lot of fun, but don’t force youself to go down there if you don’t want to.

Thanks for your response! It wasn’t my intention to sound overly critical. Congratulations on your spectacular growth and good luck for the future! I’ll definitly keep an eye on ChartDB.

Interesting project. I wonder though how a repo that’s merely a few months old and has only seen 117 issues in total does accumulate 9.8k stars? Seems a bit fishy to me.

This reminds me of nebula although nebula does require a central server to coordinate hosts.

Security is something you do

Like by reducing the attack surface on internal APIs?

I don’t even necessarily disagree with you, everybody has to decide themselves if this app offers enough upsides to be worth the downsides.

That being said, instantly calling OP stupid and their project crappy is just not the way to get your point across and in general considered a dick move.

Thanks for the write-up! I’ve settled on Immich but it’s always interesting to hear about other peoples perspectives.

I use Wasabi S3, but only for my most critical data. For full backups including large media I setup a offsite NAS.

Regarding tooling I’m really happy with Restic (coming from Borg).

I’m currently having a good experience with MikroTik. I think their products provide a good combination of features and pricing. There are a “CRS317-1G-16S+” and a “CSS326-24G-2S+RM” in my rack and I have my eyes on the “CSS610-8P-2S+IN” as a efficient little POE switch.

I haven’t used Ubiquity, so I can’t compare these two brands.

For APs I’m currently using TP Link Omada with a selfhosted Omada Controller and for Routing, DNS, Firewall and stuff I use OPNsense.

If you try to spin up multiple services but get stuck on creating a directory, you’re moving too fast. I think you’ll need to start a bit slower and more structured.

Learn how to do basic tasks in the terminal and a bit about how linux works in general. There is a learning curve, but it will be fun! Then move on to docker and get one service up and running. Go on from there with everything you learned along the way and solve the other problems you’ll encounter - one at a time.

Do you want to build one yourself or are you mainly interested in off-the-shelf solutions? What’s your budget? Do you run your services as containers? Do you need hardware acceleration for streaming with Jellyfin/Plex?

I would like to already have some redundancy, can I use the hard drives as they are or will I have to do something to them besides adding other hard drives?

Why do you want redundancy? To keep your data available or to keep your data safe?