

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.
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.
Electron. Many apps nowadays are just headless browsers and browsers are huge and complex. It’s nice from a development perspective, because you can (re)use web tools for desktop apps but it’s very resource hungry.
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:
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.
HTTP 418
You need more Excalidraw in your life.
I can recommend Restic with Wasabi S3 as cloud storage backend.
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.
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.
There’s being blunt, and there’s abuse. Linus attacks code, not people.
Maybe today, but certainly not in the past. I don’t doubt that Linus always had the best intentions for the kernel, but he nevertheless told other developers they should be retroactivly aborted. It’s hard for me to imagine that this version of Linus and a Linux CoC could’ve existed at the same time.
But I also get the impression that he did change quite a bit since then, now being blunt instead of abusive as you said. This shouldn’t be inherently incompatible with a CoC.
This does not actually work, right? Right?
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.
Regardless, though, my network setup usually consists of Factory Default Settings -> Assign a Static IP -> Configure port-based VLANs. It’s not particularly advanced. Most likely I wouldn’t even need to use anything other than the web-based management interface.
That’s pretty much what I’m doing with my Mikrotik switches too and I never had to touch the cli.
They’re saying that the proposed gender change (in the docs) will most likely not be accepted. That’s still bullshit, but to insinuate transphobia based on this comment alone goes too far IMHO.
Uhh, interesting! Thanks for sharing.