• 1 Post
  • 347 Comments
Joined 22 days ago
cake
Cake day: April 26th, 2025

help-circle
  • Then explain why one can successfully use and old synology to “mark” drives as “authentic synology” and move them into a newer DSM model to use them.

    Because they have to have a way for legacy users to maintain functionality. Going forward though, new drives in new devices are handled differently. It’s basically a quality control type thing - they’re providing the support and warranty for them, so they’re only “guaranteeing” that their checks work on their drives. That makes sense. They don’t want to be on the hook for saying that a drive that isn’t theirs was perfectly healthy and then it drops dead an hour later and you lose all your data.

    As explained ad nauseum on various yt channels, having a hw compatibility list makes sense for users likely to buy support, like business users.

    Again though, the disks still work. The compatibility lists simply tell you if they are officially supported and will get certain features.

    But add on top of it that there is no functional hardware difference between certified and non-certified, and it becomes pretty clear that Synology is to be avoided.

    But add on top of it that there is no functional hardware difference between certified and non-certified, and it becomes pretty clear that Synology is to be avoided.

    Avoiding them because of missing a few proprietary synology disk health checks is such a strange thing to do lol. You won’t get synologys disk health checks if you were to make your own server, so why is not having them on a synology a deal breaker?




  • Synology’s software is awful. Simply controlling NFS shares is an exercise in insanity, and don’t get me started on ACLs.

    Strange, I’ve had no issue controlling NFS shares or ACLs. Have set up 4 Synology NAS’s, with shares out the wahzoo. No problems. User error maybe?

    Further, synology is a real bastard company currently trying to enshittify hardware (disk) upgrades, among other terrible practices:

    That disk upgrade thing was a mountain out of a molehill. All they are doing is reserving some of their disk health features for synology branded disks because they’re the only ones they can verify meet their standards for their software.














  • It does change that fact, because again - they’re forced to by law. There’s no wiggle room. Had they chosen to defy them and take them to court, Microsoft probably would have been forced to cease trading in the USA or something equally as company destroying.

    Your data and email isn’t ever “safe” unless you’re hosting every single part of it yourself, and even then - if the government orders you to do something, you’ll fold like origami when faced with the alternative. Microsoft aren’t in the business of deciding who is and isn’t “tyrannical”. They are in the business of following legal orders and staying in business though.


  • You’re saying that Spotify don’t have employee moderators for uploaded podcasts, which they do. In this era of every person thinking they’re an influencer and everyone needs to hear what they say, the issue is that likely no matter how many they have, the number of episodes that get uploaded will always dwarf them, so they rely on their auto-moderators to find the most egregious rule breakers. They can’t catch everything there though. If a customer finds a rule breaker and reports it, they’ll take action - that’s good!

    The alternative is that every single episode of every single podcast has to be manually reviewed and approved before it goes live, which is not feasible.





OSZAR »