• 1 Post
  • 36 Comments
Joined 4 个月前
cake
Cake day: 2026年2月18日

help-circle



  • Do you never leave the house for any period of time where you might want to bring some of your media?

    In short; do you never travel?

    Plex charges for downloading your own media through your own local network onto your own local devices.

    I’m not talking about remote streaming. I’m not talking about downloading media while you’re already out of the house. Nothing about local downloads to local devices should require Plex’s servers, so it should come at no cost to them, which makes it a pure cash grab.

    So yes, Plex does charge for local use :)




  • The problem is, I have an account on lemmy.world but switched off during a time it had major problems with downtime and broken images. When I wanted to switch to another provider, my account was not portable. I hadn’t posted or commented an overwhelming amount, but it’s still not associated with this account.

    So let’s say someone creates a federated Git hosting platform and feature matches GitHub with Actions/CI etc, so there’s no reason not to switch. Let’s then say git.world starts acting up, but you can create an account on git.zip instead.

    Now you have given up your commit history and any commits you make from your git.zip account is not neatly linked with your git.world account.

    I’m sure this problem can be solved, but it’s vastly more important for it to be solved before federated Git hosting can replace the “security” of GitHub. We do have to consider the fact that some people point to their GitHub profile when job searching, so git contributions and commit history is more valuable than Lemmy posts.





  • It’s funny coming from the Plex thread into this; ~100% of people who keep using Plex do so because it’s centralised and it makes sharing their library with their network of family and friends easier.

    The truth is; a lot of us feel like we need more internet accounts about as much as we need genital warts. Part of the reason GitHub got successful was the fact that you only needed to register once and you had access to fork and PR all the repos on there.

    Decentralisation is great for self hosting things for, well, yourself and your household, but it’s got hefty downsides. Account creation is a friction point for others to join and collab.



  • My mother also worked at a switch board. When she moved into hospitality, and the guests needed to make a call, the switch board operators immediately clocked her as having worked there. My mother presented the information about the outgoing call request exactly as the operator preferred to hear it to quickly make the connection.

    I feel you about wishing you had more time with your grandmother. I was far too young to even know what questions I could have asked, and it would have been so interesting to hear about the occupation during WW2 and the early post war years.

    Not to mention the fact I miss her in general, she was the sweetest lady a grandson could ever ask for ❤️


  • If we accept the premise that certain distros will need to comply with age verification laws (school specific ones, distros running on govt machines), then it would be better if that information was securely stored in the system database rather than relying on each school/government agency reinventing the wheel.

    I will save my ire and save my effort protesting until age verification, not attestation, makes its way into my distro of choice.




  • This is the most sane take I’ve read in this entire debacle. Between arguing the semantics of attestation vs verification and whether we need five hundred forks and PRs, I’m glad to read this.

    The biggest mistake the original PR did was not make it more clear it’s not directly because of the laws themselves, it’s to support higher level systems that may want to or need to comply. Systemd is no more complying with any present or future laws than a keyboard manufacturer is violating the law if the user uses it to type racially motivated hate speech.



  • There is absolutely nothing of worth in that article.

    First of all, the team size is irrelevant. Even if the maintainers all end up in plane crashes or whatever, all that would happen is packages would “revert” to core Arch when a newer version is released.

    Secondly, Secure Boot is a Microsoft-controlled technology that is not FOSS, and should not be considered mandatory like the author implies.

    Lastly, the author conveniently doesn’t offer any evidence as to what exactly about Cachy’s “culture” (whatever that means) encourages AUR usage. The only thing I can think of is the fact that an AUR helper is preinstalled.

    Not a single claim that isn’t incorrect on its face actually has any sources backing it up.

    Can you elaborate on which part of this article has more worth than your average AI slop article?