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

help-circle
  • I mean, calling out Musks hypocrisy is not a bad thing per se, but is it really news?

    At the end of the day a lot of people choose to remain on a platform that got bought by an gigantic asshole, who can now do whatever he wants with it. That’s how it works and being upset about it just shows that many users are either naive or delusional. Twitter can’t be saved, there’s nothing left.

    Combined with the fact that most Lemmy users probably know about this and already chose alternative platforms a long time ago, articles like these rarely cause more than a shrug, at least for me.

    But hey, if it get’s a few more people off of twitter (especially like large institutions as you mentioned), I won’t complain. As time passes I just tend to think that everyone who still stays on Twitter maybe belongs there.









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