• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: December 30th, 2023

help-circle



  • 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.







  • 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.