• 1 Post
  • 55 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle


  • Yes, but is this them being assholes, or them wanting to make sure that users aren’t making their system unreliable? I think there would be a huge distinction there.

    For example, say a user wanted to create a cache drive using an SSD. But because the user doesn’t know better, they buy the cheapest crap they can find, install it, and set up caching. But because they’re using cheap shit, the drive is slow and the user reports poor performance, system hangups, and other instability.

    Wouldn’t it be in Synology’s best interest to say “here’s a list of drives we know will give you the best experience.”?

    Now, Synology has already done that, but users are ignoring it and continue to use poor storage drives expecting to use pretty sophisticated features. What now? Well, Synology disables those features.

    For example:

    De-duplication, lifespan analysis, and automatic HDD firmware updates could also disappear on non-approved drives

    Um, yeah. That makes sense. If a shitty hard drive can’t reliably get firmware updates through the NAS, why on earth would they want to keep that option enabled? Same with lifespan analysis. If a crappy drive isn’t using modern standards and protocols for measuring and logging errors and performance data, Synology really can’t “enable” this to work, can they?

    That’s what I think is happening. Although, this could be just greed, too. I don’t think there’s any real problem for most users, unless they say that we can’t use fairly common, high-quality NAS drives from Seagate or WD and must use their own branded drives. I’d have a huge problem with that.


  • Are we overreacting? Hasn’t Synology always had a list of “certified” drives for their NAS’, which end up being the same HDDs we would tend to use anyway?

    I can understand that they don’t want people using any garbage storage drives, which could increase failure and make Synology NAS’ look unreliable.

    Unless something has changed, this is how they’ve always done it, just like how every laptop manufacturer will say which RAM and storage works best (for reliability and performance) on their machines.


  • Yes, incoming.

    Outgoing is another can of worms.

    I try to run any of my iot devices on an isolated network. At most, they can see eachother, and that’s it.

    Some devices need an internet connection, unfortunately.

    The best you can do, if you’re unable to block their collection outright, is to run them through a tracker-blocking DNS (either self-hosted or something like Adguard DNS).

    That can minimize unnecessary pings home.

    Personally, if I think that a device is being malicious in their attempts to phone home, I stop using the device. I also try to make an effort to not get a smart device, if the alternative (unconnected option) works fine.

    Digital minimalism is one way to protect ourselves from rampant data collection and profiling.







  • I don’t give a shit about my car, but I’d love to use this for my bikes! I’m currently using a spreadsheet and self-hosted calendar to keep track, but this would be “easier”.

    I tried the demo, but maybe I missed it: how do you export the data you’ve input, in case you need to move it to somewhere else or if the project stops, and you want to back up the data?

    Data portability is as important to me as self-hosting.






  • I think my point was missed. I wasn’t saying that GIMP should copy what Adobe does (I can’t stand Adobe and their “business model” spyware bullshit.

    My point was more to show that Adobe showcases the features of the software, so a potential user knows what it does without needing to go through the trouble of downloading it. It may not be what the user wants, and that’s ok, at least they know!

    But GIMP is so vague in their description and offers no insight to what the app does or looks like. There’s no need to be mysterious.


  • Man, that text does the app no favours. “Image editor” could mean that it crops photos. But GIMP does a hell of a lot more. It’s been “the open-source photoshop” for decades, and they’re really selling themselves short. Screenshots would have made it so much easier to see what the software does.




  • For sure, I don’t mean to blanket all FOSS projects under the same observation. But I’ve seen some projects where the idea is brilliant, and it fills a gap that no other software can, but they have piss-poor instructions (or none at all) and hardly describe what the project is or does. You only learn about them by chance, which is a real shame.

    Here’s another example: Navidrome (https://www.navidrome.org/) is an awesome, self-hosted music streaming software.

    But their homepage doesn’t have a screenshot, so you have no idea if the UI is just command prompt, ugly, unintuitive, or the best thing ever. Even the “learn more” page has no screenshots unless you really go digging.

    Compare that to another FOSS self-hosted music streamer: https://ampache.org/

    Simple website, but at least you can see exactly what to expect from the UI. Huge advantage even if they two apps do the exact same thing (both based on the Subsonic backend).