• 18 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle




  • I’m pretty sure Firefox doesn’t know how to cast, that’s a chrome feature.
    Secondly, a chromecast dongle can either be targetted locally by an app (such as chrome) or over the internet via https.
    If you are just hosting on your windows laptop, you probably don’t have a domain with TLS, yes?
    From localhost (the laptop itself), if you run chrome, you can probably cast to your dongle whilst on the same LAN.

    If you have one of the newer Chromecasts with the remote, you can simply install the Jellyfin app on it directly, and address your Jellyfin install by IP and port.

    Plex uses some fancy redirection work around these limitations, but it relies on an external service that they provide.






  • When you set up your libraries, it’s important that you point the path at the root folder, jellyfin expects a fairly specific naming convention.
    Here’s how it is suggested to setup your tv shows for instance: https://jellyfin.org/docs/general/server/media/shows

    Simplistically, lets say you have 2 shows called “Friends” and “The Witcher”, each with multiple seasons, and your NFS mount is /mnt/media.
    You’d create something like: /mnt/media/tv
    That’s where you’d point your tv library, at that “tv” directory. It doesn’t actually matter what the directory is called, but the library should be of type “shows”.
    Under that /mnt/media/tv directory, you would create a directory for each show, and it would be the name of that show, so you’d get: /mnt/media/tv/Friends/ and /mnt/media/tv/The Witcher/
    Then under those directories you would create seasons, to put your episodes in, ie /mnt/media/tv/The Witcher/Season 01/The Witcher - 01x01 - The End’s Beginning.avi
    /mnt/media/tv/The Witcher/Season 01/The Witcher - 01x02 - Four Marks.avi

    If you pointed the root of your library at /mnt/media/tv/The Witcher/Season 01/, it would probably fail to parse the episodes.
    If you create your library as /mnt/media/allmystuff/ and just ram everything in there, it’s unlikely to find anything.
    This may all seem a bit complicated, but there’s lots of tools that are useful to automate this process.
    I personally recommend https://sonarr.tv/

    If you are doing all of the above correctly, we’ll have to dig a bit deeper for more details.

    As for “unsupported formats”, that most commonly happens when you have enabled hardware acceleration and it’s not working properly.
    Whilst there’s several reasons why it may not be working, to rule it out, try temporarily disabling Hardware Acceleration under Dashboard -> Playback -> Transcoding.
    The system should fall back to CPU transcoding which may be slow (hardware dependent), but at least it should function.

















  • I want to be clear, that I disagree with his “federation is stupid” point, but email has problems right now.

    Theoretically it’s federated, theoretically you can spin up your own mail server and self host.

    But even if you do that absolutely perfectly (SPF, DKIM, DMARC etc), you can falsely end up on spam list, that effectively block delivery of your email to large segments of the network for days if not weeks.

    Whilst theoretically federated, email falls under the broad dominion of google, microsoft and a couple of other large players.





  • Maybe the client is faster/prettier/can show videos/uses less data/integrates with their phone better.
    Maybe it’s got features that clients here lack such as the ability to host larger images or video.
    Maybe the user is sick of responding to conversations over there and it not being federated, so they are ignored.
    Maybe using the Threads app is just faster (because it’s local instead of batch federating).

    If I was in charge of product design for Threads, I would be literally crawling the issue listings for Lemmy/Kbin and the associated clients looking for complaints and implementing solutions for those problems.
    Then I would make a list of every limitation within the system and make sure Threads exceeds that baseline.

    And then when I had made the software better in every measurable way (because I am paying a large team of developers to target those pain points), I’d start adding features that ActivityPub doesn’t, especially if ActivityPub instances would find those features hard to implement.

    I’d make damn sure that every time ActivityPub changes from a source outside Meta, I’d drag my heels on implementing that feature, so that instance hosts are forced to choose between implementing the new version, or maintaining compatability with Threads.

    Why would a user here move there?
    Because their spouse/coworker/friend tried to send something for the 50th time and the message just never came through.


  • Threads will mainstream threads.
    Any good content here will be available to the Threads users, who will be oblivious to where it is coming from.
    Eventually, Meta will take steps to break compatability, and lots of the most prolific contributors from here will move to Threads exclusively (for a host of valid reasons).
    When it is no longer in Meta interest to federate, they will stop.

    The fediverse will continue, but it will be weakened by it’s temporary reliance on Threads (who could afford to host large images/videos/etc, have lower latency, etc etc).